]> asedeno.scripts.mit.edu Git - PuTTY.git/commit
Padding on the end of the encrypted data in OpenSSH key format was
authorSimon Tatham <anakin@pobox.com>
Sat, 15 Jun 2002 16:31:22 +0000 (16:31 +0000)
committerSimon Tatham <anakin@pobox.com>
Sat, 15 Jun 2002 16:31:22 +0000 (16:31 +0000)
commit729512abc2a6209423511522709ae130d8b38ad9
treee2eaf469e25b4199f26d105e7fde8ac5a6a519b4
parentab1d4f5dce15dc037672f817de28f1e27bcbf5a6
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.

[originally from svn r1733]
import.c