Stateless PGP Keys

This is something that's been needed for quite some time. This allows for you to regenerate your PGP keys deterministically.

https://github.com/skeeto/passphrase2pgp

The magic of this stems from picking a finite UNIX time to enter as an input in the key generation process. Then voila.

Quantum Safe Onion Routing = https://arxiv.org/pdf/2001.03418.pdf (this is probably already several levels above what we see from the Tor Project already; I really don't like their earlier specifications and standards to be entirely honest with you)

^^ Maybe we also throw this in the t.me/libredarkweb channel ; why not?

Apologies for the gap in publishing on here, there are quite a few things that I have to add in here, so figure that I may as well stop procrastinating on that and get to it.

Researcher Discovered the NIST Specification on SHA256 Prime Values is Incorrect

"According to the National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) Publication 180-2, 'These words represent the first thirty-two bits of the fracitonal parts of t he cube roots of the first sixty-four prime numbers.'

No reason was provided as to why these values were selected...

Close examination of the SHA-256 constants reveals that only four of the numbers are actually prime numbers.

Source = https://www.femto-second.com/papers/SHA256LimitedStatisticalAnalysis.pdf

Standard Notes Updated Their Cryptography

These updates are palpable upgrades to the application itself.

Now they employ Argon2 for the password hashing and XChacha20-Poly1305 for the creation of the nonce (changes for each note that is saved by a user).

That's not to say that the cryptographic primitives that they were using before were weak, but these are obviously considerably stronger (and cryptographically more secure as well).

In many cases it is also estimated that Chacha20-poly1305 is faster than AES256-GCM on hardware (and software as well).

196-bit nonces are used for the chacha20 stream cipher encryption.

More information on the specification for this upgrade / update can be found here = https://docs.standardnotes.org/specification/encryption/

OASIS Key Management Protocol = https://docs.oasis-open.org/kmip/kmip-spec/v2.1/csprd01/kmip-spec-v2.1-csprd01.pdf

Chacha20 key wrapping + SipHash = https://eprint.iacr.org/2020/059.pdf

A lot cryptographic repos contained here for you to peruse through (hence the name of the GitHub account, I suppose) = https://github.com/CryptoFanOrg

Sign and Verify Bitcoin Messages = https://github.com/bitcoinjs/bitcoinjs-message

Best Explanation / Breakdown of How TLS Works You'll Ever Find in Life = https://tls.ulfheim.net/

Another resource = https://github.com/CryptoFanOrg

Proof Carrying Data = https://github.com/arkworks-rs/pcd

Snark and Relation Traits = https://github.com/arkworks-rs/snark

OASIS Key Management Protocol = https://docs.oasis-open.org/kmip/kmip-spec/v2.1/csprd01/kmip-spec-v2.1-csprd01.pdf

Chacha20 key wrapping + SipHash = https://eprint.iacr.org/2020/059.pdf

Merlin (weird ass website that apparently is for people that are trying to run from the law [just kidding]); this is zero knowledge proofs and some other other shit that's related or peripherally related to it.

https://merlin.cool/ (kind of weird actually ; one off website, designed in the fashion of the Rust documentation)

Trillian (this one is pretty significant) = https://github.com/google/trillian/

Trillian is an implementation of the concepts described in the Verifiable Data Structures white paper, which in turn is an extension and generalisation of the ideas which underpin Certificate Transparency.

OpenSK = OpenSK is an open-source implementation for security keys written in Rust that supports both FIDO U2F and FIDO2 standards.

https://github.com/google/OpenSK

Secure Message = https://github.com/google/securemessage

HTTP Signed Exchanges

A signed exchange is a delivery mechanism that makes it possible to authenticate the origin of a resource independently of how it was delivered (this sounds cool but I just need to get more information on what the fuck this actually means)

web.dev = https://web.dev/signed-exchanges/

"Signed Exchanges allow a site to cryptographically sign a request/response pair in a way that makes it possible for the browser to verify the origin and integrity of the content independently of how the content was distributed. As a result, the browser can display the URL of the origin site in the address bar, rather than the URL of the server that delivered the content. Separating content attribution from content distribution advances a variety of use cases such as privacy-preserving prefetching, offline internet experiences, and serving content from third-party caches."