bindat(2) and connectat(2) syscalls for review.
Jilles Tjoelker
jilles at stack.nl
Sun Feb 17 22:26:03 UTC 2013
On Thu, Feb 14, 2013 at 11:08:53PM +0100, Pawel Jakub Dawidek wrote:
> bind(2) and connect(2) are used just fine currently without any flags.
> I'd like to see good example before I decide to add such argument. The
> AT_SYMLINK_NOFOLLOW flag is of no use here, it is used for syscalls that
> can operate on symlinks (you can chmod, chown or stat a symlink, so it
> does make sense there).
By that reasoning, the O_NOFOLLOW open flag should not exist.
However, it seems that it is uncommon to bind/connect to sockets located
in untrusted directories. Also, any flag could be implemented instead as
a setsockopt() on the socket.
--
Jilles Tjoelker
More information about the freebsd-arch
mailing list