From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: [9fans] permissions in /net
Date: Sat, 7 Oct 2006 16:18:07 +0200 [thread overview]
Message-ID: <972a21167c992073583e2b9c9da37ffe@voidness.de> (raw)
I found the files 'iproute' and 'arp' to be without any write
protection. While it was easy to restrict write permissions to the
hostowner[1], I am not completely sure if that would break something
on other people's systems.(?)
For instance, ip/rip needs to write to 'iproute'. I'm guessing it is
common use to run it as hostowner, guessing right?
BTW: Do you consider write access to 'log' critical as well?
Heiko
[1] 'eve' stands for the hostowner in the kernel's terminology,
doesn't she?
reply other threads:[~2006-10-07 14:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=972a21167c992073583e2b9c9da37ffe@voidness.de \
--to=heiko.dudzus@gmx.de \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).