Been running, testing, re-installing and rebooting a lot of times since
my post above.
I've noted that in
/etc/cron.daily/spamassassin
there is umask 022 to updated the spam assassin rules, and consistently
"the system" will fail to install or fall over if login.defs is changed
to 027 on reboot
Been running, testing, re-installing and rebooting a lot of times since
my post above.
I've noted that in
/etc/cron.daily/spamassassin
there is umask 022 to updated the spam assassin rules, and consistently
"the system" will fail to install or fall over if login.defs is changed
to 027 on reboot
[SOLVED] (possibly I don't want to appear too arrogant on my first post
:)
I updated my 12.04 to 14.04 with no problems and then recently I decided
to increase my security with various tools like tripwire, ,tiger and
lynis and one of the "recommendations" was to tighten up the security on
gcc
[SOLVED] (possibly I don't want to appear too arrogant on my first post
:)
I updated my 12.04 to 14.04 with no problems and then recently I decided
to increase my security with various tools like tripwire, ,tiger and
lynis and one of the "recommendations" was to tighten up the security on
gcc
