Best Explanation / Breakdown of How TLS Works You'll Ever Find in Life = https://tls.ulfheim.net/
tls12.xargs.org
The Illustrated TLS 1.2 Connection
Every byte of a TLS connection explained and reproduced
OASIS Key Management Protocol = https://docs.oasis-open.org/kmip/kmip-spec/v2.1/csprd01/kmip-spec-v2.1-csprd01.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)
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.
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.
GitHub
GitHub - google/trillian: A transparent, highly scalable and cryptographically verifiable data store.
A transparent, highly scalable and cryptographically verifiable data store. - google/trillian
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
https://github.com/google/OpenSK
GitHub
GitHub - google/OpenSK: OpenSK is an open-source implementation for security keys written in Rust that supports both FIDO U2F and…
OpenSK is an open-source implementation for security keys written in Rust that supports both FIDO U2F and FIDO2 standards. - google/OpenSK
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."
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."
web.dev
Signed Exchanges (SXGs)
An SXG is a delivery mechanism that makes it possible to authenticate the origin of a resource independently of how it was delivered.
Asylo Dev = asylo.dev
Encrypted enclave applications
1. Integrates with gRPC for easy and secure inter-enclave and external communication
2. Use attestation to verify your enclave's integrity, and cryptographically bind your secrets to identity ACLs for safe storage.
Code for piping this all through Docker can be found here = https://asylo.dev/docs/guides/quickstart.html#what-is-an-enclave
Encrypted enclave applications
1. Integrates with gRPC for easy and secure inter-enclave and external communication
2. Use attestation to verify your enclave's integrity, and cryptographically bind your secrets to identity ACLs for safe storage.
Code for piping this all through Docker can be found here = https://asylo.dev/docs/guides/quickstart.html#what-is-an-enclave
asylo.dev
Quickstart Guide
Install Asylo, build, and run your first enclave!
DigiCert Certificate Tools = https://docs.digicert.com/certificate-tools/
ECNR (elliptic curve variant) = https://ieeexplore.ieee.org/document/4418260
ieeexplore.ieee.org
A Novel Blind Signature Scheme Based on Nyberg-Rueppel Signature Scheme and Applying in Off-Line Digital Cash - IEEE Conference…
IEEE Xplore, delivering full text access to the world's highest quality technical literature in engineering and technology. | IEEE Xplore
End to End by Google (some encryption stuff) = https://github.com/google/end-to-end
GitHub
GitHub - google/end-to-end: End-To-End is a crypto library to encrypt, decrypt, digital sign, and verify signed messages (implementing…
End-To-End is a crypto library to encrypt, decrypt, digital sign, and verify signed messages (implementing OpenPGP) - google/end-to-end
Phenomenal post by this individual regarding potential vulnerabilities in attempting to leverage ed25519 for HD keys (not as straightforwarfd as one would imagine that it is)
https://forum.w3f.community/t/key-recovery-attack-on-bip32-ed25519/44
https://forum.w3f.community/t/key-recovery-attack-on-bip32-ed25519/44
Key recovery attack on BIP32-Ed25519 (they deserve their fucking credit for this ; just failing to understand why they're so daft in so many other areas of blockchain...just doesn't even make sense really)
https://forum.w3f.community/t/key-recovery-attack-on-bip32-ed25519/44
https://forum.w3f.community/t/key-recovery-attack-on-bip32-ed25519/44
libp2p TLS = https://github.com/libp2p/go-libp2p-tls (this is the GitHub but there's no documentation that speaks on this as well ; fuck )
There's more information about TLS 1.3 for libp2p contained here = https://github.com/libp2p/specs/blob/master/tls/tls.md [had to find additional information]
Replacement / Currently used in lieu of the TLS that we were looking at above = https://github.com/libp2p/go-libp2p-secio (secio)
More specs on the protocol can be found here = https://github.com/libp2p/specs/blob/master/secio/README.md [SECIO allows participating peers to support a subset of algorithms]
There's more information about TLS 1.3 for libp2p contained here = https://github.com/libp2p/specs/blob/master/tls/tls.md [had to find additional information]
Replacement / Currently used in lieu of the TLS that we were looking at above = https://github.com/libp2p/go-libp2p-secio (secio)
More specs on the protocol can be found here = https://github.com/libp2p/specs/blob/master/secio/README.md [SECIO allows participating peers to support a subset of algorithms]
GitHub
GitHub - libp2p/go-libp2p-tls: go-libp2p's TLS encrypted transport
go-libp2p's TLS encrypted transport. Contribute to libp2p/go-libp2p-tls development by creating an account on GitHub.
Verifiable Secret Sharing (this is interesting ; another in-depth banger) = https://www.jcraige.com/vss-forgery