-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
FFeature Request: Implement Quantum-Safe Encryption with Kyber to Prevent Future Decryption by Quantum Computers #1836
Comments
when go tls supports it |
@Fangliding It's time to work, dude. |
I've already noticed it, but utls still not updated so rprx doesn't want to add it to core see #3813 (comment) |
没有指纹伪装的话意义不大,等 uTLS 更新 @gaukas |
REALITY sessionid 仍用 X25519 共享密钥来加解密,因为相关代码仅作认证不加密应用数据,且客户端始终会发 X25519 临时公钥 |
In #3884: Let's try to use SSL |
implemented in #3991 |
Description of the issue
As the development of quantum computing advances, the need for quantum-safe encryption becomes increasingly important. Traditional encryption methods like TLS are at risk of being broken by powerful quantum computers. One major concern is that censorship departments or other malicious actors may currently store TLS-encrypted data, intending to decrypt it in the near future once quantum computing capabilities are sufficiently advanced. To ensure the long-term security of data and communications, I propose the implementation of Kyber as an enhancement to TLS in Xray.
Possible solussion
Kyber, a lattice-based, post-quantum cryptographic algorithm, as an enhancement to the existing TLS 1.3 encryption in our tool. This would provide an additional layer of security that is resistant to quantum computing attacks, while maintaining the proven security of TLS 1.3. The integration should be seamless and optional, allowing users to choose between the standard TLS 1.3 encryption and the enhanced TLS 1.3 encryption with Kyber. In addition, there are existing practice on Kyber
Reference: https://pq-crystals.org/kyber/index.shtml
The text was updated successfully, but these errors were encountered: