certanix-verify 0.14.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,41 @@
1
+ # GENERATED FILE. DO NOT EDIT.
2
+ #
3
+ # The public build of packages/certanix-verify/src/certanix_verify/__init__.py,
4
+ # generated by tools/vendor_verify_core.py. Edit the SOURCE and re-run the generator.
5
+
6
+ """certanix-verify — offline verification of Certanix evidence packs.
7
+
8
+ Self-contained: the standard library plus ``cryptography``. No network, no cosign
9
+ binary, no transparency-log lookup, nothing from the Certanix platform at runtime.
10
+
11
+ The verification logic in ``_core`` is vendored verbatim from the platform's
12
+ ``certanix/verify_core.py`` by a generator, and the schema/gate data in
13
+ ``descriptors.json`` is serialised from the platform's live models and registries. CI
14
+ asserts both are current and that this verifier agrees with the platform's on every
15
+ case in the conformance corpus. There is one implementation; this is its copy.
16
+
17
+ VERIFICATION SCOPE: this checks that the pack's canonical bytes match the detached
18
+ signature made by the key you supply. It does not tell you whose key that is. Confirm
19
+ the key's fingerprint against an out-of-band source before trusting what it says.
20
+ """
21
+
22
+ from __future__ import annotations
23
+
24
+ __version__ = "0.14.0"
25
+
26
+ from ._core import ( # noqa: F401
27
+ VerificationResult,
28
+ VerificationStatus,
29
+ canonical_pack_bytes,
30
+ verify_canonical_bytes,
31
+ verify_pack_bytes,
32
+ )
33
+
34
+ __all__ = [
35
+ "__version__",
36
+ "VerificationResult",
37
+ "VerificationStatus",
38
+ "canonical_pack_bytes",
39
+ "verify_canonical_bytes",
40
+ "verify_pack_bytes",
41
+ ]
@@ -0,0 +1,30 @@
1
+ # GENERATED FILE. DO NOT EDIT.
2
+ #
3
+ # The public build of packages/certanix-verify/src/certanix_verify/__main__.py,
4
+ # generated by tools/vendor_verify_core.py. Edit the SOURCE and re-run the generator.
5
+
6
+ """``python -m certanix_verify`` — the same CLI as the ``certanix-verify`` script.
7
+
8
+ The console script is the documented entry point, but it only exists once the package
9
+ is *installed*. Someone reading the evidence from a source checkout, or from an
10
+ unpacked sdist, has the code and no script — and the first thing they try is
11
+ ``python -m``. Without this module that fails with "No module named
12
+ certanix_verify.__main__", which reads like the verifier is broken rather than like
13
+ the shell is missing a PATH entry.
14
+
15
+ So this file exists to make the module form work everywhere the code does:
16
+
17
+ python -m certanix_verify verify pack.json --key cosign.pub
18
+
19
+ It adds nothing and decides nothing — it is the console-script entry point, reached
20
+ by the other route.
21
+ """
22
+
23
+ from __future__ import annotations
24
+
25
+ import sys
26
+
27
+ from .cli import main
28
+
29
+ if __name__ == "__main__":
30
+ sys.exit(main())