On Wed, 26 Dec 2012 21:44:15 +0100, Frantisek Hanzlik wrote:
> openssh-5.9p1 (-28.fc17) seems be patched by some
> openssh-5.9p1-sesandbox.patch
> which hardly print this message (if selinux disabled):
>
> ...
> diff -up openssh-5.9p1/openbsd-compat/port-linux.c.sesandbox
> openssh-5.9p1/openbs
Reindl Harald wrote:
>
>
> Am 25.12.2012 10:34, schrieb Michael Schwendt:
>> On Tue, 25 Dec 2012 04:34:13 +0100, Reindl Harald wrote:
>>
>>> is it possible on systems with selinux completly disabled to
>>> get rid of this messages in /var/log/secure everytime a
>>> ssh-session is opened?
>>>
>>>
On Wed, 26 Dec 2012 18:42:39 +0100, Reindl Harald wrote:
>
>
> Am 25.12.2012 10:34, schrieb Michael Schwendt:
> > On Tue, 25 Dec 2012 04:34:13 +0100, Reindl Harald wrote:
> >
> >> is it possible on systems with selinux completly disabled to
> >> get rid of this messages in /var/log/secure every
Am 25.12.2012 10:34, schrieb Michael Schwendt:
> On Tue, 25 Dec 2012 04:34:13 +0100, Reindl Harald wrote:
>
>> is it possible on systems with selinux completly disabled to
>> get rid of this messages in /var/log/secure everytime a
>> ssh-session is opened?
>>
>> Dec 25 04:33:28 localhost sshd[10
On Tue, 25 Dec 2012 04:34:13 +0100, Reindl Harald wrote:
> is it possible on systems with selinux completly disabled to
> get rid of this messages in /var/log/secure everytime a
> ssh-session is opened?
>
> Dec 25 04:33:28 localhost sshd[10980]: selinux sandbox not useful [preauth]
What you have
Am 25.12.2012 04:51, schrieb Tom Horsley:
> On Tue, 25 Dec 2012 04:34:13 +0100
> Reindl Harald wrote:
>
>> is it possible on systems with selinux completly disabled to
>> get rid of this messages in /var/log/secure everytime a
>> ssh-session is opened?
>
> I don't know how to get rid of the sou
On Tue, 25 Dec 2012 04:34:13 +0100
Reindl Harald wrote:
> is it possible on systems with selinux completly disabled to
> get rid of this messages in /var/log/secure everytime a
> ssh-session is opened?
I don't know how to get rid of the source of the message,
but I have discovered the way to keep
192.168.2.2 port 45524 ssh2
Dec 25 04:33:28 localhost systemd-logind[898]: New session 393 of user root.
Dec 25 04:33:28 localhost sshd[10980]: pam_unix(sshd:session): session opened
for user root by (uid=0)
Logwatch:
**Unmatched Entries**
selinux sandbox not useful [preauth] : 211 time(s
