Quote:
Originally Posted by KliPPy
He is already using HTTPS, by connecting to remote on port 443.
|
Actually he is not, there is more to it than simply connecting on 443.
cURL output when using HTTPS
Code:
# curl -v https://google.com
* About to connect() to google.com port 443 (#0)
* Trying 173.194.46.73... connected
* Connected to google.com (173.194.46.73) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_RSA_WITH_RC4_128_SHA
* Server certificate:
* subject: CN=*.google.com,O=Google Inc,L=Mountain View,ST=California,C=US
* start date: Oct 22 12:55:10 2014 GMT
* expire date: Jan 20 00:00:00 2015 GMT
* common name: *.google.com
* issuer: CN=Google Internet Authority G2,O=Google Inc,C=US
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: google.com
> Accept: */*
cURL output when using Port 443
Code:
# curl -v google.com:443
* About to connect() to google.com port 443 (#0)
* Trying 173.194.46.68... connected
* Connected to google.com (173.194.46.68) port 443 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: google.com:443
> Accept: */*
Notice how the HTTPS one sends SSL info and the 443 one does not.
__________________