Skip to main content
Information Security

Return to Answer

scrubbing
Source Link
StackzOfZtuff
StackzOfZtuff
  • 18.2k
  • 1
  • 54
  • 86

To answer the original question - most people never type https://something.comhttps://example.com directly. They rely either on links (click here to access our secure login server) or on redirects (type "gmail.com""gmail.com" in the browser, and you will be automatically redirected to a secure site).

This is where SSLStripSSLStrip comes in -: it intercepts the original, unsecured HTTP reply, and replaces <a href="https"><a href="https">; links with HTTP (insecure) versions. Also, it changes redirects ("Location:""Location:" headers) that point to HTTPS URLs.

With SSLStrip2SSLStrip2, this goes a bit further (intercept, redirect to an invalid subdomain, use DNS interception to actually provide a valid IP for that subdomain).

To answer the original question - most people never type https://something.com directly. They rely either on links (click here to access our secure login server) or on redirects (type "gmail.com" in the browser, and you will be automatically redirected to a secure site).

This is where SSLStrip comes in - it intercepts the original, unsecured HTTP reply, and replaces <a href="https"> links with HTTP (insecure) versions. Also, it changes redirects ("Location:" headers) that point to HTTPS URLs.

With SSLStrip2, this goes a bit further (intercept, redirect to an invalid subdomain, use DNS interception to actually provide a valid IP for that subdomain).

To answer the original question - most people never type https://example.com directly. They rely either on links (click here to access our secure login server) or on redirects (type "gmail.com" in the browser, and you will be automatically redirected to a secure site).

This is where SSLStrip comes in: it intercepts the original, unsecured HTTP reply, and replaces <a href="https">; links with HTTP (insecure) versions. Also, it changes redirects ("Location:" headers) that point to HTTPS URLs.

With SSLStrip2, this goes a bit further (intercept, redirect to an invalid subdomain, use DNS interception to actually provide a valid IP for that subdomain).

Source Link
Bogd
Bogd
  • 146
  • 3

To answer the original question - most people never type https://something.com directly. They rely either on links (click here to access our secure login server) or on redirects (type "gmail.com" in the browser, and you will be automatically redirected to a secure site).

This is where SSLStrip comes in - it intercepts the original, unsecured HTTP reply, and replaces <a href="https"> links with HTTP (insecure) versions. Also, it changes redirects ("Location:" headers) that point to HTTPS URLs.

With SSLStrip2, this goes a bit further (intercept, redirect to an invalid subdomain, use DNS interception to actually provide a valid IP for that subdomain).