A
U
T
H
E
N
T
I
C
A
T
I
O
N
E
N
G
I
N
E
ClavisAUH
Product
Sign-in for apps
01
Keys, accounts, trials
Devices & HWID
02
Machines known part by part
Protect 24/7
03
Know the moment someone tries
Signed releases
04
Every build carries a signature
Seller API
05
Resell and stay in charge
The five utilities on the home page
Security
Protect Hub
Pricing
Docs
Sign in
Get started
Menu
Product
Sign-in for apps
Devices & HWID
Protect 24/7
Signed releases
Seller API
Security
Protect Hub
Pricing
Docs
Sign in
Get started
Protect Hub · ClavisAUH
VI
Tiếng Việt
Tiếng Việt
Library
Protection basics in one hour
Five foundations for any licensed software
01
Why a binary can never keep a shared secret
Everything inside the file you ship can be read. An API key, a password or a decryption key shared by every buyer is a key for everyone. A sound design leaves only public material in the file.
4 min read
02
Signing requests and responses: what each signature proves
The device's signature proves a request came from that machine unchanged. The app's signature proves the answer came from the real server. Missing either one leaves a door open.
4 min read
03
Stopping replays: nonces, time and binding to the request
A valid request recorded once stays valid if the server does not remember seeing it. One-time nonces, a narrow time window and short sessions close this attack together.
3 min read
04
Let the server hold the verdict
An if-statement in a binary can be patched to always be true. What cannot be patched is data or computation that only the server hands out, and only to a valid session.
4 min read
05
Safe offline licenses: signed tokens, short lives, untrusted clocks
Working without a network is convenient, but every offline day is a day a revoked license keeps running. Signed tokens, short lifetimes and rewind detection keep both promises.
4 min read