Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML version of email link not over HTTPS #58

Closed
dcRUSTy opened this issue Jul 12, 2020 · 6 comments
Closed

HTML version of email link not over HTTPS #58

dcRUSTy opened this issue Jul 12, 2020 · 6 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request good first issue Good for newcomers

Comments

@dcRUSTy
Copy link

dcRUSTy commented Jul 12, 2020

Describe the bug
There is button to display "HTML Version" of email. It redirects with an http:// URL and not https://

To Reproduce
Steps to reproduce the behavior:

  1. Send urself an email (with HTML content?)
  2. In bot click on "HTML Verison" button

Expected behavior
URL must begin with https://

Screenshots
notHTTPS

@rosehgal
Copy link
Owner

rosehgal commented Jul 12, 2020

@dcRUSTy I agree to this, but the http to https redirection is done at webserver layer. So even if you are see this html link, there is redirect call happening at the server layer which will move to https. You can check that out in your browser when the link is open.

I will keep this issue open till then 😄

@dcRUSTy
Copy link
Author

dcRUSTy commented Jul 12, 2020

wireshark
The redirection is way too late.... the email URL/UUID.html is in plaintext visible to anyone(sniffer) on the network.

@rosehgal
Copy link
Owner

@dcRUSTy it is not the case. The domain and uri are anyway submitted in plaintext even with https. The only role of https is to prevent data not the host uri.
You can refer to this question https://stackoverflow.com/questions/8277323/what-information-is-visible-to-a-packet-sniffer-which-intercepted-a-https-packet

@dcRUSTy
Copy link
Author

dcRUSTy commented Jul 12, 2020

For example url is https://example.com/1-2-3-4.html then sniffer can only get to know example.com
if url is on http://example.com/1-2-3-4.html then sniffer can see example.com along with 1-2-3-4.html. Trust me

GET /1-2-3-4.html is also encrypted in HTTPS

In our trashemail example the 1-2-3-4.html(UUID) over http is visible on wireshark... since it is visible attacker can also access this html with URL.

@rosehgal
Copy link
Owner

Oh yes! That is the case I think, I missed in the first shot. I think it will be a quick fix. Will fix this up. Thanks for pointing this out.

@rosehgal rosehgal self-assigned this Jul 12, 2020
@rosehgal rosehgal added bug Something isn't working enhancement New feature or request good first issue Good for newcomers labels Jul 12, 2020
@rosehgal
Copy link
Owner

Thanks @dcRUSTy. This has been fixed and rolled to production as well. It was just a config change, so no code change is there to point to any commit. Check that out, I am closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants