Alright I got it all figured out
Ok I did all this while sitting at the computer behind the firewall. My home computer is just sitting there all innocent-like and has the mythical ip address of 123.123.123.123... Just for s**ts and giggles the computer I am sitting at (which is behind the stinken firewall) has the private address of 192.168.0.5. But this is unimportant. The following ain't the best way since I will be using root accounts, but it works.
Ok here I am at the bash prompt.
1st step: become root.
2nd: goto the /root/.ssh/ directory, if .ssh/ is missing, create it.
3. ssh from here to my home computer and and login as root. (which normally shouldn't be allowed, but right now it is
).
4. change to /root/.ssh on the remote(home) machine.
5. Now here is the fun part, we are gonna make a public/private keycode so we don't have to issue a password to use ssh no more. The command is:
root@home> ssh-keygen -t rsa
pick the defaults names (id_rsa) and don't put any keywords or anything, just leave the passphrase blank. That should generate 2 files. id_rsa, and id_rsa.pub
6. now we make the authorized key file by using the "id_rsa.pub" key that we just created.
root@home> cat id_rsa.pub >> authorized_keys
7. now we exit from the remote(home) server and go back to your desktop in front of you. And we use the "scp" command to pull down the id_rsa key that we need from your home machine. (like copy but uses ssh to cp from remote machines)
root@firewall'dcomputer> pwd
/root/.ssh/ (this is just to double check we are in the correct folder, that's all)
root@firewall'dcomputer> scp
root@123.123.123.123:/root/.ssh/id_rsa ./
8. now after we get the file we need to make sure that it works ok.
root@firewall'dcomputer> ssh -i /root/.ssh/id_rsa 123.123.123.123
Now you should of just automaticly logged in after a short pause, it shouldn't ask for a password or anything.
9. Now exit back to the firewall'd computer. Now the tricky part. We need to establish a ppp connection to the remote(home) computer to finish up.
root@firewall'dcomputer> pppd silent noauth 10.0.2.15:10.0.2.2 pty "ssh -i /root/.ssh/id_rsa -t 123.123.123.123 "pppd silent noauth 10.0.0.2.2:10.0.2.15""
*note that the 10.0.2.2 and the 10.0.2.15 are switched around the second time you type them and the double set of quotes at the end
10. now if that worked, double check your handywork. If you type in "ifconfig" you should see a new ppp0 connection with the ip address 10.0.2.2. Now with that ppp connection chugging into the background, go ahead and ssh into the home machine using the ip address 10.0.2.15. Now if you have the ppp stuff set up you can now ssh or ftp or telnet or whatever back down the pipe using the ip address 10.0.2.2 for the firewalled computer.
Now as long as that virtual private network stays functional you can run home and now can ftp, share files, telnet, X sessions, or whatever with the peace of mind that it's all being encrypted thru a ssh pipe, directly from home to school with no routers or firewalls or nothing standing in your way. Imagine telnet being secure! If you want to you can get fancy and setup the firewalled box as a router and now you have access to the entire firewalled network from home!
That's my little example of bypassing a secure firewall in ten relativly easy steps. Now in order to make it complete you are gonna have to put that ' root@firewall'dcomputer> pppd silent noauth 10.0.2.15:10.0.2.2 pty "ssh -i /root/.ssh/id_rsa -t 123.123.123.123 "pppd silent noauth 10.0.0.2.2:10.0.2.15"" ' stuff in to a shell script and have that shell script be activated by some sort of thing you can do from home. Like sending a special e-mail to trigger it like was suggested or put it on a timer to go off at convenent times.
Good Luck!
Facebook
Twitter