From: Jon M <gentoo@net-xero.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sshd issues
Date: Wed, 15 Nov 2006 11:17:23 -0500 [thread overview]
Message-ID: <455B3D93.4050300@net-xero.net> (raw)
In-Reply-To: <200611151544.46407.michaelkintzios@gmail.com>
Mick wrote:
> On Wednesday 15 November 2006 03:08, Jon M wrote:
>> Ohh okay that makes sense.
>>
>> For everyones information, I got it to work properly. First of all, I'm
>> an idiot and was edited /etc/ssh/ssh_config, not /etc/ssh/sshD_config :P
>>
>> Secondly, I had to enable PasswordAuthentication yes as well as
>> ChallengeResponseAuthentication no
>
> How does ChallengeResponseAuthentication affect matters?
Hi Mick,
I'm not sure, however when ChallengeResponseAuthentication is set to yes
it still would go into keyboard interactive mode.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-15 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 2:49 Re: [gentoo-user] sshd issues brettholcomb
2006-11-15 3:08 ` Jon M
2006-11-15 14:22 ` Brian Davis
2006-11-15 15:44 ` Mick
2006-11-15 16:17 ` Jon M [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-15 2:04 Jon M
2006-11-15 2:29 ` Daevid Vincent
2006-11-15 2:35 ` Jon M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=455B3D93.4050300@net-xero.net \
--to=gentoo@net-xero.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox