Re:Kimi-K3 Releases on HuggingFace 7/27
by ljlolel on Monday July 27, 2026 @10:51AM
(#49070528)
can send safely context if there’s confidential computing ala my site https://trustedrouter.com/
[ Parent
| on HN ]
How do you prove you are running exclusively on Nitro enclave instances or GCP confidential spaces?
Is your local compute airgapped?
Re:Kimi-K3 Releases on HuggingFace 7/27
by trollbridge on Monday July 27, 2026 @02:16PM
(#49073521)
My local compute is used by me, and I'm accountable to myself whether or not is secure. So to a certain degree, I trust myself and also know what limitations / potential vulnerabilities it might have.
Re:Kimi-K3 Releases on HuggingFace 7/27
by well_ackshually on Monday July 27, 2026 @01:26PM
(#49072841)
I trust my local compute quite a bit more than a random project that has "trusted" in its name.
Seems clear from their website?
1. Their API server provide an attestation JWT. This JWT is signed by Google's private key. 2. The attestation has details on the running container. I suppose the container host is a Google-provided distro and Google's signer will verify that the OS is theirs and up-to-date. 3. They could've proxy the attestation. To prove this is not the case, the field eat_nonce include the TLS certificate fingerprint, which should match the API server you're connecting to. I suppose you will need to pull their container and verify from the source that the container itself generate the private key, it never leaves the container, and the container has no way to run arbitrary code such as SSH or vulnerabilities.