From owner-freebsd-questions@FreeBSD.ORG Mon Feb 4 20:17:08 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1DF816A419 for ; Mon, 4 Feb 2008 20:17:08 +0000 (UTC) (envelope-from SRS0=0IHuIv=SZ=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout04.yourhostingaccount.com (mailout04.yourhostingaccount.com [65.254.253.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8BAC213C455 for ; Mon, 4 Feb 2008 20:17:08 +0000 (UTC) (envelope-from SRS0=0IHuIv=SZ=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan01.yourhostingaccount.com ([10.1.15.1] helo=mailscan01.yourhostingaccount.com) by mailout04.yourhostingaccount.com with esmtp (Exim) id 1JM7kZ-00077K-Cf for freebsd-questions@freebsd.org; Mon, 04 Feb 2008 15:17:07 -0500 Received: from impout02.yourhostingaccount.com ([10.1.55.2] helo=impout02.yourhostingaccount.com) by mailscan01.yourhostingaccount.com with esmtp (Exim) id 1JM7kY-0008Pv-Si; Mon, 04 Feb 2008 15:17:06 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9]) by impout02.yourhostingaccount.com with NO UCE id lYFw1Y00A0BkWne0000000; Mon, 04 Feb 2008 15:15:56 -0500 X-EN-OrigOutIP: 10.1.18.9 X-EN-IMPSID: lYFw1Y00A0BkWne0000000 Received: from c-98-206-161-17.hsd1.il.comcast.net ([98.206.161.17] helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1JM7jL-0006Zr-Ch; Mon, 04 Feb 2008 15:15:51 -0500 Date: Mon, 4 Feb 2008 14:16:33 -0600 From: "Zane C.B." Message-ID: <20080204141633.07099349@vixen42> In-Reply-To: <20080204133837.3c3b3b67@vixen42> References: <20080204043021.1a8ee670@vixen42> <200802041254.44475.wundram@beenic.net> <20080204082152.2129c3c6@vixen42> <200802041536.30469.wundram@beenic.net> <20080204133837.3c3b3b67@vixen42> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 98.206.161.17 X-EN-OrigHost: c-98-206-161-17.hsd1.il.comcast.net Cc: "Heiko Wundram \(Beenic\)" , freebsd-questions@freebsd.org Subject: Re: unix domain socket security and PID retrieval X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2008 20:17:08 -0000 On Mon, 4 Feb 2008 13:38:37 -0600 "Zane C.B." wrote: > On Mon, 4 Feb 2008 15:36:30 +0100 > "Heiko Wundram (Beenic)" 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. > > > > > > More and more it looks like getting either PID and/or user info > > > about the other process connecting up to it is impossible, with > > > out writing some sort of authentication system for the two to > > > use or both ends have to support the LOCAL_CREDS stuff. > > > > I cannot believe that this doesn't exist for Perl (everything > > exists for Perl in one way or another...), and anyway, a quick > > search on CPAN found this, which looks as though it's (at least > > part of) what you're looking for: > > > > http://search.cpan.org/~mjp/Socket-MsgHdr-0.01/MsgHdr.pm > > > > Finally, thinking back to the last time I used SCM_CREDS on Linux > > (which is a loooong time ago), I'm not even sure that the sender > > has to send an SCM_CREDS message (which would invalidate my former > > reply); I think it's enough if the receiver requests to get one > > (which will be filled in by the kernel), see the description in > > the referenced page above which shows you how to set up the > > corresponding recvmsg call. > > > > Sending one is only required in case the sender is root and wants > > to spoof it's credentials to the remote process (IIRC). > > Thanks. I did not think to try a search for that. I was trying > various combinations involving the word unix and socket. > > I've gotten it installed now and will post with how it works out. I can say it installs mostly fine. A few tests do not pass. I am still working on getting a working test script with it.