ust to
>>> keep services tidy and separated. Some of these have to connect to ssh
>>> servers, therefore they require a .ssh/known_hosts. /etc/security thinks
>>> this is a security risk and complains about it every night...
>> I think the basic idea makes sense.
>&g
ave to connect to ssh
> > servers, therefore they require a .ssh/known_hosts. /etc/security thinks
> > this is a security risk and complains about it every night...
>
> I think the basic idea makes sense.
>
> The file name still in use for backward compatibility,
> ".ssh
Tobias Ulmer wrote on Sun, Feb 21, 2010 at 02:36:43AM +0100:
> I've got a bunch of "users" with no password/no way to log in, just to
> keep services tidy and separated. Some of these have to connect to ssh
> servers, therefore they require a .ssh/known_hosts. /etc/sec
I've got a bunch of "users" with no password/no way to log in, just to
keep services tidy and separated. Some of these have to connect to ssh
servers, therefore they require a .ssh/known_hosts. /etc/security thinks
this is a security risk and complains about it every night...
Inde
Hi Daniel,
> /etc/security complains about the lost+found directory in /var/mail.
> Here is a diff to ignore a lost+found named directory in /var/mail:
Umm, i'm not convinced ignoring debris left over from file system repair
in /var/mail is a sane default. Being reminded to clean
Hi!
/etc/security complains about the lost+found directory in /var/mail. Here is a
diff to ignore a lost+found named directory in /var/mail:
--- security.orig Wed Aug 13 00:51:28 2008
+++ securitySun Nov 1 09:04:48 2009
@@ -434,7 +434,7 @@
fi
# Mailboxes should be owned by user and