Authenticator Secret Key Registration Gateway
This so-called Registration Gateway is made for people-clients to register their secret keys used for logging-in to a lightweight business server with no complicated credentials required.
After the registration, the clients use some TOTP authenticator app such as Google Authenticator to log in to the server's portal.
Server-side Usage
Installation
pip install uvia vapp skregister
Usage
## nano skregister.sh
export JWT_SECRET="very-strong-password-for-token-generating"
export SETUPKEY_ENCRYPT_SECRET="some-other-strong-password-for-secret-key-encrypting"
export SENDER_GMAIL_ADDRESS="your-own-gmail-address"
export SENDER_GMAIL_APP_PWD="your-own-gmail-application-password"
export TELEGRAM_BOT_TOKEN="your-own-telegram-bot-token"
export FILE_AVRO_DATA="./setupkeys.avro"
export TOKEN_EXPIRE_MINUTES=10
uvia -a vapp -m skregister [-p <PORT>] [-H <HOST>]
## chmod +x skregister.sh
## ./skregister.sh
Client-side Usage
Users to open the web page served by the above server in any modern web browser to perform the registration.
- First step: require an entry code for further process
- Enter user email or Telegram ID.
- Enter captcha produced by the page.
- Click Send Code button to ask a code sent to the very email or Telegram account.
- Second step: pick the entry code via email
- Open the registered email inbox.
- Look for an email related to entry code.
- Copy the entry code, it must be a five-letter uppercase random string.
- Third step: provide the entry code for the server to generate secret key
- Enter some proper name for new secret key.
- Paste the entry code which is picked in the second step.
- Click Register button to ask a QR code be shown.
- Scan the QR code with an authenticator app.
Detailed tips, tricks, and examples, can be found at project's repository https://github.com/asinerum/skregister
(C) 2026 Asinerum Conlang Project
Metadata
Release files for skregister 1.0.2
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 | Actions |
|---|---|---|---|---|
| skregister-1.0.2.tar.gz | 5.3 kB | Without provenance | Details for skregister-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| skregister-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for skregister-1.0.2-py3-none-any.whl |
Total release size: 11.1 kB
Release files / skregister-1.0.2.tar.gz
| Download URL | skregister-1.0.2.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8773a2e1bbcaffbe931c5164f234042c56b7dc2fa5069cb6215b866ff870526b
|
|
BLAKE2b-256 checksum How to use checksums |
8df5454b3c8642aa7ba750b1d6a1423e363951e842619d61592ef870422552df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / skregister-1.0.2-py3-none-any.whl
| Download URL | skregister-1.0.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e15487591fe3079570d6e2e1f2eb2697f274d28a5fa3ae419a0d901ded82552
|
|
BLAKE2b-256 checksum How to use checksums |
d514ce357b915e90f35244576113b0092fa5389ee328a406ad6c1c5d2f7a1c49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for skregister 1.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.