Rustls: new, modern TLS library written in Rust
1–10 of 112 posts
Re: Rustls: new, modern TLS library written in Rust
#2No support for TLS 1.3? Any reason for this, other than work?
Re: Rustls: new, modern TLS library written in Rust
#3No support for TLS 1.3? Any reason for this, other than work?
It's listed in the "Possible future features" section...
Isn't TLS 1.3 currently still a draft? [1]
[1]: https://en.wikipedia.org/wiki/Transport_Layer_Security#TLS_1...
Re: Rustls: new, modern TLS library written in Rust
#4I'm developing a twitch whenever I see the word "modern" in a software description. It doesn't actually say anything about what you're doing.
Re: Rustls: new, modern TLS library written in Rust
#5I'm developing a twitch whenever I see the word "modern" in a software description. It doesn't actually say anything about what you're doing.
In this case I would tend to take "modern" to mean "not based on openssl."
Re: Rustls: new, modern TLS library written in Rust
#6I'm developing a twitch whenever I see the word "modern" in a software description. It doesn't actually say anything about what you're doing.
I take it to mean "uses current, best practices." For example:
- C++: uses C++11 features, avoids non-RAII resources, prefers standard libraries over older, platform-specific libraries, not written as "C with classes."
- C: doesn't do weird stuff like bypassing malloc(), avoids undefined behavior.
- in general: has a test suite, probably uses continuous testing like Travis, uses modern language features to achieve cleaner & more robust code.
Re: Rustls: new, modern TLS library written in Rust
#7I'm developing a twitch whenever I see the word "modern" in a software description. It doesn't actually say anything about what you're doing.
> The following things are broken, obsolete, badly designed, underspecified, dangerous and/or insane. Rustls does not support [...]
Re: Rustls: new, modern TLS library written in Rust
#8Re: Rustls: new, modern TLS library written in Rust
#9I'm developing a twitch whenever I see the word "modern" in a software description. It doesn't actually say anything about what you're doing.
I take it to mean "uses current, best practices." For example: - C++: uses C++11 features, avoids non-RAII resources, prefers standard libraries over older, platform-specific libraries, not written as "C with classes." - C: doesn't do weird stuff like bypassing malloc(), avoids undefined behavior. - in general: has a test suite, probably uses continuous testing like Travis, uses modern language features to achieve cl…
> C: doesn't do weird stuff like bypassing malloc(), avoids undefined behavior.
Can you elaborate?
Re: Rustls: new, modern TLS library written in Rust
#10Earlier quoted context omitted.
I take it to mean "uses current, best practices." For example: - C++: uses C++11 features, avoids non-RAII resources, prefers standard libraries over older, platform-specific libraries, not written as "C with classes." - C: doesn't do weird stuff like bypassing malloc(), avoids undefined behavior. - in general: has a test suite, probably uses continuous testing like Travis, uses modern language features to achieve cl…
> C: doesn't do weird stuff like bypassing malloc(), avoids undefined behavior. Can you elaborate?
It's a bit of a naive comment, because it wholly depends on the libraries you include and what those do.
Use any of the debugging libraries that shim in their own alloc routines, you bypass malloc (or at least do a bunch of things that impact what gets malloc'd).