full-disclosure - OpenSSHd - Publickey-Authentication - Has 3.9 problems with 16384Bit DSA-keys?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1105646834.76923.34.camel@localhost>
From: frank at knobbe.us (Frank Knobbe)
Subject: OpenSSHd - Publickey-Authentication - Has
	3.9 problems with 16384Bit DSA-keys?

On Thu, 2005-01-13 at 19:54 +0100, vh wrote:
> I created a 16384-Bit DSA-Key and stored the public part of this key in
> ./ssh/authorized-keys. I'm able to login with a 4096Bit DSA-Key but the
> SSHd wont accapt the 16384Bit-Key and falls back to passwort
> authentication.

heh... I'm just curious: Why do you think a 4096 bit key is not
sufficient? 
And, don't you think the session setup of a 16K+ key would be
computationally expensive?

Frank

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050113/20151829/attachment.bin