On 2019-11-28 20:21, Jakub Jelen wrote:
On Wed, 2019-11-27 at 13:47 +0100, Jouk Jansen wrote:
> Jakub Jelen wrote on 27-NOV-2019 13:20:25.09
>
>> On Tue, 2019-11-26 at 13:27 +0100, Jouk Jansen wrote:
> [snip]
>>> Question : why does is work with just running "/usr/sbin/sshd"
>>> but
>>> not with
>>> "systemctl start sshd" ?
>> This sounds like an issue with selinux permissions on the
>> authorizied
>> keys file or path to it. Configure sshd to run in debug mode by
>> setting
>> LogLevel DEBUG3 in sshd_config, restart the service and retry. The
>> logs
>> will show up in journal and in /var/log/secure pointing the reason
>> why
>> your key was rejected.
> You are right. I switched selinux off (setenforce 0) and the problem
> is
> gone. I could not find an entry in the journalctl -e output (but
> maybe I
> overlooked (too many records)). Perhaps I should look in the selinux
> logs,
> but where do I find them?
Hello.
I would start with sshd logs as I described above. The selinux denials
are in /var/log/audit/audit.log but they sometimes do not give enough
information what is wrong.
If you're suggesting this to be a permission issue on authorized_keys wouldn't it
be a good
idea to request the output of "ls -Z ~/.ssh"?
--
The key to getting good answers is to ask good questions.