-
Improvement
-
Resolution: Fixed
-
Normal
-
None
The page where a user submits their username and password should be handled through HTTPS, to reduce the chance of username and passwords being intercepted, particularly when users are logging in at public hotspots over WiFi.
Given that other sites like GMail and Facebook are now encrypting their entire traffic to overcome Firesheep (http://en.wikipedia.org/wiki/Firesheep) session cookie cloning attacks, it's seems very poor practice that passwords are being sent apparently in plain text.
- has related issue
-
IMG-68 4 or 5 seconds latency on HTTPS-CAA image loading (instead of none)
- Closed
-
MBS-5298 WikiDocs links are not scheme-independent
- Closed
-
MBS-5301 gravatars do not get loaded over SSL when they should be
- Closed
-
MBS-5347 acoustid API isn't available nor requested over https, so on https musicbrainz-server acoustids don't appear
- Closed
-
MBS-6701 Now being shifted around from http to https
- Closed
-
PICARD-337 Allow using encrypted connection to mb.org
- Closed
-
MBS-5339 Cover Art should be loaded over SSL where possible
- Closed
-
MBS-357 Don't store passwords in clear text
- Closed
- is a dependency of
-
MBS-6711 not redirected to HTTPS login page
- Closed
- is duplicated by
-
MBS-3631 Allow login vis SSL
- Closed