★ ☆ ★   W E L C O M E   T O   M Y   H O M E P A G E   ★ ☆ ★

NULLRAKE'S PAGE

last updated: NOV 19 2026  ·  hosted on a Pentium 133  ·  28.8k friendly
  *** WELCOME 2 MY HOMEPAGE *** IF U R SEEING THIS, THE PAGE LOADED OK *** DO NOT ENTER KEYS U DONT OWN *** SIGN MY GUESTBOOK *** BEST VIEWED IN NETSCAPE NAVIGATOR 4.0 @ 800x600 *** TELL UR FRIENDS *** THIS SITE IS ALWAYS UNDER CONSTRUCTION ***
01 · move the decision off the client

REE's whole static path exists because the answer to "is this licensed" is computed somewhere the customer controls. Flip the branch and the app believes itself licensed. No amount of clever in the binary changes that arithmetic. Moving the decision does.

DO THIS
  1. Make the server the only thing that grants value. The paid result, the export, the update, the premium data, the cloud action: those come back from your server after it checks entitlement. A patched client that never gets the payload has cracked nothing that matters.
  2. Sign the entitlement, not a boolean. Return a token that names the features, the account, the expiry and a nonce, signed with an asymmetric key. The client can verify it and cannot mint one. A bare {"success": true} is a gift.
  3. Keep the TTL short and refresh it. Minutes to hours, not years. A leaked or extracted token then expires on its own, and revocation becomes real instead of aspirational.
  4. Bind the token to something the attacker does not have. Account plus device fingerprint plus a rotating server-side secret. It does not stop a determined person with the real account, but it stops a copied token being posted to a forum.
  5. Decide what offline means before you ship. Offline mode means a cached grant the client can present forever. Either you accept a time-boxed offline lease, or the feature needs the network. Pick deliberately; both are defensible, "we never thought about it" is not.
Reality check. If your product genuinely does all its work locally and has no server, you cannot make the check unbreakable. You can only make breaking it expensive and detectable. Say so internally and budget accordingly instead of buying a packer and calling it done.
WHAT THIS COSTS YOU
  • One auth endpoint and a key pair. Days, not months.
  • A support story for "my internet is down". Plan it before launch.
  • Ongoing key rotation. Cheap, and the thing most teams skip.
[ INDEX ] [ NEXT: 02 SIGNATURES ]

✉ tip me (crypto) · notes & messages (SimpleX) · contact me · telegram bot · services
NETSCAPE NOW! IE 3.0 800x600 HTML 3.2
© 1997-2026 nullrake // this page is best viewed on a CRT // sign my guestbook