From: Brian Davis <bridavis@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sshd issues
Date: Wed, 15 Nov 2006 09:22:08 -0500 [thread overview]
Message-ID: <455B2290.4090301@comcast.net> (raw)
In-Reply-To: <455A8490.8080207@net-xero.net>
Just keep in mind that rsa/dsa keys would be a more secure way of
authenticating, especially with all the brute-force scripts out there.
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
>
> This works perfectly now. Thanks again everyone, sorry for wasting
> your time.
>
> brettholcomb@bellsouth.net wrote:
>> I think that tells you that this is the default setting if you don't
>> change it.
>>
>>> From: Jon M <gentoo@net-xero.net>
>>> Date: 2006/11/14 Tue PM 09:35:13 EST
>>> To: gentoo-user@lists.gentoo.org
>>> Subject: Re: [gentoo-user] sshd issues
>>>
>>> Hi Daevid,
>>>
>>> I tried playing around with some options in there and didn't seem to
>>> do much, but not sure if I tried changing that specifically. I do
>>> have a question though.. My ssh_config looks something along the
>>> lines of this:
>>>
>>> # Host *
>>> # PasswordAuthentication yes
>>>
>>> My question is, should they actually have # symbols in front as if
>>> they're commented out? My gut is telling me no..
>>>
>>> Thanks again
>>>
>>>
>>> Daevid Vincent wrote:
>>>> Change/Add this:
>>>>
>>>> PasswordAuthentication yes
>>>>
>>>> In /etc/ssh/sshd_config
>>>>
>>>> DÆVID
>>>>> -----Original Message-----
>>>>> From: Jon M [mailto:gentoo@net-xero.net] Sent: Tuesday, November
>>>>> 14, 2006 6:04 PM
>>>>> To: gentoo-user@lists.gentoo.org
>>>>> Subject: [gentoo-user] sshd issues
>>>>>
>>>>> Hey all,
>>>>>
>>>>> I've been using other distributions for a while (CentOS,
>>>>> Slackware, Red Hat, etc) and finally switching to Gentoo, however
>>>>> this oddness with SSH is getting to me. It seems when I SSH into
>>>>> my machine it uses "keyboard interative" mode, where as I'm used
>>>>> to every other distro using just "password" mode I think it is.
>>>>> I'm wondering if there is any way to change this. I tried
>>>>> comparing /etc/ssh/ssh_config between my CentOS machine and my
>>>>> Gentoo machine, and both files are pretty much the same, and
>>>>> everything is commented out anyway.
>>>>>
>>>>> Any light someone could shed on this would be much appreciated.
>>>>> Thanks in advance!
>>>>> --
>>>>> gentoo-user@gentoo.org mailing list
>>>>>
>>>>>
>>>>
>>> --
>>> gentoo-user@gentoo.org mailing list
>>>
>>>
>>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-15 14:28 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 [this message]
2006-11-15 15:44 ` Mick
2006-11-15 16:17 ` Jon M
-- 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=455B2290.4090301@comcast.net \
--to=bridavis@comcast.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