| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 2 Dec 2007 12:36:09 +0100 From: Pavel Machek <pavel@....cz> To: David Brownell <david-b@...bell.net> Cc: rtc-linux@...glegroups.com, kernel list <linux-kernel@...r.kernel.org>, Alessandro Zummo <alessandro.zummo@...ertech.it> Subject: Re: RTC wakealarm write-only, still has 644 permissions Hi! > > > It's not an issue of accidental writes, it's an issue of there being > > > no other synchronization for setting those alarms. Remember that both > > > RTC_WKALM_SET and RTC_ALM_SET ioctls can set that same alarm, and so > > > could a different userspace activity ... > > > > We have 3 interfaces to one hardware resource. I do not think kernel > > should try to arbitrate it here. There's just one alarm clock with > > three interfaces. > > Having three interfaces is bad enough ... ensuring that none of > them can ever be used safely would be stupid. They can be used safely. You just have to pick one and stay with it. (And no, no-clobber hack does not help here. Or do you have specific application where no-clobber hack helps?) Anyway, with wildcarded dates, no-clobber is a problem -- because you need to kill the alarm after you waken up, or it will repeat. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists