-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Could be, however this sounds like you are trying to use a protocol or
authentication method that is not supported.
This is a way of allowing all with the preference of publickey,
AllowedAuthentications publickey,password,hostbased
# AllowedAuthentications publickey
The other might be the cipher that you are allowing and the one that
is compiled into the program. Try allowing any cipher and change your
ciphers with the program you are using, which is... ?
This should work. Try using 3des first and see if that works.
==DMT>
____________________________________________
Douglas M. Todd, Jr.
Network Architect
Sapient Corporation
One Memorial Dr.
Cambridge, MA 02072
Ph: 617.679.6974
Fx: 617.374.0320
Em: offsite: <[EMAIL PROTECTED]> || onsite: <[EMAIL PROTECTED]>
3w: www.sapient.com
pgp finger print: 0ABD 17C3 A8AF 4C17 AA17 0A78 418D D938 2AEE C185
verisign thumb: 65F6 0951 538F 990D 4687 21A9 41C0 5DD0
"So what are the ethics of rattling someone's door knob?"
> -----Original Message-----
> From: Joseph Galbraith [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 26, 2000 2:49 PM
> To: Ken Scott
> Cc: [EMAIL PROTECTED]
> Subject: Re: No Further Authentication Methods Available
>
>
> Sounds like maybe the client doesn't have a valid reverse
> DNS mapping? The 2.0.13 server is configured to require
> this by default, and if it can't resolve the client ip, you
> get the behavior you've described.
>
> I believe the parameter is RequireReverseMapping in the
> server config file.
>
> - Joseph
>
> > On 26-Jan-00 Ken Scott wrote:
> > > Hi all.
> > >
> > > I apologize in advance for asking about this, because I
> know it's been
> > > asked before--I've seen it in the archive--but I've never seen
an
> > > answer. I've just installed ssh-2.0.13 (Red Hat 6.1, via
> the RPM), and
> > > all seemed to go well. However, when attempting to connect to
any
> > > remote
> > > machine, I get nothing but the "no further authentication
methods
> > > available" message. I gather this is some sort of
> client-configuration
> > > issue, but can't figure out what needs to be changed. If
> anyone could
> > > offer any suggestions, it would be greatly appreciated.
>
>
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.0.2
iQA/AwUBOJBUAkGN2Tgq7sGFEQKUhgCcCWA/D4Zms8wB2WYb305fOxE50YkAoI/L
IwxkxoFWtXcqFN3y4TMAINyq
=oIoM
-----END PGP SIGNATURE-----
