summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2016-04-28Merge branch '1.17'Jeff Forcier
2016-04-28Merge branch '1.16' into 1.17Jeff Forcier
2016-04-28Merge branch '1.15' into 1.16Jeff Forcier
2016-04-28Pushed regular versions of all tags so this is no longer neededJeff Forcier
2016-04-28Merge branch '1.17'Jeff Forcier
2016-04-28Annotate bug 649 with major keyword againJeff Forcier
2016-04-28Merge branch '1.17'Jeff Forcier
2016-04-28Merge branch '1.16' into 1.17Jeff Forcier
2016-04-28Merge branch '1.15' into 1.16Jeff Forcier
2016-04-28Keep the big posse of backported supports out of 2.0Jeff Forcier
Looks cleaner that way.
2016-04-28Merge branch '1.15' into 1.16Jeff Forcier
2016-04-28Update backported support items with both keywords and specs.Jeff Forcier
Now that bitprophet/releases#45 is done, this works
2016-04-28Add 2.0.0 release back in for final changelog tweakingJeff Forcier
2016-04-28Merge branch '1.17'Jeff Forcier
2016-04-28date bumpJeff Forcier
2016-04-28Mark the 1.17-specific features so they show up in that releaseJeff Forcier
2016-04-28Merge branch '1.16' into 1.17Jeff Forcier
2016-04-28date bumpJeff Forcier
2016-04-28Merge branch '1.15' into 1.16Jeff Forcier
2016-04-28Bring alabaster req in line with newer branchesJeff Forcier
2016-04-28Update some backported support tickets as 1.15+Jeff Forcier
Including 612 which should've been marked backported but was not.
2016-04-28Really hope this date sticksJeff Forcier
2016-04-28Update releases/semantic_version dependencies re: major version workJeff Forcier
2016-04-28Changelog entry re #731, re #611Jeff Forcier
2016-04-28Patch fix via @alex on #731, tests pass locally againJeff Forcier
2016-04-28Merge branch 'master' into 731-intJeff Forcier
2016-04-28Merge branch 'master' of github.com:paramiko/paramikoJeff Forcier
2016-04-28Merge pull request #733 from alex/from-encoded-pointJeff Forcier
Use a more recent cryptography and call a function
2016-04-27Use a more recent cryptography and call a functionAlex Gaynor
2016-04-25Formatting tweaks re #731Jeff Forcier
2016-04-25Merge branch 'master' into 731-intJeff Forcier
2016-04-25Merge branch '1.16' into 1.17Jeff Forcier
2016-04-25Merge branch '1.17'Jeff Forcier
2016-04-25Merge branch '1.15' into 1.16Jeff Forcier
2016-04-25Changelog closes #670Jeff Forcier
2016-04-25Test & implementation for part 1 re: #670Jeff Forcier
2016-04-25Merge branch '1.16' into 1.17Jeff Forcier
2016-04-25Merge branch '1.17'Jeff Forcier
2016-04-25Merge branch '1.15' into 1.16Jeff Forcier
2016-04-25Neglected to mark a bug 1.15+.Jeff Forcier
Was showing up in 1.13, 1.14 releases
2016-04-25Merge branch '1.17'Jeff Forcier
2016-04-25Reinstate 1.17.0 release lineJeff Forcier
2016-04-25Merge branch '1.16' into 1.17Jeff Forcier
2016-04-25Reinstate 1.16.1 release lineJeff Forcier
2016-04-25Merge branch '1.15' into 1.16Jeff Forcier
2016-04-25Reinstate release line for 1.15.5Jeff Forcier
2016-04-25Add support for ECDSA key sizes 384 and 521 alongside the existing 256.Alex Orange
Previously only 256-bit was handled and in certain cases (private key reading) 384- and 521-bit keys were treated as 256-bit keys causing silent errors. Tests have been added to specifically test the 384 and 521 keysizes. As RFC 5656 defines 256, 384, and 521 as the required keysizes this seems a good set to test. Also, this will cover the branches at ecdsakey.py:55. Test keys were renamed and test_client.py was modified as a result. This also fixes two bugs in ecdsakey.py. First, when calculating bytes needed to store a key, the assumption was made that the key size (in bits) was divisible by 8 (see line 137). This has been fixed by rounding up (wasn't an issue as only 256-bit keys were used before). Another bug was that the key padding in asbytes was being done backwards (was padding on current_length - needed_length bytes).
2016-04-25Merge branch '1.17'Jeff Forcier
2016-04-25Merge branch '1.16' into 1.17Jeff Forcier
2016-04-25Reword/link changelog re #677, re #676Jeff Forcier
generated by cgit v1.2.3 (git 2.39.1) at 2025-03-15 12:48:55 +0000