bschaatsbergen

7 ms·

1.
by bschaatsbergen 10d ago
Joke's on them, I don't have the key either.
2.
by bschaatsbergen 10d ago
Thanks for sharing Ted!
3.
by bschaatsbergen 10d ago
What mjg59 says. The benchmarks are against a vTPM, that was what I had access to, and it's the environment I'm implementing the RATS side in. Worth adding that not every outbound connection needs to go through the TPM (IMO). It&#
4.
by bschaatsbergen 10d ago
Author here. There's a benchmark table further down the post, the numbers come from this repo if you want to run them yourself: https://github.com/bschaatsbergen/go-tpm-tls-bench
5.
by bschaatsbergen 10d ago
Author here. All of it is mine, the library ( https://github.com/bschaatsbergen/go-tpm-tls ) and the benchmarks ( https://github.com/bschaatsbergen/go-tpm-tls-bench ) and the working notes. English is
6.
by bschaatsbergen 10d ago
That's right, I'm learning in public here. That draft is a different direction though, they change the handshake: new TLS extensions carry the evidence, and the far end appraises the platform during the connection. What I'm d
7.
Signing TLS handshakes inside a TPM(bschaatsbergen.com)
36 points by bschaatsbergen 10d ago|46 comments
8.
by bschaatsbergen 2mo ago
Author here, thanks for posting this. Been going deeper on TPMs lately, working through machine identity after remote attestation, the point where you've proven a machine is genuine but still need it to prove which machine it is to som
9.
Show HN: Marmot, context layer for agents and humans(marmotdata.io)
17 points by bschaatsbergen 3mo ago|4 comments
10.
by bschaatsbergen 9mo ago
That's, indeed, a spec limitation, not something cek can solve. If you're interested in provenance tracking, you might want to look at Sigstore's cosign attestations or GUAC (Graph for Understanding Artifact Composition).
11.
by bschaatsbergen 9mo ago
Skopeo and crane are both fantastic tools, but they address different problems at a different level. Skopeo and crane operate at the image registry level, handling pulling, pushing, synchronizing, etc. cek is focused on what's in the c
12.
by bschaatsbergen 9mo ago
While they may look similar at first glance, Dive and Cek target different use cases. Dive is great at visualizing layer content and analyzing image efficiency, but requires the Docker daemon and can't extract file contents. Cek is dae
13.
List, inspect and explore OCI container images, their layers and contents(github.com)
49 points by bschaatsbergen 9mo ago|11 comments
14.
Multi-resolver DNS dialer for Go with race, fallback, and consensus strategies(github.com)
3 points by bschaatsbergen 11mo ago|0 comments
15.
Typosquatting GitHub Container Registry `Ghrc.io`
15 points by bschaatsbergen 1y ago|1 comments
16.
Zns: CLI tool for querying DNS records with readable, colored output(github.com)
30 points by bschaatsbergen 2y ago|6 comments
17.
Replicating AWS RDS automated backups to a different region(binx.io)
2 points by bschaatsbergen 4y ago|0 comments
18.
Pull AWS DynamoDB Locally(bschaatsbergen.com)
2 points by bschaatsbergen 5y ago|0 comments
19.
Pre-Jitting in AWS Lambda(bschaatsbergen.com)
2 points by bschaatsbergen 5y ago|0 comments
20.
Pre-jitting in Lambda (using CrossGen) to reduce .NET cold starts(bschaatsbergen.com)
2 points by bschaatsbergen 5y ago|0 comments
21.
by bschaatsbergen 5y ago
Good to know you enjoyed the read!
22.
by bschaatsbergen 5y ago
Both Marc Brooker (lead developer on the AWS Lambda team) giving the talks at Re:Invent as I mentioned in the footnotes, and the official documentation that's out there will provide you with a lot of information.
23.
by bschaatsbergen 5y ago
Great article @mlerner