DragonFly bugs List (threaded) for 2007-01
DragonFly BSD
DragonFly bugs List (threaded) for 2007-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: at/batch broken


From: "Thomas E. Spanjaard" <tgen@xxxxxxxxxxxxx>
Date: Sun, 07 Jan 2007 09:22:00 +0000

YONETANI Tomokazu wrote:
The problem: at or batch command fails to accept a new schedule
because it fails to create a lock file /var/at/jobs/.lockfile.
The bug exists in 1.4/1.6 releases too.

I remember having to touch the .lockfile and .SEQ before being able to use at(1) as well, on at least as early as 1.3.


The root cause is, as I posted in that thread, second call to setreuid()
fails if you don't close a file descriptor you opened right after the
first call to setreuid(real_uid, effective_uid) with the same argument
fails, whether you close the descriptor or not.  I'm attaching the sample
code again.  It fails on DragonFly, but succeeds on FreeBSD.  I looked
around in the kernel code but I couldn't find any description that it's
a security feature specific to DragonFly.

No idea, but I also haven't looked at any code...


Cheers,
--
        Thomas E. Spanjaard
        tgen@netphreax.net

Attachment: signature.asc
Description: OpenPGP digital signature



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]