Analysis

Analyze pasted Windows .reg license file

Analysis:
Inspected registry keys and fields, inferred purpose and machine-binding from values and checksums.
Conclusion:
File is a Glenisys/GSP Cor license with CPU-based fingerprint, x64 version 6, expires 2027-11-21; checksums bind data to machine so editing will invalidate the/

Tools: list_files, web_search

Run it yourself

Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SOFTWARE\Glenisys\License] [HKEY_LOCAL_MACHINE\SOFTWARE\Glenisys\License] "Checksum"="9a7b18e9-dde1bdaf-7cbe0c03-bf7e298b" "Ethernet"="" "Processor 1"="00610f01-00000000-00000000" "Processor 2"="00610f01-00000000-00000000" "Processor 3"="00610f01-00000000-00000000" "Processor 4"="00610f01-00000000-00000000" "Serial"="100555" [HKEY_LOCAL_MACHINE\SOFTWARE\GSP\License\Cor] "Checksum"="6500107c-8605baa3-4fd9cef8-d01f850d" "Created"="2026/11/21" "Expire"="2027/11/21" "Company"="PH01A063" "Type"="Personal" "License"="5c0a3c4f-9fe5a8d8-a18d4b4e-55f3ebc2" "Platform"="x64" "Version"="6" [HKEY_LOCAL_MACHINE\SOFTWARE\GSP\License\Cor\Cor] "Checksum"="9cef1eb4-312cc6d7-38354bae-ebce3f70" "Created"="2026/11/21" "Expire"="2027/11/21" "License"="5c0a3c4f-9fe5a8d8-a18d4b4e-55f3ebc2" "Platform"="x64" "Version"="6"

Dr.Binary
list_files
web_search
web_search
web_search

You've pasted a Windows Registry Editor (.reg) license file — there's no question attached, so here's my read of it, and tell me what you'd like to do with it.

What this file is

A license/activation file for Glenisys software (Glenisys Kft. — the Hungarian member of Jura Group that builds security-printing software such as Corvina). The GSP\License\Cor tree most plausibly holds the license for the Cor (Corvina) module of a Glenisys "GSP" platform, version 6, x64. That part is an informed guess — the registry keys confirm the vendor, but I couldn't confirm the exact GSP product name online.

Structure

1. Hardware fingerprint — HKLM\SOFTWARE\Glenisys\License

  • [-HKEY...] delete + recreate is the standard .reg "replace key" idiom — importing overwrites the whole key.
  • Processor 1..4 = up to 4 CPU slots, 00610f01-00000000-00000000. The first 8 hex digits look like a CPUID-style signature (stepping=1, model=0, family=F, ext-model=6); the two zeroed groups look like a processor-serial/PSN field that's unused/zeroed on modern CPUs.
  • Ethernet = empty — no MAC was captured, so the fingerprint is CPU-based only.
  • Serial = 100555, the license serial.
  • Checksum = 32 hex chars (4×8 groups, like the other GUID-style values) — presumably a keyed hash over the fingerprint fields, so the fingerprint can't be edited without regenerating it.

2. Product license — HKLM\SOFTWARE\GSP\License\Cor (+ nested Cor\Cor)

  • Company = "PH01A063" (looks like an internal customer/project code, not a name)
  • Type = Personal; Platform = x64; Version = 6
  • Created 2026/11/21 → Expire 2027/11/21 — a 1-year subscription
  • License = same ID (5c0a3c4f-...) in both keys, but each key carries its own Checksum — consistent with the checksum covering the fields plus the key context.

Practical implications

  • The license is machine-bound: the Glenisys\License fingerprint must match the machine it was generated for. Importing this .reg on a different PC will recreate the values, but validation will fail (or the app will regenerate/detect a mismatch), and no tool can recompute the vendor's checksums without their algorithm.
  • Both checksums are 128-bit values presumably derived from a secret-salted hash — editing any field (serial, expiry, type) invalidates them.
  • If this is a backup you made before reinstalling the same machine, importing it back is the right move; if validation still fails, the usual culprits are a changed CPU or a license version 5→6 mismatch.

What's the goal here — restoring/migrating this license, or analyzing how the licensing scheme works? If it's the latter, upload the binary that reads these keys (the app or its license DLL) and I can reverse the checksum/validation logic from there. (Generating new valid licenses for the vendor's software is not something I'll do, but understanding and verifying the mechanism is fine.)