On 06/13/2010 01:51 AM, Chris Kloiber wrote:
> IIRC, you might be having an SELINUX issue. Check to see if SELINUX does
> not like the labeling on the ~/.ssh/authorized_keys2 file.
>
restorecon -R -v ~/.ssh
Will fix the problem. You have to have the correct labels in order for
sshd to reach the
sean darcy writes:
> On 06/12/2010 09:34 AM, Wolfgang S. Rupprecht wrote:
>>
>> Craig White writes:
>>> sounds like you created the file elsewhere (or even on another computer)
>>> and moved it into place thereby creating SELinux issue.
>>
>> That would be my guess too, seeing how it happens to
IIRC, you might be having an SELINUX issue. Check to see if SELINUX does
not like the labeling on the ~/.ssh/authorized_keys2 file.
--
Chris Kloiber
On 06/13/2010 01:06 AM, Ed Greshko wrote:
On 06/12/2010 09:33 AM, sean darcy wrote:
New install of F13.
drwx--. 2 root root 4096 Jun 11
On 06/12/2010 09:33 AM, sean darcy wrote:
> New install of F13.
>
> drwx--. 2 root root 4096 Jun 11 20:22 .ssh
>
> ls -l /root/.ssh
> total 12
> -rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
>
>
> The rsa key is in authorized_keys.
>
> But when I try to login into root:
>
> Jun 11
On Sat, Jun 12, 2010 at 11:14 PM, sean darcy wrote:
> On 06/12/2010 02:37 AM, Konstantin Svist wrote:
>
> How do I "Check/fix the selinux flags for your authorized_keys"?
>
>From $HOME do:
restorecon -R -v .ssh
Pretty sure that will do that trick.
By the way earlier in this thread there was th
On 06/12/2010 09:34 AM, Wolfgang S. Rupprecht wrote:
>
> Craig White writes:
>> sounds like you created the file elsewhere (or even on another computer)
>> and moved it into place thereby creating SELinux issue.
>
> That would be my guess too, seeing how it happens to me regularly when I
> do clea
On 06/12/2010 02:37 AM, Konstantin Svist wrote:
> On 06/11/2010 06:33 PM, sean darcy wrote:
>> New install of F13.
>>
>> drwx--. 2 root root 4096 Jun 11 20:22 .ssh
>>
>> ls -l /root/.ssh
>> total 12
>> -rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
>>
>>
>> The rsa key is in author
Craig White writes:
> sounds like you created the file elsewhere (or even on another computer)
> and moved it into place thereby creating SELinux issue.
That would be my guess too, seeing how it happens to me regularly when I
do clean installs and then try to copy the customized files from an NF
On 06/11/2010 06:33 PM, sean darcy wrote:
> New install of F13.
>
> drwx--. 2 root root 4096 Jun 11 20:22 .ssh
>
> ls -l /root/.ssh
> total 12
> -rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
>
>
> The rsa key is in authorized_keys.
>
> But when I try to login into root:
>
> Jun 11
On Fri, 2010-06-11 at 21:33 -0400, sean darcy wrote:
> New install of F13.
>
> drwx--. 2 root root 4096 Jun 11 20:22 .ssh
>
> ls -l /root/.ssh
> total 12
> -rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
>
>
> The rsa key is in authorized_keys.
>
> But when I try to login into
Larry Brower wrote:
> sean darcy wrote:
>> New install of F13.
>>
>> drwx--. 2 root root 4096 Jun 11 20:22 .ssh
>>
>> ls -l /root/.ssh
>> total 12
>> -rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
>>
>>
>> The rsa key is in authorized_keys.
>>
>> But when I try to login into root:
sean darcy wrote:
> New install of F13.
>
> drwx--. 2 root root 4096 Jun 11 20:22 .ssh
>
> ls -l /root/.ssh
> total 12
> -rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
>
>
> The rsa key is in authorized_keys.
>
> But when I try to login into root:
>
> Jun 11 21:12:39 new-gate
New install of F13.
drwx--. 2 root root 4096 Jun 11 20:22 .ssh
ls -l /root/.ssh
total 12
-rw---. 1 root root 1006 Jun 11 20:23 authorized_keys
The rsa key is in authorized_keys.
But when I try to login into root:
Jun 11 21:12:39 new-gateway sshd[1786]: debug1: temporarily_use_uid: 0
13 matches
Mail list logo
