Menu

cryptship | Part 2 — Air-Gapped, On-Prem, Cloud: One Loader, Three Key Providers
📰

cryptship | Part 2 — Air-Gapped, On-Prem, Cloud: One Loader, Three Key Providers

DEV Community: docker·Ai2th·about 2 hours ago
#HbkmqfeY
#devtodocker#devto#dev#server#license
Reading 0:00
15s threshold

Ai2th

Posted on Nov 15

Edited on Nov 15

Customers run software in very different places: a disconnected network, their own data centre, or a cloud account. cryptship handles all three with one loader and one license format . The only thing that changes is how the content key is obtained.

🔌 Key providers

That choice is a single pluggable interface, pkg/keyprovider :

Mode Provider Binding Revocation

Air-gapped offline machine fingerprint, or none expiry only

On-prem / cloud online a per-license secret held by your server real : the server declines

Confidential attested SEV-SNP / TDX attestation gates the key planned: interface and mock only today

🛫 offline: no network, ever

Everything needed to unwrap the key is in the license and the machine. Revocation is by expiry : issue short-lived licenses and renew them. Binding policies none , strict and pool all work offline.

🌐 online: revocation that works

With online , the per-license binding secret stays on your server.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.