On 06/21/17 02:36, Frédéric Bron wrote:
> Thanks a lot, I was becoming totally crazy!!
You're welcome.
I would have taken the route suggested by Paul to resolve the problem as it
takes
care of all the files and directory at once.
--
Fedora Users List - The place to go to speculate endlessly
On Tue, 20 Jun 2017 20:36:22 +0200
Frédéric Bron wrote:
> >> -rw---. 1 egreshko egreshko
> >> unconfined_u:object_r:ssh_home_t:s0 398 Jun 21 01:35
> >> authorized_keys
> >
> > Interesting, I have home_root instead of ssh_home. What does that
> > mean? Does it mean that I created the .ssh d
On Tue, Jun 20, 2017 at 08:36:22PM +0200, Frédéric Bron wrote:
> >> -rw---. 1 egreshko egreshko unconfined_u:object_r:ssh_home_t:s0 398
> >> Jun 21 01:35
> >> authorized_keys
> >
> > Interesting, I have home_root instead of ssh_home. What does that
> > mean? Does it mean that I created the .s
>> -rw---. 1 egreshko egreshko unconfined_u:object_r:ssh_home_t:s0 398 Jun
>> 21 01:35
>> authorized_keys
>
> Interesting, I have home_root instead of ssh_home. What does that
> mean? Does it mean that I created the .ssh directory as root, then
> chown it which is possible?
> I am totally una
> I still can't reproduce doing it this way on a new VM. How about checking
> the
> selinux contexts?
>
> [egreshko@f26-b14 .ssh]$ ll -Z *
> -rw---. 1 egreshko egreshko unconfined_u:object_r:ssh_home_t:s0 398 Jun
> 21 01:35
> authorized_keys
> -rw---. 1 egreshko egreshko unconfined_u:o
On 06/20/17 23:51, Frédéric Bron wrote:
>> OK. The only other way I could reproduce the error is if the key that
>> was
>> copied into authorized_keys isn't the correct key for the sending system or
>> if I
>> managed to copy into authorized_keys in such a way that it was mangled. For
>>
> Are the systems that work older systems? They recently
> changed sshd to disable a lot of older encryption
> and hash algorithms and wot-not. Perhaps it doesn't
> like your old keys?
no because I regenerated the key and got the same result.
I wonder if the users need to be part of a group to be
On Tue, 20 Jun 2017 16:24:59 +0200
Frédéric Bron wrote:
> Same error from another computer targeting this one.
Are the systems that work older systems? They recently
changed sshd to disable a lot of older encryption
and hash algorithms and wot-not. Perhaps it doesn't
like your old keys?
_
> How many key pairs do you have in .ssh? Is this the only one?
only one.
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
On Jun 20, 2017 17:52, "Frédéric Bron" wrote:
> OK. The only other way I could reproduce the error is if the key
that was
> copied into authorized_keys isn't the correct key for the sending system
or if I
> managed to copy into authorized_keys in such a way that it was mangled.
For example,
> OK. The only other way I could reproduce the error is if the key that
> was
> copied into authorized_keys isn't the correct key for the sending system or
> if I
> managed to copy into authorized_keys in such a way that it was mangled. For
> example,
> each key needs to be on a single li
thanks for looking at it.
> OK. The only other way I could reproduce the error is if the key that
> was
> copied into authorized_keys isn't the correct key for the sending system or
> if I
> managed to copy into authorized_keys in such a way that it was mangled. For
> example,
> each key
On 06/20/17 22:55, Ed Greshko wrote:
> Going to try a few more things before I retire.
OK. The only other way I could reproduce the error is if the key that was
copied into authorized_keys isn't the correct key for the sending system or if I
managed to copy into authorized_keys in such a wa
On 06/20/17 22:48, Frédéric Bron wrote:
>> If you have in your sshd_config
>> PasswordAuthentication no
> yes, I have that
>
>> and your ~/.ssh/authorized_keys file set to allow group or other access in
>> any way
>> you will get that error.
>> Set to 600 which is -rw---. and it should be fi
> If you have in your sshd_config
> PasswordAuthentication no
yes, I have that
> and your ~/.ssh/authorized_keys file set to allow group or other access in
> any way
> you will get that error.
> Set to 600 which is -rw---. and it should be fine.
authorized_keys, id_rsa and id_rsa.pub are
On 06/20/17 22:24, Frédéric Bron wrote:
> I have installed the sshd service but cannot do
> ssh localhost
> because I get the following error:
> Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
>
> Same error from another computer targeting this one.
If you have in your sshd_config
Pa
I have installed the sshd service but cannot do
ssh localhost
because I get the following error:
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Same error from another computer targeting this one.
The strange thing is that I have exactly the same sshd_config file and
.ssh directory (
17 matches
Mail list logo
