Easy

Post #43,631 by deSitter 6/27/02 11:17:03 AM Reply	Easy From the "Dynamic IP Hacks" howto: It would be nice to be able to get access to my work machine (Sun) from home, and vice versa, yet telnet is firewalled at work. Here's a way around it. For purposes of this explanation I'll give the method for gaining access to my work machine from my home Linux machine, with a dial-up PPP connection to my ISP and dynamic IP assignment. From home, when I want access to my work machine, I dial-in and fire up X, set "xhost +", determine my dynamic IP, and email my dynamic IP to my work machine in a mail message with a particular format. On my work machine I have a procmail recipe/script setup that parses the body of a message whose subject matches a target, say "X-W". If the body of that message meets certain requirements then it extracts the IP from the message and spawns an xterm with the display directed to my home dynamic IP like this: xterm -display my.ip.i.sent:0.0 -e login Voila! In about 30 secs to a minute, an xterm login shell appears on my home machine! I haven't tried going the other direction yet because my home machine isn't on full time, but using the other methods of determining the dynamic IP from a remote machine it should work the same way. Now assuming you can sneak in a few VNC servers (corporate security is so braindead that this should be easy) you are on Windows and the games can begin. You could slip in a UNIX box with a direct crossover connection and the appropriate routing to your Windows work box without anyone suspecting much. Just "accidentally" leave your laptop at work. -desitter
Post #43,650 by pwhysall 6/27/02 1:09:46 PM Reply	Blimey. Your company leaves port 6000 open? Wonders will never cease. Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #43,673 by deSitter 6/27/02 3:10:24 PM Reply	Not Mine! But you'd be surprised how porous corporate nets are. -desitter
Post #43,708 by orion 6/27/02 9:24:14 PM Reply	Depends on the people running them if they are just learning how to run a network or are former PHBs turned Network Administrators, then the security will be weak. Like the lawfirm I used to work for, someone ran a password cracker, and I noticed the database on a shared drive full of passwords, and apparently nobody seemed to care that it existed or that someone has a list of password from most of the user accounts, including administrators. They also didn't seem concerned with applying the latest patches and kept SP4 on the NT 4.0 Servers when SP6.1 was out. They used a Linux server for a firewall, but I think someone else set it up for them. I'd give out their address and domain name, but I don't want someone to hack them and then point a finger back at my post listing the address to go at. *I am free now, to choose my own destiny.*
Post #43,730 by ben_tilly 6/28/02 1:38:03 AM Reply	Well if they don't... It is amazing how many will instead leave outbound on 80 open. Given the knowledge at home of how to create a tunnel (not hard - just look in ssh's documentation) it is trivial to hijack that to send your X display home. Cheers, Ben "... I couldn't see how anyone could be educated by this self-propagating system in which people pass exams, teach others to pass exams, but nobody knows anything." --Richard Feynman

Welcome to IWETHEY!