Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPN does not yet support PQC #1598

Closed
Kreyren opened this issue Jun 26, 2024 · 4 comments
Closed

SPN does not yet support PQC #1598

Kreyren opened this issue Jun 26, 2024 · 4 comments
Labels
question TYPE: generic question about configuration or usage unlisted ATTRIBUTE: this issue will not be listed in-app, such as among search results

Comments

@Kreyren
Copy link

Kreyren commented Jun 26, 2024

image

SPN claims to be coming with a state of the art encryption yet seems to be lacking any kind of management for Post Quantum Safety as it's apparently not using a Post Quantum Safe encryption and it's unclear who runs the SPN nodes to probably sanely claim that it's also lacking management for Harvest Now, Decrypt Later to claim that all traffic sent over SPN is at a high risk of being collected and decrypted in the future.
So it seems that you are not really solving any problems with VPN and seemingly adding problems as e.g. wireguard can be configured to use a post-quantum safe cryptography to manage this problem.

Please fix that, the idea of SPN seems good on paper and i would like to use it for our infra in https://github.com/NiXium-org/Nixium to provide clearweb services that do not expose the location of the server to the SPN service provider or anyone who's trying to locate the IP.

Referencing for details: FiloSottile/age#578

P.S: Cut out the marketing bullshit it makes you seem like glowie instead of someone who's serious about privacy and security to the point that majority of people i talked to about SPN didn't want to use it as it seems too suspicious.

@Kreyren Kreyren added the bug TYPE: a report on something that isn't working label Jun 26, 2024
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@dhaavi
Copy link
Member

dhaavi commented Jul 1, 2024

Hey @Kreyren,

Thank you for raising your concerns.

SPN definitely uses state of the art encryption.

PQC is still experimental. While NIST has selected four algorithms for standardization in 2022 - CRYSTALS-Kyber, CRYSTALS-Dilithium, SPHINCS+, and FALCON - none of them are standardized yet. Three of them have draft standards. None of them are available in the golang stdlib.

Apart from that, practical quantum computers are still at least 10-30 years away. If your network traffic is worth saving 10 years and then paying for computation on a quantum computer "just in case", then whoever is targeting you has enough money to target you in other, faster, more practical, and cheaper ways.
Thus, PQC currently does not fit a realistic threat model for Internet traffic for pretty much anyone.

As soon as PQC is standardized and available, we will put it on the roadmap.

@dhaavi dhaavi closed this as completed Jul 1, 2024
@dhaavi dhaavi added unlisted ATTRIBUTE: this issue will not be listed in-app, such as among search results question TYPE: generic question about configuration or usage and removed bug TYPE: a report on something that isn't working labels Jul 1, 2024
@dhaavi dhaavi changed the title SPN appears to be objectively inferior to common VPNs SPN does not yet support PQC Jul 1, 2024
@Kreyren
Copy link
Author

Kreyren commented Jul 1, 2024

PQC is still experimental. While NIST has selected four algorithms for standardization in 2022 - CRYSTALS-Kyber, CRYSTALS-Dilithium, SPHINCS+, and FALCON - none of them are standardized yet. Three of them have draft standards. None of them are available in the golang stdlib. -- @dhaavi (#1598 (comment))

NTRU was developed in 1996 and European Union recommended it on 7th September 2015 in PQCRYPTO https://pqcrypto.eu/docs/initial-recommendations.pdf and beyond the EU standardization it's standardized in IEEE Std 1363.1 and X9.98 and implemented by OpenSSH, WolfSSH, Lokinet, BouncyCastle, etc..

None of them are available in the golang stdlib. -- @dhaavi (#1598 (comment))

image

Apart from that, practical quantum computers are still at least 10-30 years away. -- @dhaavi (#1598 (comment))

Willful missinformation:

Atom Computing has 1225-Qubits already, Cleveland Clinic uses their quantum computer for healthcare research and most importantly IBM's Senior Vice President and Director of Research Dario Gill claims that there are no obstacles to get quantum computers with +100K qubits in 5 years

If your network traffic is worth saving 10 years and then paying for computation on a quantum computer "just in case", then whoever is targeting you has enough money to target you in other, faster, more practical, and cheaper ways.
Thus, PQC currently does not fit a realistic threat model for Internet traffic for pretty much anyone. -- @dhaavi (#1598 (comment))

That's apparently what NSA and their data center in utah is doing to every day people as reported by forbes https://www.forbes.com/sites/netapp/2013/07/26/nsa-utah-datacenter with capacity to hold estimated exabytes of storage harvested through their global surveillance programs such as those explained by Edward Snowden during his interview by John Oliver on Last Week Tonight S2E8: https://youtu.be/SgTQDp1jwBw?t=2082

Because of that we can sanely claim that objectively that fits everyone's threat model.


It's frankly alarming that you are the lead developer of SPN and yet are apparently this misinformed on the critical subjects and refuse to take this subject with the seriousness it deserves which is enough for me to want to disqualify SPN for it's use in NiXium.

@dhaavi
Copy link
Member

dhaavi commented Jul 1, 2024

It seems we have different views on this.
You are welcome to choose whatever technology fits your needs.

@safing safing locked as too heated and limited conversation to collaborators Jul 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question TYPE: generic question about configuration or usage unlisted ATTRIBUTE: this issue will not be listed in-app, such as among search results
Projects
None yet
Development

No branches or pull requests

2 participants