natesales

5 ms·

1.
by natesales 1y ago
All attestation verification happens client side. We have verifiers in Python [1] and Go [2] (which FFIs to our other SDKs like WASM and Swift). We push all the verification logic to the client so the verification process is entirely transp
2.
by natesales 1y ago
An attacker would need to compromise our build pipeline to publish a backdoored VM image [1] and extract key material to forge an attestation from the hardware [2]. The build process publishes a hash of the code to Sigstore’s transparency l
3.
by natesales 1y ago
We have to trust the hardware manufacturer (Intel/AMD/NVIDIA) designed their chips to execute the instructions we inspect, so we're assuming trust in vendor silicon either way. The real benefit of confidential computing is to
4.
by natesales 1y ago
The keys are generated on the CPU and never leave the enclave, but the data is decrypted on the CPU so it hits the registers in plaintext. When the enclave starts, the CPU does a few things: 1. The CPU does a key exchange with the GPU (in c
5.
by natesales 1y ago
The verified trust boundary extends from the CPU to GPU [1], and TLS encrypts all data to/from the enclave and client so we can't see anything in the clear. HTTP parsing and application logic happens on the CPU like normal. The GP
6.
by natesales 2y ago
AS34553 hosts my personal services (email, website, VM hosting, nuclear fusion reactor, etc). It's an "autonomous system" - the kind of network that enables announcing your own IP space with BGP.
7.
Show HN: OpenReactor – Open-Source Nuclear Fusion Reactor(github.com)
11 points by natesales 2y ago|2 comments
8.
Show HN: Pathvector – Secure and open-source BGP routing platform(github.com)
6 points by natesales 4y ago|0 comments
9.
Logknife – Remove sensitive information from logs(github.com)
1 points by natesales 4y ago|0 comments
10.
Show HN: "q", a DNS query tool with support for UDP, TCP, DoT, DoH, DoQ and ODoH(github.com)
140 points by natesales 4y ago|45 comments