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. |

| Subject: | Limiting SSH reverse tunnels? |
|---|---|
| Date: | Sat, 24 Sep 2005 07:19:20 -0700 |
Forgive me if this is a stupid question, but I’ve been banging my head against it and the archives for a while now.
Several people have figured out the joys of reverse tunneling, and are now using SSH tunnels to bypass the corporate VPN get into the office using tunnels they set up in advance for that purpose.
I don’t want to disable SSH tunneling completely; it’s actually quite important that users be able to, say, tunnel an rsync connection through to a machine at the data center. I don’t want them getting into the office that way, though.
Is there a way to stop SSH from allowing this? Maybe a way to deny reverse tunneling to office IP address space?
Reiterating the corporate policy ain’t working.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | sshd as non root, Ben Ford |
|---|---|
| Next by Date: | ForwardX11Trusted option not working, openssh . overbored |
| Previous by Thread: | sshd as non root, Ben Ford |
| Next by Thread: | ForwardX11Trusted option not working, openssh . overbored |
| Indexes: | [Date] [Thread] [Top] [All Lists] |