Opened 4 years ago

Last modified 4 years ago

#2012 new improve feature

SSL situation summary

Reported by: dima42 Owned by:
Priority: major Milestone: unassigned
Component: unknown Keywords:
Cc:

Description (last modified by dima42)

Current situation:

http://www.bewelcome.org sends forms for signup, sign-in, verification and password change over SSL. These are all the places where the password is transmitted. However, it is still vulnerable to man-in-middle attacks. To improve this situation we could redirect users to a single https page to log in, and then meta-refresh out of https once logged in.

https://www.bewelcome.org is fully functional except for that we get mixed content warnings on any page with a map. We are not routing users onto https because of these mixed content warnings. OSM does not provide map tiles over https. I'm not sure what happens if we request OSM tiles over ssl cloudmade protocol. We could also proxy the tiles on our server.

Related discussions:

Change History (3)

comment:1 Changed 4 years ago by dima42

  • Description modified (diff)

comment:2 Changed 4 years ago by jsfan

I don't quite follow on the first part. All SSL connections are vulnerable to MITM attacks. The only protection against that is users being cautious enough to check certificates and preferably even fingerprints.

I'm not sure what exactly the suggested change will fix and how.

comment:3 Changed 4 years ago by dima42

The only thing I mean is:

If http://www.bewelcome.org/login is served by someone else, the user has basically no way of knowing. If https://www.bewelcome.org/login is served by someone else, most browsers will give the user a certificate mismatch warning.

Note: See TracTickets for help on using tickets.