TgCryptoRust
[!NOTE] This project is provided for educational and experimental purposes. The implementation follows public AES specifications and is tested against known vectors, but it has not received a formal third-party security audit. Do not treat it as a certified cryptographic module.
Rust-powered, AES-NI accelerated cryptography for Telegram clients.
TgCryptoRust is a drop-in replacement for TgCrypto, implemented in Rust and packaged for Python through PyO3 and Maturin. It implements the cryptographic algorithms Telegram requires, namely:
AES-256-IGE— used in MTProto v2.0.AES-256-CTR— used for CDN encrypted files.AES-256-CBC— used for encrypted passport credentials.
Requirements
- Python 3.9 through 3.14
- Rust 1.86+ (only when building from source)
Prebuilt wheels are available for common desktop and server platforms. Rust is only required when a wheel is not available for your platform.
Installation
pip install TgCryptoRust
Or with uv:
uv add TgCryptoRust
uv sync
API
def ige256_encrypt(data: bytes, key: bytes, iv: bytes) -> bytes: ...
def ige256_decrypt(data: bytes, key: bytes, iv: bytes) -> bytes: ...
def ctr256_encrypt(data: bytes, key: bytes, iv: bytes, state: bytes) -> bytes: ...
def ctr256_decrypt(data: bytes, key: bytes, iv: bytes, state: bytes) -> bytes: ...
def cbc256_encrypt(data: bytes, key: bytes, iv: bytes) -> bytes: ...
def cbc256_decrypt(data: bytes, key: bytes, iv: bytes) -> bytes: ...
Usage
IGE Mode
Note: Data must be padded to a multiple of the block size (16 bytes).
import os
import tgcrypto
data = os.urandom(1024)
key = os.urandom(32)
iv = os.urandom(32)
encrypted = tgcrypto.ige256_encrypt(data, key, iv)
decrypted = tgcrypto.ige256_decrypt(encrypted, key, iv)
assert decrypted == data
CTR Mode
CTR accepts arbitrary-length data. The state argument is a one-byte offset
inside the current keystream block, kept for TgCrypto compatibility.
import os
import tgcryptors
data = os.urandom(1000)
key = os.urandom(32)
iv = os.urandom(16)
state = b"\x00"
encrypted = tgcryptors.ctr256_encrypt(data, key, iv, state)
decrypted = tgcryptors.ctr256_decrypt(encrypted, key, iv, state)
assert decrypted == data
TgCrypto-compatible bytearray mode: data, key, iv, and state may also
be passed as bytearray. When iv or state are bytearray, they are
updated in place — after the call they hold the advanced counter and
residual offset, so passing the same objects to the next call continues the
stream across chunks. This is how pyrogram and its forks (kurigram, pyrofork,
...) drive the obfuscated TCP transports and CDN file downloads:
import os
import tgcrypto
key = os.urandom(32)
iv = bytearray(os.urandom(16))
state = bytearray(1)
first = tgcrypto.ctr256_encrypt(data[:100], key, iv, state) # iv/state advance in place
second = tgcrypto.ctr256_encrypt(data[100:], key, iv, state) # continues the stream
Passing plain bytes behaves as a stateless one-shot call.
CBC Mode
Note: Data must be padded to a multiple of the block size (16 bytes).
import os
import tgcrypto
data = os.urandom(1024)
key = os.urandom(32)
iv = os.urandom(16)
encrypted = tgcrypto.cbc256_encrypt(data, key, iv)
decrypted = tgcrypto.cbc256_decrypt(encrypted, key, iv)
assert decrypted == data
Streaming API
Use the streaming classes when processing one logical stream in chunks. The key schedule is expanded once and reused.
import os
import tgcryptors
key = os.urandom(32)
iv = os.urandom(16)
data = os.urandom(1024)
stream = tgcryptors.Ctr256(key, iv)
encrypted = stream.update(data[:300]) + stream.update(data[300:])
IGE streaming is also available for block-aligned chunks:
import os
import tgcrypto
key = os.urandom(32)
iv = os.urandom(32)
data = os.urandom(1024)
stream = tgcrypto.Ige256(key, iv)
encrypted = stream.encrypt(data[:512]) + stream.encrypt(data[512:])
Runtime Metadata
import tgcryptors
print(tgcryptors.__version__)
print(tgcryptors.runtime_info())
Imports
Existing TgCrypto users can keep importing tgcrypto:
import tgcrypto
New code can import the branded module directly:
import tgcryptors
Both modules expose the same API.
Compatibility
TgCryptoRust is a full drop-in replacement. All function names, argument orders, return types, and validation behavior match the original TgCrypto:
| Function | Arguments |
|---|---|
ige256_encrypt |
(data, key, iv) |
ige256_decrypt |
(data, key, iv) |
ctr256_encrypt |
(data, key, iv, state) |
ctr256_decrypt |
(data, key, iv, state) |
cbc256_encrypt |
(data, key, iv) |
cbc256_decrypt |
(data, key, iv) |
Architecture
tgcryptors-core— Rust AES primitive and Telegram block modes (IGE, CTR, CBC).tgcryptors-python— PyO3 extension module exposing the native API.python/tgcrypto— Compatibility shim re-exportingtgcryptorsfor existing imports.tests/— Python unit tests covering the public API.
On x86 and x86_64, AES-NI is detected at runtime when the crate is built with
the default aesni feature. Other targets use a software fallback (T-table based,
not guaranteed constant-time on every CPU).
Expanded key material is zeroized on drop using the zeroize
crate, which guarantees the compiler will not optimize away the clearing.
Migrating From TgrCrypto
TgrCrypto is deprecated in favor of TgCryptoRust.
pip uninstall TgrCrypto
pip install TgCryptoRust
Existing code that imports tgcrypto can remain unchanged.
Development
# Set up environment
uv sync --python 3.14
# Build and install the native module
uv run maturin develop --release
# Run Python tests
.venv/bin/python -m unittest discover -s tests -v
Run the Rust checks:
cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --release
Build a wheel:
uv build --wheel
Changelog
1.3.1
ctr256_encrypt/ctr256_decryptnow acceptbytearray(andbytes) fordata,key,iv, andstate. Whenivorstateare passed asbytearray, the advanced counter and residual byte offset are written back in place, matching TgCrypto's stateful semantics. This fixes a crash at connect time with pyrogram and its forks, whose obfuscated TCP transports and CDN downloads passbytearrayand rely on the in-place carry (issue #4).
1.3.0
- Bumped MSRV from Rust 1.83 to 1.86.
- Replaced manual key zeroization with the
zeroizecrate for guaranteed compiler-resistant memory clearing. - Removed deprecated
generate-import-libfeature (no-op since PyO3 0.29). - Added CI job to verify MSRV compliance.
- Fixed clippy warnings and imprecise documentation comments.
- Changed license from LGPLv3+ to MIT.
License
MIT — Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software.
© 2026-Present Joy.
Metadata
Release files for TgCryptoRust 1.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tgcryptorust-1.3.1.tar.gz | 37.2 kB | Details |
Built distributions (wheels)
Total release size: 7.8 MB
Release files / tgcryptorust-1.3.1.tar.gz
| Download URL | tgcryptorust-1.3.1.tar.gz |
|---|---|
| Size | 37.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
658f8356a5cd674f163422588efde990524c362530ea897836a2e6b7df31118b
|
|
BLAKE2b-256 checksum How to use checksums |
3e1214b06a9df3be031a275cb235f2854377cba81d7e238a38bb0fd5136bf887
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp314-cp314-win_amd64.whl
| Download URL | tgcryptorust-1.3.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 190.7 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e4ab80589cb59805ab66346a1a96f4e8a29e13e3324d4b57f34352782230adfc
|
|
BLAKE2b-256 checksum How to use checksums |
bdeaebc5365898eeffb05a22e17881463f3aa109cf7b0df9146855756219940a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp314-cp314-manylinux_2_34_x86_64.whl
| Download URL | tgcryptorust-1.3.1-cp314-cp314-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 285.6 kB |
| Tags | CPython 3.14 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
67e98fe4a9c98444807520494e8c9e15558e5fb96b5d44d1f42f04f6a165ff4c
|
|
BLAKE2b-256 checksum How to use checksums |
63ace5074788949a40c1ee2f6863ce7a553dfdbe1ba8e0141b3b33ebced2460c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp314-cp314-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | tgcryptorust-1.3.1-cp314-cp314-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 284.2 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
0f87eec575a952dcef9c9a2915b088b999668426bfbbeb5ed7a10f81316c3017
|
|
BLAKE2b-256 checksum How to use checksums |
9db834852d631af8e5899d52c4c19d267871cae3dbba6c2cd2a1fc332f52bc09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | tgcryptorust-1.3.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 273.3 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
9a70f31ea34028535cb3b44f353596f61c02734a49b61e60e15c8e4720d9fe91
|
|
BLAKE2b-256 checksum How to use checksums |
2f436a539ef3eda06ba7b542723a934e7121a5133c2cec430cf59af3f657861f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | tgcryptorust-1.3.1-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 252.5 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
61480fff7fbeedcacfb432eade3a1a9997e762bfaaebd0a2b38829e7ff958544
|
|
BLAKE2b-256 checksum How to use checksums |
1ce819204fb479797c808457373ca95c098bed42beceee1c1ccb6bf8871487a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp313-cp313-win_amd64.whl
| Download URL | tgcryptorust-1.3.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 190.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6379642d846e92c5e548759c2e54c39096724eb52224d7a94cbb9d4b1cc13d95
|
|
BLAKE2b-256 checksum How to use checksums |
c4bebd04acb0ee7ab21cc629dcd1bb04c1c14d67e98e1c579dd07591541bab1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | tgcryptorust-1.3.1-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 285.2 kB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
ccd32bd01387143735fc55c7f660d88a0e01e5823c5d9f0569ba4fae4ee12ad2
|
|
BLAKE2b-256 checksum How to use checksums |
d6f389a06fc612fc62bc1af4db118773ae075b43bc17cc4ffe2822d3faf869c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | tgcryptorust-1.3.1-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 284.1 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
318a70b8d46cc581272fc4cae8a4b1cc15eea978a50e5a876bc0cdd9809d8448
|
|
BLAKE2b-256 checksum How to use checksums |
a74cfba79f360cfbd8dd1cfeb00ffc127839ff0462776d240fcec049f2dad071
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | tgcryptorust-1.3.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 273.2 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
a0b6113c24df713d03e805f4651449b2b9cd3a38e2d871482527c0ece5d57b26
|
|
BLAKE2b-256 checksum How to use checksums |
8773fae5e0d61de2622c628afe3ae2bae527f583d4d0591b9cdafe2faf6cacde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | tgcryptorust-1.3.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 252.2 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
51c3aa1b9a397b3a9e84346d7d0ec61d54c87af24c0531a83d6a6a91721a5057
|
|
BLAKE2b-256 checksum How to use checksums |
9ed691e24e5ee6064737591d9cab8211b5e1f62d1120410fdf099596adaf3ad2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp312-cp312-win_amd64.whl
| Download URL | tgcryptorust-1.3.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 190.4 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
bea45d9308dcaa2b2f808a7a848bf7953dda61087af6e12491c554fcb6533bea
|
|
BLAKE2b-256 checksum How to use checksums |
801208cba4e9940e9eebed291bf5c6ef17741ec016aedad54357fe6a77e7cbb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | tgcryptorust-1.3.1-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 284.9 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
be81c52ee05cef4fd81a91071758edb1b8e409c28783857c6bf113ce84463e9f
|
|
BLAKE2b-256 checksum How to use checksums |
db558846333b800761551d4766891574c178712d1904d7fc29f5685a2995a7de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | tgcryptorust-1.3.1-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 284.0 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
359d1746a68a8089d5fef8d52cef0a803324c36474a07e6c67179e60af6cc527
|
|
BLAKE2b-256 checksum How to use checksums |
d5c581694dfdb252fe394dc401c7509e51f223401622fb3d7f0b386b2df4d8cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | tgcryptorust-1.3.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 273.0 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
74f2f92d69ce91e4443f379da3790969035323113e52c5fe7fce54390af491c5
|
|
BLAKE2b-256 checksum How to use checksums |
3126343f9d30b0e10a0ce9fad43956fbb39ab26a9bfba88284fbed81f88f9ad9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | tgcryptorust-1.3.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 252.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a182b4fd46b29b6d2ed3be547ee432640d709fb0716a1738fd2a671ce3e59a87
|
|
BLAKE2b-256 checksum How to use checksums |
bae5580d6d391112a5fb7a896eb5d55e9c4c171066f1b7f51ee44a33ae1059b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp311-cp311-win_amd64.whl
| Download URL | tgcryptorust-1.3.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 192.9 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
1071d8368e3b1a90f7ba9d29ed8c1f0df64b28fe2357483084668746adf04a6f
|
|
BLAKE2b-256 checksum How to use checksums |
8dc03530d31faf05b86e1840e3899ce55c37b483f8c2432678513374c6455b2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | tgcryptorust-1.3.1-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 285.4 kB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
999e74c71a178c014cc88dda250c5ecb3ff12ae005a2255020fc7ae68314e151
|
|
BLAKE2b-256 checksum How to use checksums |
4e078c196ea7565ca68998e4e9a0a9db811c5cc294506c97d7bcf4d23f111dfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp311-cp311-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | tgcryptorust-1.3.1-cp311-cp311-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 284.9 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
3efde80d8f6494fc7300f042e3d5ea7a092d4eb5b287876f2523a05350a4f347
|
|
BLAKE2b-256 checksum How to use checksums |
db363146f1e99038b23e8736dbf94261f3037f13824f64c85b1159d3d6fff247
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | tgcryptorust-1.3.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 274.0 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
a029a910b6f81996ec0bec7516c8a9fd2193730f31213a5564d7113fb3dbf389
|
|
BLAKE2b-256 checksum How to use checksums |
b8c67fe557f21b27f84340bcc10fdd9f068eb5aab7df3e93f2a3efd62710b3fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | tgcryptorust-1.3.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 253.5 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8fe2618e3ea71737e9883b735201dfd7d385defed318848b10d69aad0d73266f
|
|
BLAKE2b-256 checksum How to use checksums |
b3f9b3295009cd9a068a9aff5a98ff36a6a564e9056bd96808b8fff88a4376eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp310-cp310-win_amd64.whl
| Download URL | tgcryptorust-1.3.1-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 193.2 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c6aae16bde99b197fdc955eca5ee62ba7a0890da13f1890003d96dee5464f639
|
|
BLAKE2b-256 checksum How to use checksums |
2e7909a16733fd2e886baa25a5ae43e808090412d5bcb01481361f7d8a3d9196
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp310-cp310-manylinux_2_34_x86_64.whl
| Download URL | tgcryptorust-1.3.1-cp310-cp310-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 285.5 kB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
15b17d1c6f6cf125779de68896cc409646d91a6462d22ade20ce4b9a063c1bf0
|
|
BLAKE2b-256 checksum How to use checksums |
aa369d6682617d0f7d503f8892d089a4777915ec9e4db2afb3e70b0c8c2c82ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | tgcryptorust-1.3.1-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 285.0 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
1d670f724d7ef7b9783e8582c64eebe1e504f0d4787230303bc1e647e18c8f24
|
|
BLAKE2b-256 checksum How to use checksums |
4fbee5543ea6c5b412b525b724f529284c60cb251a85620497a0919fc38caeeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | tgcryptorust-1.3.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 274.2 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
d1f354b86d889438859ac89780755b1e22698f78d06c63bee3fdf58a86915c59
|
|
BLAKE2b-256 checksum How to use checksums |
351a7412218cde9c6684c96caa0a1d5b0872e6916b7d8d21e193eebe281656da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | tgcryptorust-1.3.1-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 253.6 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
58f57703fdfa9e8f8242fd4c6c589663aa22f1787c4de9569d143be2de9e37fc
|
|
BLAKE2b-256 checksum How to use checksums |
96060cd6bf421d5996c481bf933a85319b68a16e42f8cdbd329b9e3679159eb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp39-cp39-win_amd64.whl
| Download URL | tgcryptorust-1.3.1-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 195.9 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d6f6019e488b3234ae65b4e87b4d70d2d1ffbdc770b6117d00e7b23fde484ef6
|
|
BLAKE2b-256 checksum How to use checksums |
9a39dfc3da3f66bdf2c8eae78552294bee291ab4f4cf4f1fa0d9a3074d4b8e21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp39-cp39-manylinux_2_34_x86_64.whl
| Download URL | tgcryptorust-1.3.1-cp39-cp39-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 287.4 kB |
| Tags | CPython 3.9 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
9bd65de77ead40f032d5a32659281ba2f1e192fe748d1303f4d403e2759e6077
|
|
BLAKE2b-256 checksum How to use checksums |
178f8d4d3230016f8f9b6ad02a67c417168e94252e5bb332a0ad27d25d70aa98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp39-cp39-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | tgcryptorust-1.3.1-cp39-cp39-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 286.6 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
acfbeae8ca9a3a736940e74421c4a73b75761ac17386ce68c89f67e52b5c9738
|
|
BLAKE2b-256 checksum How to use checksums |
f500f611e1046b5a7a5bbbe267807d0b46c88e4c9601a4ad9b2a7060db22f7db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | tgcryptorust-1.3.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 275.8 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
ce545162917e3338fef15d48a72cda5034f47fffefdbb0390cfcc486b63baf82
|
|
BLAKE2b-256 checksum How to use checksums |
cd00e65350e696dd0ed6e76a364965ceeaef9451ac26406f8ab49225e623e9c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / tgcryptorust-1.3.1-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | tgcryptorust-1.3.1-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 255.2 kB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
dc3f28aa53705442a26e3fd42484f1452acc621b371522dee38b981d5e1a6deb
|
|
BLAKE2b-256 checksum How to use checksums |
bbd23caf678d003e37233250cc007563060952f2243f362cfddecfa54fedb890
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency log