full-disclosure - Re: TTY handling when executing code in lower-privileged context (su, virt containers)

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] [day] [month] [year] [list]

Message-ID: <CALx_OUBPZ404v+ibEcQrvxpdWL26233FS=MmZKgNpinigPe-8w@mail.gmail.com>
Date: Sun, 11 Nov 2012 09:51:26 -0800
From: Michal Zalewski <lcamtuf@...edump.cx>
To: Jerry Bell <jerry@...kologist.com>
Cc: Full-Disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: TTY handling when executing code in
 lower-privileged context (su, virt containers)

The only thing I am saying is that when you have a choice between
direct root logins and using sudo / su, telling people to use the
latter option for "security reasons" actually makes them worse off.

Poor corporate security practices, schizophrenic account lockout
policies, or dealing with "hundreds of administrators" on a single box
are completely tangential to that (though you can have as many uid 0
accounts as you want).

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