OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Jason Stone (jason-fbsd-securityshalott.net)
Date: Wed Mar 06 2002 - 10:58:01 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    > If the problem was that SSH was using protocol 2 instead of 1, and you
    > only had an SSHv1 key, please note that all the machines in the
    > FreeBSD cluster accept SSHv2 keys now, too :) I personally prefer to
    > go with v2 anywhere I can, so I just generated a v2 key (ssh-keygen -t
    > dsa) and copied the public key over to freefall:.ssh/authorized_keys2.

    The current version of openssh has deprecated the use of authorized_keys2,
    known_hosts2, etc, and they threaten that future version will completely
    ignore the *2 files.

    So it's probablly a good idea to keep all your keys in authorized_keys,
    and symlink that to authorized_keys2 for now.

     -Jason

     -----------------------------------------------------------------------
     I worry about my child and the Internet all the time, even though she's
     too young to have logged on yet. Here's what I worry about. I worry
     that 10 or 15 years from now, she will come to me and say "Daddy, where
     were you when they took freedom of the press away from the Internet?"
            -- Mike Godwin

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.0.6 (FreeBSD)
    Comment: See https://private.idealab.com/public/jason/jason.gpg

    iD8DBQE8hkqcswXMWWtptckRAgnFAKC8cj4VA1MF+pGee4IQ+0rgANNf3wCgo+DH
    2P2fqRRk5/MEqi/QyfLEWPg=
    =tZre
    -----END PGP SIGNATURE-----

    To Unsubscribe: send mail to majordomoFreeBSD.org
    with "unsubscribe freebsd-security" in the body of the message