Lamparas
My feedback
37 results found
-
411 votes
An error occurred while saving the comment Lamparas
supported this idea
·
-
146 votesLamparas
supported this idea
·
-
6 votesLamparas
supported this idea
·
-
141 votes
An error occurred while saving the comment Lamparas
commented
I have contacted Proton about not being able to use their services properly on my IPv6-only ISP in February 2026, this is an excerpt from the response I received:
As mentioned, IPv6 support for Proton services is actively monitored and discussed internally, but at this time we do not have a publicly shareable timeline or commitment for enabling native IPv6 connectivity across Proton Mail, Drive, or other services. We avoid publishing roadmap details unless implementation is confirmed and scheduled.
It is acknowledged internally that users without reliable IPv4 connectivity may experience reduced performance or reliability when accessing Proton services. While the majority of users still operate in dual-stack or IPv4-capable environments, we recognize that this balance is shifting over time.
Proton services operate on a complex, security-focused infrastructure that includes encryption layers, traffic filtering, DDoS mitigation, abuse prevention, and global routing controls. Enabling IPv6 is not a matter of address availability alone, it requires ensuring parity in security, reliability, monitoring, and abuse resistance across both protocol stacks. These requirements significantly increase the scope and risk of deployment compared to many conventional web services.For users who do not have native IPv4 connectivity, the most reliable way to use Proton services today is to make sure your network supports both IPv4 and IPv6, or to use a VPN that provides IPv4 access. This helps prevent slow or failed connections that can happen when your internet tries to convert IPv6 traffic to IPv4. Other than these options, there is no workaround on the Proton side, since our services currently rely on IPv4 for full functionality.
We continue to monitor IPv6 adoption and consider its implementation carefully, but we do not have a timeline for enabling full IPv6 support.An error occurred while saving the comment Lamparas
commented
It is interesting that Proton has had IPv6 prefixes since at least 2014, but they don't seem to be using. You can see this in the list of originated prefixes on their AS:
Lamparas
supported this idea
·
-
1,391 votesLamparas
supported this idea
·
-
871 votesLamparas
supported this idea
·
-
466 votesLamparas
supported this idea
·
-
186 votesLamparas
supported this idea
·
-
9 votesLamparas
supported this idea
·
-
6 votesLamparas
supported this idea
·
-
4 votesLamparas
supported this idea
·
-
26 votesLamparas
supported this idea
·
-
8 votesLamparas
supported this idea
·
-
20 votesLamparas
supported this idea
·
-
7 votesLamparas
supported this idea
·
-
14 votesLamparas
supported this idea
·
-
25 votesLamparas
supported this idea
·
-
16 votesLamparas
supported this idea
·
-
1,518 votesLamparas
supported this idea
·
-
2,053 votesLamparas
supported this idea
·
> I wrote the following email regarding PQC to Proton's support:
Hello,
I would like to ask about Proton's plan to support PQC in its services, more specifically the TLS stack. There are currently no PQ algorithms available as TLS exchange groups on any of Proton's services (except the CDN, which seems to be hosted by Cloudflare) for either HTTPS, or SMTP.
Checking with `openssl s_client -starttls smtp -connect mail.protonmail.ch:25 -tls1_3 -msg -servername mail.protonmail.ch`, and `openssl s_client -connect mail.proton.me:443`, I can see that neither support PQC exchange groups, and this seems to be the case for every Proton service. This is also the case for BoringSSL: `bssl s_client -starttls smtp -connect mail.protonmail.ch:25`, and `bssl s_client -connect mail.proton.me:443`.
Every single *free* email provider (gmail, yahoo, seznam, etc.) out of the 10 I tried supported a PQ TLS key exchange group (like X25519MLKEM768) for both their email WebUI, and SMTP submission.
This concerns me, because it makes all TLS sessions to Proton's service (including incoming emails) succeptible to SNDL attacks. Making Proton an even likelier target for these future attacks is the fact that many people who might be under threat by well-resourced adversaries use Proton's services. The highly-centralized nature of Proton's infrastrucutre also makes me even more concerned about the feasibility of SNDL against Proton service users.
In the last couple of months, a significant amount of peer-reviewed and credible research has shown that a cryptographically-relevant quantum computers might become available much earlier than previously thought, making many organizations move up their deadlines for PQ transitions by up to five years, all while Proton doesn't currently mitigate even the most pressing PQ threat (Asymetric key exchanges), despite algorithms currently understood to mitigate this threat being available in clients, servers and cryptographic libraries, and already deployed by most mainstream services (many of which are already working on implementing PQ algorithms in areas not succeptible to SNDL). Currently, I can throw Debian on a Raspberry, install Dovecot, Postfix, any webserver/SMTP proxy, and get support for PQ KEX algorithms, and protections against SNDL attacks out of the box.
What are Proton's plans, and timeline, around supporting, at the very least, PQ KEX algorithms for HTTPS/TLS and SMTP in it's product lineup?
Thank you.
> This is the response I received from them:
Hello,
Thank you for the detailed report and for taking the time to test this. We genuinely appreciate the thoroughness of your findings.
Adding PQ KEX support to our TLS/SMTP stack is something we are actively planning. That said, rolling this out responsibly requires significant evaluation and testing across our infrastructure, so we yet to have to a specific timeline at this stage. What we can say is that it is not something we expect to complete in the near term.
We understand the urgency around SNDL threats, especially for our users, and this is not something we are taking lightly.
Thanks again for raising this. Feedback like yours helps us prioritize the right things.
Best Regards,
XXXX
Mail Delivery Team
Proton Mail