https://blog.mozilla.org/futurereleases/2018/10/22/testing-n...
https://blog.mozilla.org/futurereleases/2018/10/22/testing-n...
I recently wrote a full review on my blog (so I won't repeat it all here): https://unop.uk/protonmail-review/
Also, Bridge is receiving a lot of attention internally. Your v1.1.1 experience will continue to improve.
Appreciate your feedback.
Your connection is not secure
The owner of protonvpn.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
Doesn't inspire confidence.
[0]https://old.reddit.com/r/firefox/comments/au7zcz/how_to_remo...
So.. IT that manages the certs and the gateway, use a MIMT 'attack' to decrypt all your traffic, scan/read it, and then encrypt it again to send it out to the wilderness of the Internet. This is what the browser is messaging. Notifying you that "something is wrong with the connection. Browser is not sure what exactly, thus pointing the finger on the certificate.
Perhaps someone can explain the above with more technical terms, but in a nutshell, our companies, on our corporate desktops/laptops sniff through each and every bit and byte that goes in and out of our machines.
A commom workardound "permanent accept this exception" (or similar wording) makes the browser to stop complaining about this breach of privacy.
https://github.com/eggsome/AddFirefoxCert
Although:
1. I don't like to encourage this kind of behavior (I only use this for "good")
2. The certutil tool needs to be recompiled from the mozzila sources for new firefox.
Yup, typically referred to as "SSL Inspection" by the companies that produce products to monitor SSL traffic. Normally this is accompanied by controlling the clients and pushing a cert into their browser to avoid the warning messages.
*disclaimer, I also work for ProtonMail so my use of ProtonVPN is more of a company perk, but one I enjoy.