Importer needs to support additional configuration properties
The importer needs to support the following additional configuration properties:
- KEY_SSL_CA_CERT = 'ssl_ca_cert'
- KEY_SSL_VALIDATION = 'ssl_validation'
- KEY_SSL_CLIENT_CERT = 'ssl_client_cert'
- KEY_SSL_CLIENT_KEY = 'ssl_client_key'
- KEY_GPG = 'gpg_key'
Values are set in the remote options on remote-add.
(see: man ostree.repo-config):
tls-client-cert-path = KEY_SSL_CLIENT_CERT Path to file for client-side certificate, to present when making requests to this repository. tls-client-key-path = KEY_SSL_CLIENT_KEY Path to file containing client-side certificate key, to present when making requests to this repository. tls-ca-path = KEY_SSL_CA_CERT Path to file containing trusted anchors instead of the system CA database. tls-permissive = (not KEY_SSL_VALIDATION) A boolean value, defaults to false. By default, server TLS certificates will be checked against the system certificate store. If this variable is set, any certificate will be accepted. gpg-verify = (KEY_GPG is not None) A boolean value, defaults to true. Controls whether or not OSTree will require commits to be signed by a known GPG key. For more information, see the ostree(1) manual under GPG.
The GPG key will need to be stored as keyring files in /usr/share/ostree/trusted.gpg.d
When a GPG key is specifed, gpg-verify=1 must be specified in the remote options.
- Pulp stores the GPG keys in the DB.
- Find out if libostree can be handed the keys directly. If not, let's see if libostree can be changed to support a different file location.
#9 Updated by email@example.com about 5 years ago
We also need to support:
# Hostname or IP of the proxy server KEY_PROXY_HOST = 'proxy_host' # Port used to contact the proxy server KEY_PROXY_PORT = 'proxy_port' # Username for an authenticated proxy server KEY_PROXY_USER = 'proxy_username' # Password for an authenticated proxy server KEY_PROXY_PASS = 'proxy_password'
Mapped to a remote configuration:
proxy A string value, if given should be a URL for a HTTP proxy to use for access to this repository.
#10 Updated by firstname.lastname@example.org about 5 years ago
The atomic project has just merged this PR: https://github.com/GNOME/ostree/pull/107 which supports managing GPG keyrings for each remote and is stored in the ostree repository directory.
The PR is the resolution to: https://bugzilla.gnome.org/show_bug.cgi?id=729592.
Not sure when it will land in a packaged release.
#13 Updated by email@example.com about 5 years ago
PR https://github.com/GNOME/ostree/pull/115 accepted and merged upstream.
Troubleshooting an issue with the ostree team. I don't think that ostree should still be looking in /usr/share/ostree/trusted.gpg.d for keyrings when there is a remote specific keyring defined. The directory not-found is also an issue.
$ sudo -u apache ostree --repo=content remote gpg-import jeff -k /tmp/j.asc Imported 1 GPG key to remote "jeff" $ sudo -u apache ostree --repo=content pull jeff rhel-atomic-host/7/x86_64/standard error: Reading keyring directory '/usr/share/ostree/trusted.gpg.d' No such file or directory
#15 Updated by firstname.lastname@example.org about 5 years ago
Issues signing a commit:
$ sudo rpm-ostree compose sign --key=30170657 --rev=rhel-atomic-host/7/x86_64/standard --repo=. error: Failed to execute child process "rpm-sign" (No such file or directory)
Please register to edit this issue