[Bug 887] Problem connecting OpenSSH Client to a F-Secure SSH Server

[bugzilla-daemon at mindrot.org]

http://bugzilla.mindrot.org/show_bug.cgi?id=887

mouring at eviladmin.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
          Component|sftp                        |ssh-keygen
         OS/Version|other                       |Linux



------- Additional Comments From mouring at eviladmin.org  2004-06-30 14:56 -------
yume:~ mouring$ ssh-keygen -b 1024 -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/Users/mouring/.ssh/id_dsa): xxx
Enter passphrase (empty for no passphrase): testme
Enter same passphrase again: testme
Your identification has been saved in xxx.
Your public key has been saved in xxx.pub.
The key fingerprint is:
b6:5a:2c:24:2d:32:4a:40:c9:b4:13:0e:12:65:d9:ce mouring at yume.local
yume:~ mouring$ cat xxx
-----BEGIN DSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,5D45E766C929404A

OUKT6wiDFO9HNVPis7IEoQtBGCeiHHAm8j0PyqcVCDCwpRnGSYEIrY2avkth/ohd
MPeW+aL08uB3b0c+67gF35ucJOGNVyzXue6izojJKB/ZoPCfdUpQGnnkNF/MsUok
ymEhzvg0ZF29qilaQeVbSE7MJnQupAiU5pa0TzeoUvlBtlxTVPlenaNt3CPj8KIU
QPKMNsHFWuyMHKk9MKc7uDWCJB4VtZbfrnrafUig+gisncpyhTQsU7fwzRTkUUI9
NNKFTx9jWXLN6CJGSw3Ju58J0CmbmH0dyGUfzRCvLoWKltu8sI/wk/tGE646BooM
WltvqcY7SGjl0Md7HYAZf0tPGgyW+7TyAczJwuGqMmuDW5rqeQ/SOXoxkM76y1iM
jqzZhGoZ4WGFxbYgiVn8b1x1SCeKLp/digsidThXsab65z0VrTaB3kl6FhEFWJo8
AwSn6NNrgOMViYVZWKsTPtFPfIJy3E9LieC0Qo0vJBca3HSTqMGWOEzSQWprQPyc
VCYWtXW7Sh1j7fVqdN8G/E5nV3CpVuLjxZgvOuDqrFyf+OWsjReAruAYgsmCwQsu
c7qNaH3CNkUgfJvk7Joj4w==
-----END DSA PRIVATE KEY-----
yume:~ mouring$ openssl dsa -in xxx -noout
read DSA key
Enter PEM pass phrase: testme
yume:~ mouring$ 

That is what you should see.  By the fact that "openssl" is not accepting the dsa key means something 
went wrong while generating it.   3.4p1 is pretty old and unless patched has at least one security issue 
assocated with it. 

I'm remarking this as a ssh-keygen issue and marking it down to "normal" unless you can prove the 
current release shows the same issue.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.