News for hackers. Stuff that matters.
Re:Russia blocks ProtonMail by akskos on Tuesday March 12, 2019 @07:22AM (#19367063)
I once lost my protonmail password and was able to get my account back by providing only my browser information, display name, rough timestamps of my requests to their servers and that "i preserved the last session for quite long time". Not sure how secure that was :d Of course I didn't get back any of the emails since they were encrypted with the previous password but still if that is their normal protocol, someone with my browser information and name could just mitm me recording the timestamps of requests to protonmail's server and request a password reset.
Re:Russia blocks ProtonMail by gruez on Tuesday March 12, 2019 @08:09AM (#19367338)
>someone with my browser information and name could just mitm me recording the timestamps of requests to protonmail's server and request a password reset.

If they can MITM you, why not steal the password directly, or serve malicious js to get your password?

Re:Russia blocks ProtonMail by uponcoffee on Tuesday March 12, 2019 @08:24AM (#19367432)
Because https mitigates their attack vectors as a mitm. They can't steal the password since it's not sent in plaintext, and for similar reasons can't deliver/inject malicious Javascript. They could collect timestamps though and scrape header information from http connections to other sites.
Re:Russia blocks ProtonMail by StreamBright on Tuesday March 12, 2019 @08:35AM (#19367500)
Not really. It just requires HTTPS mitm. It is harder to have a CA that can create a cert that looks like it was issued by the original website you are trying to achieve but this is standard practice in gov agencies to mitm HTTPS communication. The mitigation of these sort of attacks is called certificate pinning.

https://security.stackexchange.com/questions/29988/what-is-c...

Re:Russia blocks ProtonMail by uponcoffee on Tuesday March 12, 2019 @02:33PM (#19371453)
That's a fair point. My reply was more in the context of the root comment - and with an average attacker in mind - where they were describing eavesdropping as opposed an attack carried out by a sophisticated actor.

My point was that MITMing HTTPS and HSTS isn't really necessary to carry out an attack as described by the root comment.

You only need to be in position to eavesdrop and/or MITM http connections to scrape together the necessary information; a much lower bar.

Re:Russia blocks ProtonMail by StreamBright on Tuesday March 12, 2019 @04:04PM (#19372393)
True, I guess I was just nitpicking. :)
Re:Russia blocks ProtonMail by gruez on Tuesday March 12, 2019 @08:47AM (#19367569)
What you're describing is eavesdropping, not MITM
Re:Russia blocks ProtonMail by akskos on Tuesday March 12, 2019 @08:51AM (#19367587)
In that case I meant eavesdropping