System reboot triggered by just reading a device file....!?
Quoted 1 line
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 lots of "permission denied" and then its only telling half of the truth.....
Quoted 3 lines
I'd say running pretty much anything through Wine as root is not a good idea, a Windows app could hose the system without even meaning to through exactly such things.
yes, true indeed. but maybe wine has an option to sandbox the windows app to do only r/o access. if that feature doesnt exist, (set r/o flag to dosdevices) maybe it would be an useful addon. but thats OT here....
Quoted 52 lines
-----Ursprüngliche Nachricht-----
Von: "Robert Hancock" <[email protected]>
Gesendet: 21.11.07 00:35:23
An: [email protected]
CC: [email protected]
Betreff: Re: System reboot triggered by just reading a device file....!?Quoted 14 lines · [email protected] wrote:
good evening,
i stumbled over some funny issue when trying windirstat (like KDirStat) with wine.
after running that tool for a while my system rebooted. i could reproduce this with every run.
after some deep investigation (i thought i had stability issues with my system and spent more than an hour on this) i found out, that the reboot is being triggered by
iTCO_wdt(/dev/watchdog)this is how to reproduce:
- be root
(quoted diff) +0
-2- cat /dev/watchdog or dd if=/dev/watchdog of=/dev/zero bs=1 count=1 or ..... - wait one minute........Quoted 3 lines
*reboot*!
i have heard 2 opinions for now (contacted the author and also discussed on wine-devel ) that this should be expected behaviour.
Yes, it is. It's a watchdog device, it's meant to reboot the machine if whatever task is poking the watchdog dies.
Quoted 3 lines
being sysadmin quite a while, i cannot believe that (accidentally) reading a device file (being root or not - what does that matter) triggers a system reboot.
ok - when i
m root , i shouldnt do stupid things and be careful, but i thought reading/crawling trough a filesystem (r/o, btw.) with some tool which is built to do exactly this wasn`t so stupid - even from within wine.I would say that running a Windows tool that opens up and reads random files, on the /dev directory tree, as root, probably does qualify as "stupid". I'd say running pretty much anything through Wine as root is not a good idea, a Windows app could hose the system without even meaning to through exactly such things.
Quoted 10 lines
think of an admin writing a quick&dirty script for intrusion detection (find / -exec md5sum {} \; >/tmp/need-no-tripwire) and forgetting to exclude /dev, /sys or /proc appropriately...... think of someone exporting "/" via samba (readonly) and then navigating trough the /dev directory....
stupid?
i don`t think so.....i have seen worse things...... :)should someone get punished by an accidental system reboot and should he need to spend his time on this to investigate why this happens?
i`d wish there would be some fence around this or
iTCO_wdt/dev/watchdognot being active after a default desktop installation.
Quoted 15 lines
There is.. it's called "root privileges".
Quoted 5 lines
i
d be interested if im the only one who thinks this is strange/dangerous behaviour.regards
rolandSignature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://produkte.web.de/club/?mc=021131
Quoted 7 lines · On Wed, November 21, 2007 00:01, [email protected] wrote:
Quoted 1 line
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 its 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"?
Quoted 2 lines
Quoted 2 lines
Quoted 1 line
i`d wish there would be some fence around this or
iTCO_wdt/dev/watchdognot being active after adefault desktop installation.
Delete it?
Signature · 1 line
Simon Arlott