OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Anthony Atkielski (anthonyatkielski.com)
Date: Mon Nov 05 2001 - 13:24:12 CST

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

    Public-key is what I want, not password. In fact, PermitRootLogin
    without-password supposedly prevents password authentication from being used in
    SSH, forcing PK authentification.

    ----- Original Message -----
    From: "alexus" <mldb.nexgen.com>
    To: "Anthony Atkielski" <anthonyatkielski.com>; <freebsd-securityfreebsd.org>
    Sent: Monday, November 05, 2001 18:27
    Subject: Re: SecureCRT and SSH2 on FreeBSD

    > check your secure crt configuration
    >
    > most likly you specify to use public key instead of password
    >
    > ----- Original Message -----
    > From: "Anthony Atkielski" <anthonyatkielski.com>
    > To: <freebsd-securityfreebsd.org>
    > Sent: Monday, November 05, 2001 12:14 PM
    > Subject: SecureCRT and SSH2 on FreeBSD
    >
    >
    > > Can anyone assist me with the exact configuration for getting SecureCRT
    > (on
    > > Windows) to work with SSH2 against a FreeBSD server? I got SSH1 to work
    > okay,
    > > and--mysteriously--SSH2 seems to work against my Web server (4.2 release)
    > on the
    > > Net, but I can't connect to my own FreeBSD 4.3 server at home; all I get
    > is a
    > > message saying
    > >
    > > Public-key authentication with the SSH2 server for user root failed.
    > Please
    > > verify username and public/private key pair.
    > >
    > > Do I have to run anything to make SSH2 work, or is sshd sufficient? I
    > have
    > > telnetd disabled. I have PermitRootLogin set to without-password. root
    > can log
    > > in under SSH1, but nobody can log in under SSH2.
    > >
    > >
    > > To Unsubscribe: send mail to majordomoFreeBSD.org
    > > with "unsubscribe freebsd-security" in the body of the message
    > >
    >
    >

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