Bug#337279: yaird: /boot != /tmp
Sven Luther wrote:
> because i was thinking that the problem happened during boot time, and since
> there where issues of read-only filesystems. ...
This is definitely at creation time.
>
> BTW, erik, i am not sure to have the files in non-/tmp will help
> security-wise, since it will only protect from people looking after the exact
> yaird behavior, and knowing about the situation.
Messages sent to 337279@bugs.debian.org are not cc'd to me (this isn't
aimed at you, Sven; rather the other people who have commented in the
BTS). You have to send to 337279-submitter@bugs.debian.org or me
directly... Darn you BTS!
A lot of the standard /tmp races don't apply to yaird because yaird uses
mkdir, not open. Concerns about races w/ tmpreaper are also not an
issue, because yaird is run with admin supervision; certainly, if the
admin does not notice someone slowing his system so that yaird runs for
days so that tmpreaper decides to remove yaird's tmpdir then, well, he
deserves what he gets.
And, for the record, I (the admin) did not decide to use /boot as a
temporary directory. Using TMPDIR is fine, but when its not set, the
default should be /tmp, because that's the way Unix programs are
supposed to work.
Reply to: