Never heard of lsh before. Does having lsh as the first solution suggest to anyone besides me that this is an attempt to beef up one project's marketshare at the expense of another?
If it's real, it'll make slashdot. If ssh has the exploit but lsh doesn't, then ssh will be fixed. If it's unfixable, both are broken, and a new protocol will be invented. If it's an aspect common to all security protocols, we're hosed and there's no such thing as encryption anymore.
No biggie.
-- J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Judging from recent posts in freebsd-security mailing lists it seems it is real. I'm too lazy to find relevant links in freebsd mailing list archives but belive me you will be seeing it on Slashdot very soon.
Hmm (Score:3, Insightful)
Never heard of lsh before. Does having lsh as the first solution suggest to anyone besides me that this is an attempt to beef up one project's marketshare at the expense of another?
If it's real, it'll make slashdot. If ssh has the exploit but lsh doesn't, then ssh will be fixed. If it's unfixable, both are broken, and a new protocol will be invented. If it's an aspect common to all security protocols, we're hosed and there's no such thing as encryption anymore.
No biggie.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Reply to This
Re:Hmm (Score:2)
Ilya Martynov (http://martynov.org/ [martynov.org])
Re:Hmm (Score:2)
There it goes. [slashdot.org] Must be real.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:Hmm (Score:1)
Re:Hmm (Score:1)
Buck