Damn straight. As I've said in other posts here, better keep a low profile and have a cover story ready. If you can't make up one the screws will believe, then don't even think about messing with this stuff. (If you need or like your job, that is.)
Closet? No, I came out years ago. You don't have to be in IT to understand how it works. It's almost all documented out there in RFCs and other accessible information. There's also loads of free software out there. If you have a PC, you have everything it takes to play around with almost ALL the technology used by today's browsers, and other wonderful things like proxies.
Nevertheless - if they're allowing SSL connections (https://foo.com), then they're allowing connections into which they cannot snoop, and it should be possible to use such a connection for SSH. Hmm... does your browser give you certificate warnings for EVERY https: site you visit? If so, they're doing man-in-the-middle jiggery pokery, and you can forget trying to sneak an SSH connection across it.
Good. Once again we prove that if you have physical access to the machine, you own it. So you put a browser on that thumb drive and SSH too. This probably doesn't matter much at your school, but at your employer, you don't want to put evidence of your exploits in a folder on their machine - or worse, on their file server. Once it's there, it's in their backups... which they might send offsite into storage for years, so even burning down the fscking building won't eradicate that evidence. Use the thumb drive, please. Better still, encrypt its contents if you can. (Of course, if you're really worried about the safety of your job, you probably shouldn't be doing any of this stuff in the first place.)
Interesting. How does the firewall block the incoming traffic without blocking content from "real" sites? It must be snooping within the HTTP packets.
That's another good reason to use port 443 and not port 80 - because firewalls can't see within the SSL connections anyway. But beware the man-in-the-middle attack!
Damn straight. As I've said in other posts here, better keep a low profile and have a cover story ready. If you can't make up one the screws will believe, then don't even think about messing with this stuff. (If you need or like your job, that is.)
Closet? No, I came out years ago. You don't have to be in IT to understand how it works. It's almost all documented out there in RFCs and other accessible information. There's also loads of free software out there. If you have a PC, you have everything it takes to play around with almost ALL the technology used by today's browsers, and other wonderful things like proxies.
Nevertheless - if they're allowing SSL connections (https://foo.com), then they're allowing connections into which they cannot snoop, and it should be possible to use such a connection for SSH. Hmm... does your browser give you certificate warnings for EVERY https: site you visit? If so, they're doing man-in-the-middle jiggery pokery, and you can forget trying to sneak an SSH connection across it.
Good. Once again we prove that if you have physical access to the machine, you own it. So you put a browser on that thumb drive and SSH too. This probably doesn't matter much at your school, but at your employer, you don't want to put evidence of your exploits in a folder on their machine - or worse, on their file server. Once it's there, it's in their backups... which they might send offsite into storage for years, so even burning down the fscking building won't eradicate that evidence. Use the thumb drive, please. Better still, encrypt its contents if you can. (Of course, if you're really worried about the safety of your job, you probably shouldn't be doing any of this stuff in the first place.)
Interesting. How does the firewall block the incoming traffic without blocking content from "real" sites? It must be snooping within the HTTP packets.
That's another good reason to use port 443 and not port 80 - because firewalls can't see within the SSL connections anyway. But beware the man-in-the-middle attack!