XLD Logchecker
This is a fork of https://github.com/puddly/xld_logsigner, to be used within our downstream applications, removing unnecessary functionality that we do not need.
Based heavily on barrybingo/xld_sign. This is a complete disassembly of the XLD log signing algorithm, re-implemented in Python 3.5+.
Usage
usage: xld.py [-h] (--verify | --sign) FILE
Verifies and resigns XLD logs
positional arguments:
FILE path to the log file
optional arguments:
-h, --help show this help message and exit
--verify verify a log
--sign sign or fix an existing log
Overview
The final code isn't pretty, but it is simple enough to describe the algorithm.
- The log is encoded as UTF-8 and hashed with a SHA-256 variant that uses a different IV.
- The digest is converted to hex and the string
\nVersion=0001is appended onto the end. - The versioned hex-digest is then passed through an unidentified scrambling function that operates on pairs of bytes (open an issue if you recognize it).
- The resulting bytestring is then encoded using a 65-character lookup table with a strange mapping.
Metadata
Release files for xld-logchecker 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| xld_logchecker-0.8.0.tar.gz | 5.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xld_logchecker-0.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.7 kB
Release files / xld_logchecker-0.8.0.tar.gz
| Download URL | xld_logchecker-0.8.0.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be82103a8d348400fe3394f1e0e10991561def5baa7170bc4a901ac74c5a6688
|
|
BLAKE2b-256 checksum How to use checksums |
9a287f22d1e1173062f0d1c018718a82fc70b59098dd341114ae3cddb535f042
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 31, 2026.
Transparency logRelease files / xld_logchecker-0.8.0-py3-none-any.whl
| Download URL | xld_logchecker-0.8.0-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cc7e86f8733df33ccb90220ce0461fc05545291e1ee18198c128e0c2d5f86f3
|
|
BLAKE2b-256 checksum How to use checksums |
08c597377ea0f9e25297347c4b22e5b756653140258cbfa996e582ed7f6ef6e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 31, 2026.
Transparency logSecurity for xld-logchecker 0.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xld_logchecker-0.8.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.