linux-kernel - Re: RTC wakealarm write-only, still has 644 permissions

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071003021537.208621F9CA8@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
Date:	Tue, 02 Oct 2007 19:15:36 -0700
From:	David Brownell <david-b@...bell.net>
To:	pavel@....cz
Cc:	rtc-linux@...glegroups.com, linux-kernel@...r.kernel.org,
	alessandro.zummo@...ertech.it
Subject: Re: RTC wakealarm write-only, still has 644 permissions

> > > > root@amd:/sys/class/rtc/rtc0# cat wakealarm 
> > > > root@amd:/sys/class/rtc/rtc0# echo 132719 > wakealarm 
> > 
> > At which point I'd expect
> > 
> > # echo $?
> > 
> > would indicate the write failed.  That's a LONG time in the
> > past (January 2, 1970), so that setting would be rejected.
>
> echo $? says 0 here :-(.

I stand corrected.  What it should do -- and does -- in that case
involves disabling the alarm, then succeeding.

-
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/