public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why are these files restricted?
Date: Wed, 13 Dec 2017 20:10:46 -0500	[thread overview]
Message-ID: <fb8431d5-0504-4b3d-6f94-cbe278c38fbb@gentoo.org> (raw)
In-Reply-To: <20171211011039.ezxodvs2lerl6jpf@matica.foolinux.mooo.com>

On 12/10/2017 08:10 PM, Ian Zimmerman wrote:
> $ for f in /etc/at/at.deny /etc/cron.hourly/0anacron
> /etc/default/useradd ; do
>   ls -l $f ; qfile $f ;
> done
> -rw-r----- 1 root at 166 Dec 10 16:57 /etc/at/at.deny
> sys-process/at (/etc/at/at.deny)
> -rwxr-x--- 1 root root 392 Nov  4 21:04 /etc/cron.hourly/0anacron
> sys-process/cronie (/etc/cron.hourly/0anacron)
> -rw------- 1 root root 96 Aug 14 10:57 /etc/default/useradd
> sys-apps/shadow (/etc/default/useradd)
> 
> None of these seem sensitive to me, and restricting them like this looks
> like a case of SBO.

I realized that you meant "security by obscurity" after a while, but the
first google result is "small bowel obstruction" =P

It's probably just the principle of least privilege in play. If no one
other than root needs to read those files, then no one other than root
should be able to read those files. The at.deny and default/useradd
files might be overkill, but I would still rather be safe than sorry.

But for anacron: people are stupid enough to put passwords in there.


      reply	other threads:[~2017-12-14  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11  1:10 [gentoo-user] Why are these files restricted? Ian Zimmerman
2017-12-14  1:10 ` Michael Orlitzky [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb8431d5-0504-4b3d-6f94-cbe278c38fbb@gentoo.org \
    --to=mjo@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox