full-disclosure - Re: Symlink vulnerabilities

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: <CALx_OUDqRLgfFDr4PBQG3UVX1h51A_zZiMdB6h5czJd7OhnmvA@mail.gmail.com>
Date: Fri, 21 Oct 2011 21:39:22 -0700
From: Michal Zalewski <lcamtuf@...edump.cx>
To: Valdis.Kletnieks@...edu
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Symlink vulnerabilities

> In any case, the *right* answer isn't to play whack-a-mole fixing /tmp races,
> what you should be doing is using pam_namespace or similar so each user gets
> their own /tmp namespace.

That would result in counterintuitive behavior, I suppose... /tmp is a
fairly stupid and largely unnecessary artifact of the old.

If you are in charge of a distro, it would not hurt to nuke it
altogether and change all packages in your control to use per-user
$TMPDIR. Some third-party stuff will break - but it breaks every now
and then anyway.

/mz

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/