Re: Proposing Fedora Feature for private /tmp and /var/tmp for all systemd services in Fedora 17.

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

 



Once upon a time, Gregory Maxwell <gmaxwell@xxxxxxxxx> said:
> On Mon, Nov 7, 2011 at 10:00 PM, Chris Adams <cmadams@xxxxxxxxxx> wrote:
> > Well, if they're subdirectories of /tmp, you'd have to deal with all the
> > usual /tmp attacks of known targets.
> 
> Hmph? They wouldn't be accessible to anything except root I assume.
> 
> Because they're long lived the random names shouldn't provide much
> protection— and certainly not much more than partially random names
> would provide. Or am I missing something?

What if a service is only started on demand?  Are /tmp directories
recreated on a service restart?  In either case, there'd be a point
where the /tmp subdirectory wouldn't exist; a user could log in and
create their own directory, a symlink, etc.

How does systemd handle the case where the desired subdirectory already
exists?  If you use a static subdirectory name, an unclean shutdown
would leave the directories.  Does systemd delete/re-create them or use
existing?  In either case, users playing tricks could be a problem.
-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux