Date: Mon, 4 Feb 2008 07:08:24 -0600 From: "Zane C.B." <v.velox@vvelox.net> To: Scott Bennett <bennett@cs.niu.edu> Cc: freebsd-questions@freebsd.org Subject: Re: unix domain socket security and PID retrieval Message-ID: <20080204070824.341a1bae@vixen42> In-Reply-To: <200802041133.m14BXMmW029486@mp.cs.niu.edu> References: <200802041133.m14BXMmW029486@mp.cs.niu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Feb 2008 05:33:22 -0600 (CST) Scott Bennett <bennett@cs.niu.edu> wrote: > > On Mon, 4 Feb 2008 04:30:21 -0600 "Zane C.B." > > <v.velox@vvelox.net> > >wrote: > >Been starting to look into writing some stuff that uses unix domain > >sockets, but I've been running into the problem of figuring out > >what the calling PID is on the other end. > > > >Any suggestions on where I should begin to look? > > Sure. Take a look at the man pages for fork(2), vfork(2), and > fork(3f). > > > >As it currently stands, I am looking at doing this with perl. > > In that case, take a look at perlfork(1), too. I am a bit lost on what fork has to do with the question. Currently have found there is no method for figuring what PID it is. I've found there is support for figuring out what user it is, according to unix(4), but there appears to way to get to using any of the existing perl modules for unix domain sockets.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080204070824.341a1bae>