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: <c5df85930908300412lc2f334dle4502492b25827f5@mail.gmail.com>
Date:	Sun, 30 Aug 2009 12:12:42 +0100
From:	James Youngman <jay@....org>
To:	Eric Blake <ebb9@....net>
Cc:	linux-kernel@...r.kernel.org, bug-coreutils <bug-coreutils@....org>
Subject: Re: [RFC] new open flag O_NOSTD

On Mon, Aug 24, 2009 at 1:22 PM, Eric Blake<ebb9@....net> wrote:
> The name proposed in this mail is O_NOSTD (implying that a successful
> result will not be any of the standard file descriptors); other ideas
> mentioned on the bug-gnulib list were O_SAFER, O_NONSTD, O_NOSTDFD.
> http://lists.gnu.org/archive/html/bug-gnulib/2009-08/msg00358.html
>
> Thoughts?

Mostly yes,  I like it.

I'd like to explicitly vote against O_SAFER, because there may be (for
some systems or in the future) some other way of making open(2) safer.
  I'd vote positively for O_NOSTDFD or O_NOSTD.

James.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ