Modified items

All recently modified items, latest first.

python3-pulp-maven-0.8.0-1.lbn36.noarch: pulp_maven Plugin This is the pulp_maven Plugin for Pulp Project 3.0+ < This plugin let's users use Pulp as a pull-through cache for Maven repositories.All REST API examples bellow use httpie < to perform the requests. The httpie commands below assume that the user executing the commands has a .netrc file in the home directory. The .netrc should have the following configuration:.. code-...

python3-pulp-maven-0.8.0-1.lbn36.noarch: pulp_maven Plugin This is the pulp_maven Plugin for Pulp Project 3.0+ < This plugin let's users use Pulp as a pull-through cache for Maven repositories.All REST API examples bellow use httpie < to perform the requests. The httpie commands below assume that the user executing the commands has a .netrc file in the home directory. The .netrc should have the following configuration:.. code-...

python3-pulp-file-client-3.50.0-1.lbn36.noarch: Fetch, Upload, Organize, and Distribute Software Packages # noqa: E501

python3-pulp-file-1.11.2-1.lbn36.noarch: pulp_file A Pulp plugin to support hosting arbitrary files.For more information, please see the documentation < or the Pulp project page <>_.

python3-pulp-deb-client-3.4.0-1.lbn36.noarch: Fetch, Upload, Organize, and Distribute Software Packages # noqa: E501

python3-pulp-deb-3.4.0-1.lbn36.noarch

python3-pulp-container-client-2.22.0-1.lbn36.noarch: No description provided (generated by Openapi Generator https:/github.com/openapitools/openapi-generator) # noqa: E501

python3-pulp-container-2.21.0-1.lbn36.noarch: pulp_container Plugin This is the pulp_container Plugin for Pulp Project 3.0+ < This plugin provides Pulp with support for container images, similar to the pulp_docker plugin for Pulp 2.For more information, please see the documentation < or the Pulp project page <>_.

python3-pulp-cli-0.29.2-1.lbn36.noarch: Pulp command line interface This is a command line interface for Pulp 3. This software is in beta and future releases may include backwards incompatible changes. Check out our docs and the quickstart guide to get started.

python3-pulp-certguard-client-3.50.0-1.lbn36.noarch: Fetch, Upload, Organize, and Distribute Software Packages # noqa: E501

python3-pulp-certguard-1.5.5-1.lbn36.noarch: This is the pulp_certguard Plugin for the Pulp Project 3.0+. This plugin provides X.509 certificate based content protection. The X509CertGuard authenticates the web request by validating the client certificate passed in the SSL_CLIENT_CERTIFICATE HTTP header using the CA (Certificate Authority) certificate that it has been configured with. All REST API examples bellow use httpie to perform the requests. The httpie commands below assume that the user executing the commands has a .netrc file in the home directory. The ~/.netrc should have the following configuration: machine localhost login admin password admin If you configured the admin user with a different password, adjust the configuration accordingly. If you prefer to specify the username and password with each request, please see httpie documentation on how to do that. This documentation makes use of the jq library to parse the json received from requests, in order to get the unique urls generated when objects are created. To follow this documentation as-is please install the jq library with: $ sudo dnf install jq Install pulpcore Follow the installation instructions provided with pulpcore. Users should install from either PyPI or source. Install pulp-certguard from source source ~/pulpvenv/bin/activate git clone https:/github.com/pulp/pulp-certguard.git cd pulp-certguard pip install -e . Install pulp-certguard From PyPI source ~/pulpvenv/bin/activate pip install pulp-certguard Make and Run Migrations django-admin makemigrations certguard django-admin migrate certguard Create a content guard named foo This example assumes that ~/ca.pem is a PEM encoded CA certificate. $ http --form POST http:/localhost:8000/pulp/api/v3/contentguards/certguard/x509/ name=foo ca_certificate@~/ca.pem { ... "_href": "/pulp/api/v3/contentguards/certguard/x509/3046291f-d432-4a85-9d7e-fad12b0aaed7/", ... } $ export GUARD_HREF=$(http localhost:8000/pulp/api/v3/contentguards/certguard/x509/?name=foo | jq -r '.results[0]._href') Create a distribution with content protection `` $ http POST http:/localhost:8000/pulp/api/v3/distributions/ name=bar base_path=files content_guard=${GUARD_HREF}`` { ... "_href": "/pulp/api/v3/distributions/305adfe0-4851-432f-9de3-13f9b10fe131/" ... } Add content protection to an existing distribution `` $ http PATCH http:/localhost:8000/pulp/api/v3/distributions/1/ content_guard=${GUARD_HREF}`` { ... "_href": "/pulp/api/v3/distributions/0fbb102a-cb38-4d5c-afc2-b9a76e862a1d/" ... } Download protected content The following examples assume there is a file named 1.iso published under the files distribution. Further, they assume there is a PEM encoded client certificate at ~/client.pem signed by the CA at ~/ca.pem. And, a PEM encoded private key at ~/key.pem. Example of GET directly to the content application running on port 8080 over HTTP. When setting the SSL-CLIENT-CERTIFICATE manually, the newlines need to be stripped due to restrictions on legal characters in HTTP header values. $ http localhost:8080/pulp/content/files/1.iso SSL-CLIENT-CERTIFICATE:"$(tr -d 'n' < ~/client.pem)" +-----------------------------------------+ | NOTE: binary data not shown in terminal | +-----------------------------------------+ Example of GET through a reverse proxy using HTTPS (like apache or nginx) in front of the content application. Its assumed that the reverse proxy has been configured to set the SSL-CLIENT-CERTIFICATE header using the client certificate exchanged as part of the SSL negotiation. $ http https:/localhost/pulp/content/files/1.iso --cert=~/client.pem --cert-key=~/key.pem --verify=no +-----------------------------------------+ | NOTE: binary data not shown in terminal | +-----------------------------------------+

python3-pulp-ansible-client-0.23.0-1.lbn36.noarch: Fetch, Upload, Organize, and Distribute Software Packages # noqa: E501

python3-pulp-ansible-0.23.0-1.lbn36.noarch: pulp_ansible A Pulp plugin to support hosting Role and Collection Ansible content.For more information, please see the documentation < Collection Support .. warning:: The 'Collection' content type is currently in tech-preview. Breaking changes could be introduced in the future.pulp_ansible can manage the multi-role repository content < installing.htmlmulti-role-repositories>_ referred to as a...

python3-transaction-3.0.1-5.fc36.noarch: This package contains a generic transaction implementation for Python. It is mainly used by the ZODB, though.

golang-github-terraform-provider-digitalocean-2.23.0-0.1.giteed72cc.lbn36.x86_64: Terraform digitalocean provider

golang-github-digitalocean-doctl-1.86.0-0.1.git076f589.lbn36.x86_64: The official command line interface for the DigitalOcean API

golang-github-cloudflare-cfssl_trust-2022.9.0-0.1.gitb72f316.lbn36.x86_64: This is the trust stores Cloudflare uses for CFSSL. It also includes the sources of the trust chain that can be built using the mkbundle utility from CFSSL. The ca-bundle.crt file contains the trusted roots. CFSSL uses the ca-bundle.crt.metadata when building bundles to assist in building bundles that need to verified in the maximum number of trust stores on different systems. The int-bundle.crt file contains a number of known intermediates; these are preloaded for performance reasons and occasionally updated as CFSSL finds more intermediates. If an intermediate isn't in this bundle, but can be found through following the AIA CA Issuers fields, it will be downloaded and eventually merged into here. The trusted_roots directory contains the root stores from a number of systems. Currently, we have trust stores from NSS (Firefox, Chrome) OS X Windows Android 2.2 (Frozen Yogurt) Android 2.3 (Gingerbread) Android 3.x (Honeycomb) Android 4.0 (Ice Cream Sandwich) Android 4.4 (KitKat)

golang-github-cloudflare-cfssl-1.6.4-0.2.gitb4d0d87.lbn36.x86_64: CFSSL is CloudFlare's PKI/TLS swiss army knife. It is both a command line tool and an HTTP API server for signing, verifying, and bundling TLS certificates. It requires Go 1.11+ to build. Note that certain linux distributions have certain algorithms removed (RHEL-based distributions in particular), so the golang from the official repositories will not work. Users of these distributions should install go manually to install CFSSL. CFSSL consists of: a set of packages useful for building custom TLS PKI tools the cfssl program, which is the canonical command line utility using the CFSSL packages. the multirootca program, which is a certificate authority server that can use multiple signing keys. the mkbundle program is used to build certificate pool bundles. the cfssljson program, which takes the JSON output from the cfssl and multirootca programs and writes certificates, keys, CSRs, and bundles to disk.

golang-github-aliyun-ossutil-1.7.9-4.fc36.x86_64: Alibaba Cloud (Aliyun) Object Storage Service (OSS) CLI.

golang-github-aliyun-cli-3.0.104-2.s20220118git031f9f2.fc36.x86_64: Alibaba Cloud (Aliyun) CLI.

« Previous 20 items Next 20 items » 1 ... 105 106 107 108 109 110 111 ... 2359


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items