Date: Sun, 09 Jul 2017 14:07:06 +0000 From: Johannes Lundberg <johalun0@gmail.com> To: Stefan Ehmann <shoesoft@gmx.net> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Getting PID of socket client Message-ID: <CAECmPwt0Un076DT8SHVDFi-ygdfqOWU6hH1cHejn0vNmr4A9Jg@mail.gmail.com> In-Reply-To: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> References: <CAECmPwsD=PYqoG9EA=Wyq16hcrdbf7SQ3Owxdf%2BWSvYWazJfXA@mail.gmail.com> <a42d8db6-675f-b021-fc50-6ef87d310623@gmx.net> <CAECmPwuAm%2Bn6DyFR01OgatxN9Jj3um-50jOpP0jeB4=N%2Bj=yxg@mail.gmail.com> <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
That code gets the child's pid from the fork command. That's is not available in my case (Wayland client connects to Wayland server via unix socket). I can understand the security issue.. hmm will dig further tomorrow.. Thanks for the info! On Sun, 9 Jul 2017 at 15:26, Stefan Ehmann <shoesoft@gmx.net> wrote: > On 09.07.2017 11:52, Johannes Lundberg wrote: > > Hi > > > > Yeah I forgot to mention the LOCAL_CREDS. > > It does not return the PID of the client process but i guess it could be > > expanded to include that instead of adding another option for that. > > I was only skimming the man page. Didn't see that cmsgcred contains the > PID, but sockcred does not. Of course the PID in my sample output is > also wrong (the UID is printed instead of the PID): > > > $ ./unixstrserv02 > > PID of sender = 1001 > > Don't why the structs are not compatible, maybe because: > "The process ID cmcred_pid should not be looked up (such as via the > KERN_PROC_PID sysctl) for making security decisions. The sending > process could have exited and its process ID already been reused for a > new process." > > According to the commit log LOCAL_CREDS was obtained from NetBSD but I > didn't investigate further. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAECmPwt0Un076DT8SHVDFi-ygdfqOWU6hH1cHejn0vNmr4A9Jg>