Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 May 2016 17:08:47 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 176419] [kernel] [patch] socketpair support for LOCAL_PEERCRED
Message-ID:  <bug-176419-2472-keGiWMbrpm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-176419-2472@https.bugs.freebsd.org/bugzilla/>
References:  <bug-176419-2472@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176419

Martin eto Misuth <eto.freebsd@ethome.sk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eto.freebsd@ethome.sk

--- Comment #2 from Martin eto Misuth <eto.freebsd@ethome.sk> ---
I think I hit this recently as well.

Man page contains wording:

     [ENOTCONN]         The argument s does not refer to a socket on which
                        connect(2) or listen(2) have been called.

Which actually describes situation exactly, but it is bit non-obvious that =
it
also means implicit exclusion of socktepair().

More over, as mentioned by nicholas, other system I tried (Linux) supports
getting this information about socketpair() created  sockets. I have not yet
tried OS X.

I wanted to use this to verify socket owner credentials (usually parent
process), before consuming data from it, in scripted environment.
Unfortunately, this feature can be used only when I go through fs namespace=
. I
don't know how these "anonymous" sockets (created by socketpair()) are
implemented internally but, I think creating socket files in my situation is
kinda wasteful.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-176419-2472-keGiWMbrpm>