Description
Easy-to-use command-line tool for certificate management.
Features
Simple command-line UI.
Good defaults, sets up common extensions automatically.
PGP- and password-protected private keys.
OCSP and CRL info settings.
Supports EC, RSA and DSA keys.
Dependencies
Python cryptography module (version >= 3.1).
(Optional) gpg command-line tool to decrypt files.
Summary
Generate new key:
sysca new-key [--password-file TXT_FILE] [--out DST] sysca new-key ec[:<curve>] [--password-file TXT_FILE] [--out DST] sysca new-key rsa[:<bits>] [--password-file TXT_FILE] [--out DST] sysca new-key dsa[:<bits>] [--password-file TXT_FILE] [--out DST]
Create certificate signing request:
sysca request [-h] --key KEY_FILE [--password-file PSW_FILE]
[--out OUT_FILE] [--outform FMT] [--text] [--rsa-pss]
[--subject DN] [--san GNAMES] [--usage USAGE] [--CA] [--path-length DEPTH]
[--crl-urls URLS] [--issuer-urls URLS] [--ocsp-urls URLS]
[--ocsp-must-staple] [--ocsp-must-staple-v2] [--ocsp-nocheck]
[--permit-subtrees GNAMES] [--exclude-subtrees GNAMES]
[--require-explicit-policy N] [--inhibit-policy-mapping N]
[--inhibit-any N] [--add-policy POLICY]
Create selfsigned certificate:
sysca selfsign [-h] [--out OUT_FILE] [--outform FMT] [--text]
--key KEY_FILE [--password-file PSW_FILE]
[--not-valid-before DATE] [--not-valid-after DATE] [--days DAYS]
[--serial-number SN] [--rsa-pss]
[--subject DN] [--san GNAMES] [--usage USAGE] [--CA] [--path-length DEPTH]
[--crl-urls URLS] [--issuer-urls URLS] [--ocsp-urls URLS]
[--ocsp-must-staple] [--ocsp-must-staple-v2] [--ocsp-nocheck]
[--permit-subtrees GNAMES] [--exclude-subtrees GNAMES]
[--require-explicit-policy N] [--inhibit-policy-mapping N]
[--inhibit-any N] [--add-policy POLICY]
Sign certificate signing request:
sysca sign [-h] [--out OUT_FILE] [--outform FMT] [--text] --request CSR_FILE
--ca-info CRT_FILE --ca-key KEY_FILE [--password-file PSW_FILE]
[--not-valid-before DATE] [--not-valid-after DATE] [--days DAYS]
[--serial-number SN] [--reset] [--rsa-pss]
[--subject DN] [--san GNAMES] [--usage USAGE] [--CA] [--path-length DEPTH]
[--crl-urls URLS] [--issuer-urls URLS] [--ocsp-urls URLS]
[--ocsp-must-staple] [--ocsp-must-staple-v2] [--ocsp-nocheck]
[--permit-subtrees GNAMES] [--exclude-subtrees GNAMES]
[--require-explicit-policy N] [--inhibit-policy-mapping N]
[--inhibit-any N] [--add-policy POLICY]
Create or update CRL file:
sysca update-crl [-h] [--out OUT_FILE] [--outform FMT] [--text]
--ca-info CRT_FILE --ca-key KEY_FILE [--password-file PSW_FILE]
[--crl CRL_FILE] [--crl-number VER] [--delta-crl-number VER]
[--crl-scope SCOPE] [--crl-reasons REASONS] [--indirect-crl]
[--issuer-urls URLS] [--delta-crl-urls URLS]
[--last-update DATE] [--next-update DATE] [--days DAYS]
[--revoke-certs FN [FN ...]]
[--revoke-serials NUM [NUM ...]]
[--reason REASON] [--invalidity-date DATE] [--revocation-date DATE]
Display contents of CRT, CSR or CRL file:
sysca show FILE
1 maintainer
Metadata
1 maintainer
Release files for sysca 2.3
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 | |
|---|---|---|---|---|
| sysca-2.3.tar.gz | 107.6 kB | Without provenance | Details |
Release files / sysca-2.3.tar.gz
| Download URL | sysca-2.3.tar.gz |
|---|---|
| Size | 107.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a188b44361cd834ff2412893eddb838b696e8f701b517eccffc5b02a46df075
|
|
BLAKE2b-256 checksum How to use checksums |
f1dc722870d1a3c84c78f11e6283492910c003b8a320fc46ee9d69d2512ed5d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.12
|
Security for sysca 2.3
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.
