Pasar a través de proxy HTTPS

[cocozz <cocozz@gmail.com>]

Buenas noches,

Actualmente me encuentro en un sitio donde pasando un NMAP he deducido
que la conexión a Internet pasa a través de un Proxy HTTPS.

> Starting nmap 3.81 ( http://www.insecure.org/nmap/
>  ) at 2005-09-04 04:55 CEST
> Interesting ports on 192.168.1.1:
> (The 1662 ports scanned but not shown below are in state: closed)
> PORT    STATE SERVICE
> 443/tcp open  https
> MAC Address: 00:13:7F:B2:82:AB (Unknown)
>   
> Nmap finished: 1 IP address (1 host up) scanned in 0.426 seconds
>   

Muchos protocolos como el IRC, SMTP, ICMP y demás estan bloqueados por lo que estoy muy limitado.
He descargado un script para "saltarse" un proxy de este tipo pero no parece que funcione

Aqui el programa:http://monkey.org/~dugsong/httpstunnel.c

También he pasado un scan con Nessus

>  . Information found on port https (443/tcp)
>   
>   
>     A web server is running on this port through SSL
>   
>  . Information found on port https (443/tcp)
>   
>   
>     Here is the SSLv2 server certificate:
>     Certificate:
>         Data:
>             Version: 1 (0x0)
>             Serial Number:
>                
>      39:61:61:37:36:65:64:64:33:65:34:34:35:65:36:38:36:37:32:66:64:31:36:36:62:39:66:33:36:62:38:33
>         Signature Algorithm: md5WithRSAEncryption
>         Issuer:
> serialNumber=3039c7bc,
> CN=pixfirewall.ciscopix.com/unstructuredName=pixfirewall.ciscopix.com
>         Validity
>             Not Before: Sep  1 16:56:12 2005 GMT
>             Not After : Aug 30 16:56:12 2015 GMT
>         Subject:
> serialNumber=3039c7bc,
> CN=pixfirewall.ciscopix.com/unstructuredName=pixfirewall.ciscopix.com
>         Subject Public Key Info:
>             Public Key Algorithm: rsaEncryption
>             RSA Public Key: (768 bit)
>                 Modulus (768 bit):
>                    
> 00:d1:83:1c:d7:ef:ab:9d:2a:5a:45:a0:e2:54:d0:
>                    
> 6a:3a:0b:69:c3:15:13:14:80:ac:5d:93:40:e1:a7:
>                    
> c2:d0:d0:ab:82:df:54:cc:99:8c:70:82:2b:9e:b5:
>                    
> 10:d5:f1:1d:c6:27:18:72:64:77:23:fa:d2:d7:6e:
>                    
> 83:30:f0:8a:d3:ee:2e:d5:95:22:62:f7:d4:07:6f:
>                    
> 73:ee:d1:52:80:cf:93:b7:3e:5f:cf:b3:bd:22:73:
>                    
> 13:6d:03:2b:1d:ea:7f
>                 Exponent: 65537 (0x10001)
>     Signature Algorithm: md5WithRSAEncryption
>         1c:d7:95:35:30:d2:6b:74:8f:67:7c:53:88:8d:c7:03:6f:f8:
>         cf:b5:0c:39:7f:65:34:0e:6b:55:e4:d4:22:32:de:2f:3e:95:
>         1a:5d:b5:5e:cd:88:9c:8d:97:e2:6e:45:dd:60:91:bc:a5:50:
>         90:d7:9c:d2:b2:bb:8b:5a:c8:07:ca:1e:44:6c:eb:c8:04:68:
>         28:39:b9:94:d2:1a:63:e8:84:21:95:7f:34:d6:a9:42:13:75:
>         d0:de:ea:5b:ec:0e
> Here is the list of available SSLv2 ciphers:
> RC4-MD5
> EXP-RC4-MD5
> RC4-64-MD5
> The SSLv2 server offers 2 strong ciphers, but also
> 0 medium strength and 1 weak "export class" ciphers.
> The weak/medium ciphers may be chosen by an export-grade
> or badly configured client software. They only offer a 
> limited protection against a brute force attack
>   
> Solution: disable those ciphers and upgrade your client
> software if necessary.
> See http://support.microsoft.com/default.aspx?scid=kb;en-us;216482
> or http://httpd.apache.org/docs-2.0/mod/mod_ssl.html#sslciphersuite
> This SSLv2 server also accepts SSLv3 connections.
> This SSLv2 server also accepts TLSv1 connections.

 

Si alguien me pudiera hechar una mano le estaria muy agradecido,
Saludos