Great Circle Associates Firewalls
(July 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: How secure is xinetd's binding to specific interfaces
From: "Sean Fuller" <c60201 @ zone . arnold . af . mil>
Date: Wed, 31 Jul 1996 09:13:03 -0500
To: firewalls @ GreatCircle . COM
In-reply-to: <firewalls-owner @ GreatCircle . COM>
References: <838769821TueCDT . firewalls-owner @ GreatCircle . COM>

On Jul 30,  6:37pm, <firewalls-owner @
 GreatCircle .
 COM> wrote:
> Well, I have looked a little at xinetd's code, but I think it's pretty
> secure.  Basically, it probably does a getsockname() on incoming
> connections to find out what interface they are coming in on.

getsockname!  Thanks so much for pointing out this wonderful routine.
I don't know why I never saw it before.  I guess I learned firewall
programming from the TIS Firewall Toolkit and I never saw this routine
used to detect the incoming interface.  I've always used getpeername
to find out where a request is coming from, and then filter based on
subnet (along with anti-spoofing filtering on the external router).
I could kick myself.  Oh well, you learn something new every day.



Indexed By Date Previous: Re: Sidewinder Versus EagleRaptor
From: peter @ baileynm . com (Peter da Silva)
Next: Re: paying for unsolicited messages.
From: Michael Jarvis <michaelj @ burrito . insource . com>
Indexed By Thread Previous: Re: binding to specific interfaces
From: Zachary Roger Amsden <amsden+ @ andrew . cmu . edu>
Next: Re: How secure is xinetd's binding to specific interfaces
From: Chuck Murcko <chuck @ telebase . com>

Google
 
Search Internet Search www.greatcircle.com