From: devzero@web.de
To: Simon Arlott <simon@fire.lp0.eu>
Cc: Robert Hancock <hancockr@shaw.ca>, linux-kernel@vger.kernel.org
Subject: Re: System reboot triggered by just reading a device file....!?
Date: Thu, 22 Nov 2007 20:54:42 +0100 [thread overview]
Message-ID: <1614227@web.de> (raw)
since i have gotten more or less similar answers from here, i have talked to some more people privately.
the result is interesting:
if the person i talked to was some sysadmin or related to that (i.e. some person running servers), his opinion was very similar to mine.
if the person was a developer, he didn`t really understand why i have a problem with that. "be careful if you are root" was what i got.
one of the admins gave a good statement, which i liked very much and want to share:
"even if you are root: it`s unix philosophy, that reading is harmless!"
i never thought about that, but i think that`s exactly the point and that`s why i`m feeling uncomfortable with that.
anyway - it cost me some time to find a bug which was none and the only mistake i did was using a tool for which i was sure did nothing more than reading. so why should i care that i was root ?
need to change my own philosophy now, because i learned that reading isn`t harmless. ;)
regards
roland
> -----Ursprüngliche Nachricht-----
> Von: "Simon Arlott" <simon@fire.lp0.eu>
> Gesendet: 21.11.07 13:30:05
> An: devzero@web.de
> CC: "Robert Hancock" <hancockr@shaw.ca>, linux-kernel@vger.kernel.org
> Betreff: Re: System reboot triggered by just reading a device file....!?
>
> On Wed, November 21, 2007 00:01, devzero@web.de wrote:
> >>There is.. it's called "root privileges".
> > yes, true.
> >
> > but - regardless of being a windows app or not - what if you want to take a look on your system as a whole,
> > especially when using some tool which graphically shows how and where your diskspace is being used? if i
> > let this run from ordinary useraccount it would get lot`s of "permission denied" and then it`s only telling
> > half of the truth.....
>
> Such a tool shouldn't need to open any files, whether they're device files or not. Do you expect it to open
> /dev/zero etc. too and read from an infinitely sized "file"?
>
> >> > i`d wish there would be some fence around this or iTCO_wdt /dev/watchdog not being active after a
> >> default desktop installation.
>
> Delete it?
>
> --
> Simon Arlott
>
______________________________________________________________________________
Jetzt neu! Im riesigen WEB.DE Club SmartDrive Dateien freigeben und mit
Freunden teilen! http://www.freemail.web.de/club/smartdrive_ttc.htm/?mc=021134
next reply other threads:[~2007-11-22 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 19:54 devzero [this message]
2007-11-22 20:42 ` System reboot triggered by just reading a device file....!? Clemens Koller
-- strict thread matches above, loose matches on Subject: below --
2007-11-22 21:22 devzero
2007-11-21 0:01 devzero
2007-11-21 12:29 ` Simon Arlott
[not found] <fa.NKMd2cOUI5zSAFh0xiVy3hZdy3s@ifi.uio.no>
2007-11-20 23:34 ` Robert Hancock
2007-11-20 23:06 devzero
2007-11-20 23:51 ` Matt Mackall
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=1614227@web.de \
--to=devzero@web.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
/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