★ ☆ ★   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 ***
05 · the checklist

Ordered by impact. If a line fails, that is the next thing to fix, not the last one. The top four are the difference between "annoying to crack" and "already cracked and nobody noticed".

  1. Entitlement is decided on the server
    The paid value arrives only after a server check. Client-side state cannot grant it.
  2. The grant is signed and names features, account, expiry, nonce
    A bare success flag is a gift to anyone with a hex editor.
  3. Signing key is asymmetric and never in the binary
    Symmetric keys in a client can forge as well as verify.
  4. Every response carries a freshness window
    Replay of one captured response must fail.
  5. Token TTL is minutes to hours, with refresh
    Long-lived tokens cannot be revoked in practice.
  6. Offline behaviour is a deliberate decision
    Lease window or online requirement, documented and supported.
  7. No master credential, API key or private key ships in the app
    Strings are read before logic. Recovery tooling finds them first.
  8. Build hash is sent with validation
    A hash you did not ship is the single strongest tamper signal.
  9. Integrity self-check exists on critical code sections
    Detection, not prevention. Worth it only with a server report.
  10. Canaries and decoy credentials are planted
    They must fail indistinguishably from a normal licence failure.
  11. Validation outcome telemetry is on
    Account, build hash, result. Nothing that reads like spyware.
  12. Revocation is granular: key, device, build
    Do not punish a whole account family for one leaked key.
  13. A kill switch exists and was tested on a real install
    Untested switches fail on the day you need them.
  14. Anti-tamper is ranked, not stacked
    Server decision beats packing. A packer over a local boolean is theatre.
  15. Anti-debug degrades quietly, it does not crash the machine
    A deliberate bugcheck is a support disaster and documents itself.
  16. The unprotected internal build is guarded like a secret
    Your own engineers are the easiest path to a clean binary.
!! IF YOU WANT IT TESTED BEFORE YOUR CUSTOMERS DO !!

That is the paid work. Scoped in writing, you get the check, the failure, the reproduction, and a fixed build retested. Client names stay off this site without written permission.

[ SERVICES ] [ CONTACT ]
[ PREV: 04 ] [ INDEX ]

✉ 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