Explore >> Select a destination
|
You are here 
|
capnproto.org | ||
| | | | |
faultlore.com
|
|
| | | | | ||
| | | | |
ashvardanian.com
|
|
| | | | | I'd argue that almost every open-source developer gets an extra spark of joy when someone reads the documentation and uses their tool in a way that goes beyond the classic 101 examples. It's a rare treat even for popular projects like JSON parsers, but if you are building high-throughput software, such as analyzing millions of network packets per second, you'll have to dig deeper. The first thing I generally check in such libraries is the memory usage pattern and whether I can override the default memory... | |
| | | | |
www.trailofbits.com
|
|
| | | | | [AI summary] The text discusses various cryptographic constructions and their vulnerabilities. It highlights the importance of using established cryptographic primitives like HMAC, KMAC, and modern password-based key derivation functions (PBKDFs) instead of ad-hoc solutions. Key points include the risks of ambiguous encoding in MAC and hash functions, length-extension attacks, and the need for memory-hard KDFs to resist brute-force attacks. The text also touches on the broader implications of cryptographic design, emphasizing the necessity of rigorous standards and avoiding simplistic approaches that can lead to significant security weaknesses. | |
| | | | |
poignardazur.github.io
|
|
| | | Let's talk about pinning in the Rust programming language. | ||
