Menu

cryptship | Part 3 — An Honest Threat Model, and the Hardening That Raises the Cost
📰

cryptship | Part 3 — An Honest Threat Model, and the Hardening That Raises the Cost

DEV Community: devsecops·Ai2th·about 2 hours ago
#5z4NtCmv
#devtodevsecops#devto#dev#cryptship#root
Reading 0:00
15s threshold

Ai2th

Posted on Nov 15

Edited on Nov 15

Every "protect your code" product has to answer one question honestly: what about root? This part is cryptship's answer.

🧱 Where the line is

The image on disk is ciphertext. But once your app runs, its plaintext is in the container's memory, and root on the host can read that memory . No user-space trick changes that. Only two things truly do:

a confidential-compute key provider (SEV-SNP or TDX with attestation), or

keeping the crown-jewel logic server-side .

Everything else in cryptship raises the cost. We would rather say that plainly than sell you a lock that is not there.

🔧 Three ways cryptship raises the cost

1. Ship compiled code, not source

cryptship pack --transform-cmd "<your toolchain>" …

Enter fullscreen mode

Exit fullscreen mode

The transform runs over a copy of your app before it is encrypted.…

Continue reading — create a free account

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