Rust Cryptography Should Be Written in Rust
briansmith.org
Rust Cryptography Should Be Written in Rust
1–10 of 110 posts
Re: Rust Cryptography Should Be Written in Rust
#2Not wonder it is becoming the de-facto language for building applications in the blockchain space.
Does anyone else use Rust outside the blockchain/cryptography space? What are you working on?
Re: Rust Cryptography Should Be Written in Rust
#3So far the only solid use case for Rust that I have seen in applications where security is extremely important. Not wonder it is becoming the de-facto language for building applications in the blockchain space. Does anyone else use Rust outside the blockchain/cryptography space? What are you working on?
Playing devil's advocate, when is security not extremely important, except maybe in throwaway bash script-type applications?
Re: Rust Cryptography Should Be Written in Rust
#4So far the only solid use case for Rust that I have seen in applications where security is extremely important. Not wonder it is becoming the de-facto language for building applications in the blockchain space. Does anyone else use Rust outside the blockchain/cryptography space? What are you working on?
Re: Rust Cryptography Should Be Written in Rust
#5Re: Rust Cryptography Should Be Written in Rust
#6Re: Rust Cryptography Should Be Written in Rust
#7So far the only solid use case for Rust that I have seen in applications where security is extremely important. Not wonder it is becoming the de-facto language for building applications in the blockchain space. Does anyone else use Rust outside the blockchain/cryptography space? What are you working on?
Re: Rust Cryptography Should Be Written in Rust
#8Crypto code should be written in assembly. Zero ambiguity, zero undefined behavior, 100% verifiable.
Re: Rust Cryptography Should Be Written in Rust
#9Crypto code should be written in assembly. Zero ambiguity, zero undefined behavior, 100% verifiable.
Re: Rust Cryptography Should Be Written in Rust
#10Crypto code should be written in assembly. Zero ambiguity, zero undefined behavior, 100% verifiable.
Heartbleed also wasn't caused by ambiguity or undefined behavior, if you believe compiler writers.