Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Pen-Test
[Top] [All Lists]

RE: VPN protocols

Subject: RE: VPN protocols
Date: Wed, 22 Dec 2004 14:21:56 -0500
GRE and ESP are IP Protocols.

On nearly all modern firewalls you specify the ip transport [esp, ah, gre, 
other] between the two networks. Conduits for the msot part are being phased 
out so on an IOS device or PIX the line would be something like this when 
configured correctly

access-list ingress permit esp host <remote-host-ip> host <local-ip>
access-list ingress permit udp host <remote-host-ip> host <local-ip> eq 500

this will permit most IPSEC vpns to work between two permitted termination 
points. permitting all hosts to transport vpn traffic is not the best design. 
Doing so helps pentesters and blackhat gain more information on your device 
configuration than they need.

-keith

-----Original Message-----
From: John Forristel (SunGard-Chico)
[mailto:John.Forristel@sungardbi-tech.com]
Sent: Wednesday, December 22, 2004 12:04 PM
To: Dan Tesch; Pen Test
Subject: RE: VPN protocols


GRE and ESP are protocols, not ports, so they are transported through on
configured ports.  In Cisco, you permit gre and esp through for the VPN
traffic.

In a conduit statement:

conduit permit esp any any
conduit permit esp any any

notice that there is no tcp, udp, or ip in the permit statement.

I've noticed that, on some firewalls, it is buried deep in the bowels of
the config, and has timeouts set to drop the protocol after so many
minutes.




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