IPfilter
[Top] [All Lists]

Re: auth keyword help

To: "French, David" <David_French@intuit.com>
Subject: Re: auth keyword help
From: Darren Reed <darrenr@reed.wattle.id.au>
Date: Mon, 07 May 2007 01:16:29 -0700
Cc: ipfilter@coombs.anu.edu.au
Delivered-to: sp-com-lists@consult.net
Delivered-to: ipfilter-list@securepoint.com
In-reply-to: <5473E12D51727749B7CCC087E473655004932BB2@SDGEXEVS03.corp.intuit.net>
References: <5473E12D51727749B7CCC087E473655004932BB2@SDGEXEVS03.corp.intuit.net>
Reply-to: darrenr@reed.wattle.id.au
Sender: owner-ipfilter@coombs.anu.edu.au
User-agent: Thunderbird 1.5.0.5 (Windows/20060719)
French, David wrote:
> Thanks.  I found ipfauth and I am looking at it now.  I also found
> userauth.c in the source samples directory.  
>
> One last question, I don't see anything that may specify what process
> and/or user a packet is associated with.  Is this information any place
> I could reference?  If not, is there any chance it may be added at some
> point?
>
> What I am trying to do here is setup an authentication daemon to
> allow/deny outgoing connections based on the user who initiated the
> packet.  It will check a configuration file/db to see what protocols,
> networks, etc a user can send packets to.
>   

That information isn't always available, so it isn't part of what IPFilter
makes available or uses.

However, because you're using a daemon to do this, there's no reason
why the daemon can't use tricks similar to [p]identd or lsof to find the
owner of the packet...so long as it is TCP/UDP.

Darren



<Prev in Thread] Current Thread [Next in Thread>