Re: unix domain socket security and PID retrieval

2008-02-05 Thread Zane C.B.
On Mon, 4 Feb 2008 15:36:30 +0100 Heiko Wundram (Beenic) [EMAIL PROTECTED] wrote: Am Montag, 4. Februar 2008 15:21:52 schrieb Zane C.B.: I've come across that mentioned in unix(4). There is no support for it in regards to Perl. Another problem is it requires support for that on both ends.

Re: unix domain socket security and PID retrieval

2008-02-05 Thread Heiko Wundram (Beenic)
Am Dienstag, 5. Februar 2008 15:28:26 schrieb Zane C.B.: snip As far as I understand the code you've written, that won't work, because you're tying to send/receive the ancilliary messages as socket data, and not as a separate message. Additionally, I don't program any Perl (left that for good

Re: unix domain socket security and PID retrieval

2008-02-05 Thread Heiko Wundram (Beenic)
Am Dienstag, 5. Februar 2008 15:28:26 schrieb Zane C.B.: snip And, on another note, you might be interested in /usr/src/lib/libc/gen/getpeereid.c which implements a function that (internally) uses a socket option (no need to mess with ancilliary messages) to retrieve the value you're looking

unix domain socket security and PID retrieval

2008-02-04 Thread Zane C.B.
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? As it currently stands, I am looking at doing this with perl.

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Zane C.B.
On Mon, 4 Feb 2008 05:33:22 -0600 (CST) Scott Bennett [EMAIL PROTECTED] wrote: On Mon, 4 Feb 2008 04:30:21 -0600 Zane C.B. [EMAIL PROTECTED] 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

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Heiko Wundram (Beenic)
Am Montag, 4. Februar 2008 15:21:52 schrieb Zane C.B.: I've come across that mentioned in unix(4). There is no support for it in regards to Perl. Another problem is it requires support for that on both ends. More and more it looks like getting either PID and/or user info about the other

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Zane C.B.
On Mon, 4 Feb 2008 12:54:44 +0100 Heiko Wundram (Beenic) [EMAIL PROTECTED] wrote: Am Montag, 4. Februar 2008 11:30:21 schrieb Zane C.B.: 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

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Heiko Wundram (Beenic)
Am Montag, 4. Februar 2008 11:30:21 schrieb Zane C.B.: 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? As it

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Scott Bennett
On Mon, 4 Feb 2008 04:30:21 -0600 Zane C.B. [EMAIL PROTECTED] 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?

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Zane C.B.
On Mon, 4 Feb 2008 15:36:30 +0100 Heiko Wundram (Beenic) [EMAIL PROTECTED] wrote: Am Montag, 4. Februar 2008 15:21:52 schrieb Zane C.B.: I've come across that mentioned in unix(4). There is no support for it in regards to Perl. Another problem is it requires support for that on both ends.

Re: unix domain socket security and PID retrieval

2008-02-04 Thread Zane C.B.
On Mon, 4 Feb 2008 13:38:37 -0600 Zane C.B. [EMAIL PROTECTED] wrote: On Mon, 4 Feb 2008 15:36:30 +0100 Heiko Wundram (Beenic) [EMAIL PROTECTED] wrote: Am Montag, 4. Februar 2008 15:21:52 schrieb Zane C.B.: I've come across that mentioned in unix(4). There is no support for it in