On Sun, Jun 1, 2008 at 3:56 PM, Ira Abramov <[EMAIL PROTECTED]> wrote: > Quoting Amos Shapira, from the post of Fri, 30 May: >> >> All packages on my Debian Etch desktop are up to date, "vulnkeys" >> found old vulnerable keys and I cleaned them up (also from other >> systems). >> >> BUT - I can't generate good keys on Debian any more: > > that's odd. are you sure you are not running an old ssh-keygen that was > mistakenly somehow not updated? (moved elsewhere in the path, in a > chroot or something?) > > try "which" and see it's really the one from the updated package. also
In addition to what I described in my previous reply (to Shachar's message) I also did "which" and saw that it resolves to /usr/bin/ssh-keygen. > make sure you did dist-upgrade and not just upgrade. I think without it, Why "dist-upgrade"? It's a security fix for the same distro (Debian Etch). > it didn't really update ssh for me, because the way the update was The package version is 1:4.3p2-9etch2. Is this the one it should be? > defined (a split to "openssh-client" and "openssh-blcklist" or something > like that, and I think it required dist-upgrade) I have both on my system now, as far as I'm aware ssh-vulnkeys was introduced only in the new packages. Any other ideas? Thanks, --Amos ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
