projects / u / mdw / putty / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c232b3e) | patch
Padding on the end of the encrypted data in OpenSSH key format was
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sat, 15 Jun 2002 16:31:22 +0000 (16:31 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sat, 15 Jun 2002 16:31:22 +0000 (16:31 +0000)
commit04627c33eaedaab98bce22ed21103a0b8324cff6
treee2eaf469e25b4199f26d105e7fde8ac5a6a519b4tree | snapshot (tar.gz zip)
parentc232b3e336238048cb3a8c3548906182ee54c9cdcommit | diff
Padding on the end of the encrypted data in OpenSSH key format was
broken: the OpenSSL EVP layer specifies a very particular form of
padding, which I wasn't generating because it hadn't occurred to me
that it might be mandatory. Irritatingly this was causing our
exported OpenSSH keys to load perfectly happily back in through our
OpenSSH import routines, but to be rejected by OpenSSH proper. Sigh.

git-svn-id: svn://svn.tartarus.org/sgt/putty@1733 cda61777-01e9-0310-a592-d414129be87e
import.c diff | blob | blame | history
Local modifications for Simon Tatham's `PuTTY' SSH client and terminal emulator