Collection of tools producing signed artifacts
Project description
Set of scripts used for signing artifacts via configured signers
Requirements
Python 3.7+
Features
pubtools-sign
pubtools-sign-clearsign
pubtools-sign-containersign
Setup
$ pip install -r requirements.txt $ pip install . or $ python setup.py install
Usage
$ pubtools-sign --help $ pubtools-sign-clearsign --help $ pubtools-sign-containersign --help
Configuration
Configuration is done via a yaml file. The default location is ~/.config/.pubtools-sign/conf.yaml or /etc/pubtools-sign/conf.yaml. You can also specify a custom location via the –config argument. The configuration file is divided into sections, each section is a signer. Each signer has a set of attributes that are used to configure the signer Conf.yaml has following structure::
msg_signer: messaging_brokers: - <protocol://<host>:<port> for messaging broker messaging_cert_key: <path to messaging client key + certificate in PEM format> messaging_ca_cert: <path to CA certificate bundle> topic_send_to: topic://<topic> - topic where to send signing requests topic_listen_to: queue://<queue> - queue where to listen for answers from signing server. Supported templating variables: {creator - UID from client cert}, {task_id} environment: <env> - environment attribute which is included in signing request service: <service> - service attribute which is included in signing request timeout: <int> - timeout for signing request retries: <int> - number of retries for receiving signing responses from messaging brokers send_retries: <int> - number of retries for whole send + receive cycle message_id_key: <id> - attribute in message response used as unique identifier for signing request log_level: <level> - log level for pubtools-sign cosign_signer: rekor_url: <rekor-url> upload_tlog: <true|false> registry_user: <user> - used to login to registry where images will be signed registry_password: <password> env_variables: <key>: <val> - mapping of environment variables used in signing process. This can be used for example for AWS setup key_aliases: <alias>: <key> - mapping of key aliases to actual keys. When passing alias as signing key, <key> is used instead. This way you cna define for example "prod-key" alias and have different real keys for different signers
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file pubtools_sign-0.0.10.1.tar.gz
.
File metadata
- Download URL: pubtools_sign-0.0.10.1.tar.gz
- Upload date:
- Size: 45.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.12.7
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 154bd79fb5f5b2780cbde325f4c2589bc09cf6113b9e2ebc1a7ff142b0e918eb |
|
MD5 | 898e72ab1453c64844c0eb5b909ab2c1 |
|
BLAKE2b-256 | 36fd501c764b7db9fb06eaf8fb6c3f401d164545dbaef1afcb39df8e045c3a73 |
File details
Details for the file pubtools_sign-0.0.10.1-py3-none-any.whl
.
File metadata
- Download URL: pubtools_sign-0.0.10.1-py3-none-any.whl
- Upload date:
- Size: 32.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.12.7
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 701e941a2c888da287e3178d2b59b8cbd8e5608c0507f4d00252461f00472624 |
|
MD5 | 5f0cf2442987d5f5e01689242372fa61 |
|
BLAKE2b-256 | 23761457bbff7d6209d9eb77a5494cc3e4f1ca5d3ae3df1eb3eaf85f17e8d12b |