Quic-Transfer协议不需要TLS?
如果我不需要安全数据。 我可以不用Quic使用TLS吗?为什么必须将TLS与Quic一起使用?
谢谢。
If I need't a secure data.
Can I use TLS without QUIC? Why must use TLS with QUIC?
Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我认为您的意思是:
是,否。
RFC 9000和RFC 9001(QUIC标准)都要求QUIC安全,并通过TLS安全。而且,您的不可能在Internet上看到未经加密的Quic服务器。
但是,究竟是什么阻止您做任何您想做的事情?特别是使用QUIC没有加密?实际上,已经有允许它的实现。
话虽如此,我鼓励您实际上始终使用加密,即使进行测试或开发。这是一个很好的做法。因为它是强制性生产的(否则它是不安全的,除非您在没有网络的情况下在当地的怪异设置中使用它),并且最好将不同的Env保持在尽可能靠近的情况下。为了避免细微的问题。
I assume you meant:
Yes and no.
Both RFC 9000 and RFC 9001 (the QUIC standard) require QUIC to be secure, and through TLS. And it is highly unlikely you will see a QUIC server on the internet that is not encrypted.
But what exactly is stopping you from doing whatever you want? In particular using QUIC without encryption? In fact there already are implementations that allow it.
That being said, I encourage you to actually always use encryption, even for testing or development. It is a good practice. Because it is mandatory for production (otherwise it is not safe, unless you use it in a weird setup like locally without network), and it is a good idea to keep different envs as close to each other as possible. In order to avoid subtle issues.