Great Circle Associates Firewalls
(September 1992)
 

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

Subject: SUMMARY: Why allow incoming telnet?
From: Frederick M. Avolio <avolio @ dco . dec . com>
Date: Tue, 29 Sep 92 09:15:49 -0400
To: firewalls @ GreatCircle . COM
In-reply-to: Your message of Tue, 29 Sep 92 08:15:03 -0400. <m0mZgVp-001dnuC @ pilot . dmg . ml . com>

I won't go into our screened gateway as it is described in papers already pointed
to (decuac.dec.com:/pub/docs/firewall/*).  For people needing telnet access
from the outside, we use a Digital Pathways, Inc encryption device 
(Mtn View, CA) -- although other companies make similar boxes I am sure --
and a server on the internal net which provides the external gateway with the
authentication challenge for the person trying to log in.  Once authenticated
the user gets attached to a process which would allow access to internal nodes
(where they would then need their passwords, etc.),

F



Follow-Ups:
References:
Indexed By Date Previous: Re: SUMMARY: Why allow incoming telnet?
From: "Jon S. Stumpf" <jss @ sysdev . dmg . ml . com>
Next: Re: X and firewalls
From: Amos Shapira <amoss @ cs . huji . ac . il>
Indexed By Thread Previous: Re: SUMMARY: Why allow incoming telnet?
From: "Jon S. Stumpf" <jss @ sysdev . dmg . ml . com>
Next: Re: SUMMARY: Why allow incoming telnet?
From: Michael Reilly / Network Systems Lab (NSL) <reilly @ PA . DEC . COM>

Google
 
Search Internet Search www.greatcircle.com