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

PHYLO sends user passwords in plaintext; should be using TLS #118

Open
movermeyer opened this issue Apr 23, 2018 · 2 comments
Open

PHYLO sends user passwords in plaintext; should be using TLS #118

movermeyer opened this issue Apr 23, 2018 · 2 comments

Comments

@movermeyer
Copy link

PHYLO is not using encryption (ie. TLS). This has been an increasingly dangerous thing for websites to do, as user details are being sent in plaintext across the internet.

This allows third parties to collect the user details which can be used to compromise other online accounts of the >60% of users who re-use their passwords across multiple sites.

Beyond that, we have seen nation-states take advantage of non-TLS connections in order to perform man-in-the-middle attacks on users, which can harm both the users and the reputation of the site.

This is all to say that encrypting connections to websites has become table stakes for being secure on the web.

From Fiddler 4:

POST http://ec2-52-26-53-11.us-west-2.compute.amazonaws.com/api/login/ HTTP/1.1
Host: ec2-52-26-53-11.us-west-2.compute.amazonaws.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://phylo.cs.mcgill.ca/
Content-Type: application/x-www-form-urlencoded
Content-Length: 34
Origin: http://phylo.cs.mcgill.ca
DNT: 1
Connection: keep-alive

username=MyUsername&password=MySecurePassword

More reading:

@movermeyer
Copy link
Author

movermeyer commented Apr 23, 2018

This applies to

@waldispuhl
Copy link

Thanks. We are indeed planning to use TSL. We're working on it but are experiencing compatibility issues. Hopefully it'll be fixed soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants