Hacking or Getting Around Proxy Servers At work?

[SLAG]

this is in theory


Proxy server called "Blue Coat" - www.bluecoat.com -

How would I go about getting around it?

Now it seems just like an HTTP proxy as i can still run CMD and do an ftp command from the console. Email Ports are working and functional.


How to get around the "Blue Coat"

[htismaqe]

I should also mention that in my experience doing consulting, most companies will issue a warning if you get caught wasting time on the Internet. However, deliberately bypassing network security controls will result in IMMEDIATE termination.

[htismaqe]

I just checked out Circumventor and it may work.

You theoretically would be using your home computer as a proxy to access sites that your proxy at work won't allow.

The only issue with this is that as soon as they see 600,000 log entries in the proxy log with a destination address of your broadband connection at home, they'll shut that down too.

[StcChief]

Originally Posted by SLAG02

this is in theory


Lets say "X" employer installed a new Proxy server called "Blue Coat" - www.bluecoat.com -

How would I go about getting around it?

Now it seems just like an HTTP proxy as i can still run CMD and do an ftp command from the console. Email Ports are working and functional.


How to get around the "Blue Coat"

hits... is right...this will get you fired or moved into the IT dept.

Depends on how well you know what your doing, And can explain what your doing if caught.

Hackers are promoted (for trying to break security) or fired.....

Your choice....

[SLAG]

my plan is to get a promotion if they fire me thats the risk im willing to take -- rdp-may work im not sure if its blocked or not i know ftp is open. circumventor may work but i doubt it -- could a change in the hosts file make any difference or not ?

[SLAG]

Originally Posted by htismaqe

I just checked out Circumventor and it may work.

You theoretically would be using your home computer as a proxy to access sites that your proxy at work won't allow.

The only issue with this is that as soon as they see 600,000 log entries in the proxy log with a destination address of your broadband connection at home, they'll shut that down too.

Circumventor will not work..


my IP address is not on the Approved List at work...MY approved List is very short right now.. its suppose to be expanding.. and at that point some other proxy sites may work who knows..

what i need is to fool the Blue Coat into thinking one of those proxy sites is an Approved site such as www.usps.gov or www.ups.com

I can only think of 3 other sites i have access to.

[htismaqe]

changing the hosts file won't do shit...

Is FTP open to everywhere? You could use a remote desktop tool where you can change the ports used...

[SLAG]

Originally Posted by htismaqe

changing the hosts file won't do shit...

Is FTP open to everywhere? You could use a remote desktop tool where you can change the ports used...

Yes it seems FTP is open everywhere..

I did CMD , FTP , OPEN ftp.aol.com, ftp.chiefsplanet.com ftp.chillplace.net all work fine If i knew usernames and PW to all those places



I do have Ultra VNC installed on my PC and have been using the VNC Client on my cell phone.. it sucks.. but Ultra VNC is hella cool

[unlurking]

As htis said, you will get caught, but if that doesn't matter to you, then do as he suggested. It looks as though FTP is open to the world, and only HTTP is blocked by site.

Actually using FTP as a proxy though won't likely work (may be software out there, but I don't know it), as FTP is UDP and HTTP is TCP. I seriously doubt they have 21 TCP open. I would check for telnet (23) or SMTP (25). Either of these can be proxied easily, and are likely open to the world like FTP. SSH (22) probably is as well, but if you set this up on a home box, you'll probably want to use SSH for admin access. You could however configure to tunnel X Windows over SSH, which will give you the ability to open Firefox (or browser of choice) on the target system and have it display on your work box. (Without dissing VNC, I actually find this a better solution because you don't transmit the graphics of an entire desktop, only the application windows you open.)

Lastly, many of the proxy content filters are "word-based". This is due to the ever-changing ip address landscape of the internet, and the ability to filter on custom language. That usually means you can simply enter the IP address of the target website (if not hosted virtually), and get to the site. Don't know about blue-coat though.

[htismaqe]

Originally Posted by unlurking

As htis said, you will get caught, but if that doesn't matter to you, then do as he suggested. It looks as though FTP is open to the world, and only HTTP is blocked by site.

Actually using FTP as a proxy though won't likely work (may be software out there, but I don't know it), as FTP is UDP and HTTP is TCP. I seriously doubt they have 21 TCP open. I would check for telnet (23) or SMTP (25). Either of these can be proxied easily, and are likely open to the world like FTP. SSH (22) probably is as well, but if you set this up on a home box, you'll probably want to use SSH for admin access. You could however configure to tunnel X Windows over SSH, which will give you the ability to open Firefox (or browser of choice) on the target system and have it display on your work box. (Without dissing VNC, I actually find this a better solution because you don't transmit the graphics of an entire desktop, only the application windows you open.)

Lastly, many of the proxy content filters are "word-based". This is due to the ever-changing ip address landscape of the internet, and the ability to filter on custom language. That usually means you can simply enter the IP address of the target website (if not hosted virtually), and get to the site. Don't know about blue-coat though.

Great post. Elaborated on most of the things I wasn't able to articulate myself.

I'm so fuggin burned out on technology...

[unlurking]

haha

I totally understand. Used to have multiple firewalls, routers , and servers in a nice rack solution. Now I'm down to a single ingress device, a few laptops and desktops and a crapload of parts I don't really feel motivated to do anything with.

I've got about 40GB of mp3's on a server I've been to lazy to setup. Working so many hours that tech is no longer the passion it once was. The family is happy to be spending more time with me, and I'm glad I've gotten out of my cave. Used to be my life, now it's just my job. Think I'm turning into one of those old farts I used to make fun of when I first got into IT. oh well

[SLAG]

Originally Posted by unlurking

As htis said, you will get caught, but if that doesn't matter to you, then do as he suggested. It looks as though FTP is open to the world, and only HTTP is blocked by site.

Actually using FTP as a proxy though won't likely work (may be software out there, but I don't know it), as FTP is UDP and HTTP is TCP. I seriously doubt they have 21 TCP open. I would check for telnet (23) or SMTP (25). Either of these can be proxied easily, and are likely open to the world like FTP. SSH (22) probably is as well, but if you set this up on a home box, you'll probably want to use SSH for admin access. You could however configure to tunnel X Windows over SSH, which will give you the ability to open Firefox (or browser of choice) on the target system and have it display on your work box. (Without dissing VNC, I actually find this a better solution because you don't transmit the graphics of an entire desktop, only the application windows you open.)

Lastly, many of the proxy content filters are "word-based". This is due to the ever-changing ip address landscape of the internet, and the ability to filter on custom language. That usually means you can simply enter the IP address of the target website (if not hosted virtually), and get to the site. Don't know about blue-coat though.

Think I could Run a Port Sniffer and see whats open?

[Fish]

Originally Posted by SLAG02

Think I could Run a Port Sniffer and see whats open?

You just wanted to type "port sniffer" didn't you?

[unlurking]

@ KC Fish

A sniffer will just tell you what traffic is visible to your machine (unless you ARP poison, and bringing down the network will definitely get you fired).

Since you seem to have "time" to do this, attracting AS LITTLE attention as possible is your best bet. If you're trying to "impress" the IT staff to get a job, setting alarms off is not going to help.

Easiest thing to do, would be to configure a linux box at home (you seem to be getting good with SUSE) with SSH on a buch of different ports.

#/ vim /etc/ssh/sshd_config

modify the first line in the file to add more ports...
(don't forget to remove the comment symbol "#")

Port 22,23,25,80,443,2200,3500,4500 (etc.)

then restart sshd...

#/ /etc/init.d/sshd stop
#/ /etc/init.d/sshd start

Then check that it's working...

#/ nmap -A localhost -p 22,23,25,80,443, (etc.)

Then when you get to the office, see if you can login over one of the open ports. At this point, all you have to do is install a proxy server on your box on the open port.

EDIT:
Unless by "port sniffer" you meant "scanner", you still need to have a box on the outside to respond to you. Also, you will often see ports respond as "filtered" rather than open or closed as most firewalls now adays act as proxies, calling into question the results of most port scans. Actually opening a connection through the firewall to the outside is least likely to be seen, and will give solid results.

[SLAG]

Originally Posted by unlurking

@ KC Fish

A sniffer will just tell you what traffic is visible to your machine (unless you ARP poison, and bringing down the network will definitely get you fired).

Since you seem to have "time" to do this, attracting AS LITTLE attention as possible is your best bet. If you're trying to "impress" the IT staff to get a job, setting alarms off is not going to help.

Easiest thing to do, would be to configure a linux box at home (you seem to be getting good with SUSE) with SSH on a buch of different ports.

#/ vim /etc/ssh/sshd_config

modify the first line in the file to add more ports...
(don't forget to remove the comment symbol "#")

Port 22,23,25,80,443,2200,3500,4500 (etc.)

then restart sshd...

#/ /etc/init.d/sshd stop
#/ /etc/init.d/sshd start

Then check that it's working...

#/ nmap -A localhost -p 22,23,25,80,443, (etc.)

Then when you get to the office, see if you can login over one of the open ports. At this point, all you have to do is install a proxy server on your box on the open port.

EDIT:
Unless by "port sniffer" you meant "scanner", you still need to have a box on the outside to respond to you. Also, you will often see ports respond as "filtered" rather than open or closed as most firewalls now adays act as proxies, calling into question the results of most port scans. Actually opening a connection through the firewall to the outside is least likely to be seen, and will give solid results.

alright.. after my 2 mickeys 40's ware off i will take a stab at it

[SLAG]

What if I am not able to load an SSH client on to my work machine? What would the method Be for using telnet in this case?