Modified items

All recently modified items, latest first.

python3-perf-5.14.0-0.rc4.git0.1.lbn25.x86_64: A Python module that permits applications written in the Python programming language to use the interface to manipulate perf events.

rubygem-tomlrb-1.3.0-1.lbn25.noarch: A racc based toml parser.

rubygem-sfl-2.3-1.lbn25.noarch: Spawn for Ruby 1.8

rubygem-public_suffix-4.0.6-1.lbn25.noarch: PublicSuffix can parse and decompose a domain name into top level domain, domain and subdomains.

rubygem-pg-1.2.3-1.lbn25.x86_64: This is the extension library to access a PostgreSQL database from Ruby. This library works with PostgreSQL 9.1 and later.

rubygem-openssl-2.1.2-132.lbn25.x86_64: OpenSSL provides SSL, TLS and general purpose cryptography. It wraps the OpenSSL library.

rubygem-net-telnet-0.2.0-132.lbn25.noarch: Provides telnet client functionality. This class also has, through delegation, all the methods of a socket object (by default, a TCPSocket, but can be set by the Proxy option to new()). This provides methods such as close() to end the session and sysread() to read data directly from the host, instead of via the waitfor() mechanism. Note that if you do use sysread() directly when in telnet mode, you should probably pass the output through preprocess() to extract telnet command sequences.

rubygem-iso8601-0.13.0-1.lbn25.noarch: ISO8601 is a simple implementation in Ruby of the ISO 8601 (Data elements and interchange formats - Information interchange - Representation of dates and times) standard.

ruby-ldap-0.9.16-20.lbn25.x86_64: Ruby/LDAP is an extension library for Ruby. It provides the interface to some LDAP libraries (e.g. OpenLDAP, UMich LDAP, Netscape SDK, ActiveDirectory). The common API for application development is described in RFC1823 and is supported by Ruby/LDAP.

squid-4.13-1.lbn25.x86_64: Squid is a high-performance proxy caching server for Web clients, supporting FTP, gopher, and HTTP data objects. Unlike traditional caching software, Squid handles all requests in a single, non-blocking, I/O-driven process. Squid keeps meta data and especially hot objects cached in RAM, caches DNS lookups, supports non-blocking DNS lookups, and implements negative caching of failed requests. Squid consists of a main server program squid, a Domain Name System lookup program (dnsserver), a program for retrieving FTP data (ftpget), and some management and client tools.

rubygem-multipart-post-2.0.0-13.lbn25.noarch: Use with Net::HTTP to do multipart form posts. IO values that have #content_type, #original_filename, and #local_path will be posted as a binary file.

rubygem-aws-eventstream-1.2.0-1.lbn25.noarch: Amazon Web Services event stream library. Decodes and encodes binary stream under `vnd.amazon.event-stream` content-type.

rubygem-hitimes-1.3.1-1.lbn25.x86_64: Hitimes is a fast, high resolution timer library for recording performance metrics. It uses the appropriate low method calls for each system to get the highest granularity time increments possible. It currently supports any of the following systems: * any system with the POSIX call `clock_gettime()` * Mac OS X * Windows * JRuby Using Hitimes can be faster than using a series of `Time.new` calls, and it will have a much higher granularity. It is definitely faster than using `Process.times`.

systemd-rpm-macros-249.4-2.lbn25.noarch: Just the definitions of rpm macros. See https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_systemd for information how to use those macros.

python3-pyrsistent-0.15.7-1.lbn25.x86_64: Pyrsistent is a number of persistent collections (by some referred to as functional data structures). Persistent in the sense that they are immutable. All methods on a data structure that would normally mutate it instead return a new copy of the structure containing the requested updates. The original structure is left untouched.

summon-vault4summon-0.4-0.1.gitcd31ff2.lbn25.x86_64: Providers for Summon are easy to write. Given the identifier of a secret, they either return its value or an error. There is the contract: They take one and only one argument, the identifier of a secret (a string). The argument can also be a flag with value -v or --version. The provider must return his version on stdout. If retrieval is successful, they return the value on stdout with exit code 0. If an error occurs, they return an error message on stderr with a non-0 exit code. The default path for providers is /usr/local/lib/summon/. If one provider is in that path, summon will use it. If multiple providers are in the path, you can specify which one to use with the --provider flag, or the environment variable SUMMON_PROVIDER. If your providers are placed outside the default path, give summon the full path to them. Variable IDs are used as identifiers for fetching Secrets. These are made up of a secret name (required) and secret key path (optional). The Vault CLI to retrieve a secret is vault kv get -field=mysecretkeypath secret/name This provider are 2 implemented formats for Variable ID: secret/name#mysecretkeypath as used by AWS Secrets Manager provider secret/name/mysecretkeypath as used by Keepass kdbx database file provider So the two commands below return the same value summon --provider vault4summon --yaml 'hello: !var secret/name#mysecretkeypath' printenv hello summon --provider vault4summon --yaml 'hello: !var secret/name/mysecretkeypath' printenv hello

summon-s3-0.2.0-0.2.git42b6d99.lbn25.x86_64: AWS S3 provider for Summon. Provides access to secrets stored in Amazon S3.

summon-keyring-0.2.1-2.lbn25.noarch: Cross-platform provider for Summon that talks to keyrings. Wraps the Python keyring library to allow summon to fetch credentials from: OSX Keychain Linux Secret Service Windows Credential Vault gnome-keyring kwallet This provider requires that you have Python and pip installed. By default, this provider fetches secrets from the service "summon". Change this by setting the SUMMON_KEYRING_SERVICE environment variable.

summon-conjur-0.6.0-0.1.gitf48c46b.lbn25.x86_64: CyberArk Conjur provider for Summon

summon-chefapi-0.1.1-0.2.git88fdef1.lbn25.x86_64: For many, Chef encrypted data bags are difficult to work with. This Summon provider allows you to use Summon + secrets.yml to improve your development workflow with encrypted data bags. Example Create an encrypted data bag with a PostgreSQL password. $ knife data bag create passwords postgres --secret-file encrypted_data_bag_secret { "id": "postgres", "value": "mysecretpassword" } Install Summon and this provider. Create a secrets.yml file. POSTGRES_PASSWORD: !var passwords/postgres/value Now you can inject the password into any process as an environment variable. Instead of dealing with the Data Bag API in your Chef recipe, you can just use ENV['POSTGRES_PASSWORD']. $ summon chef-client --once Once chef-client finishes, the password is gone, not left on your system. Configure Configuration of this provider is through environment variables: CHEF_NODE_NAME: The name of the node. (node_name in knife.rb) CHEF_CLIENT_KEY_PATH: The location of the file that contains the client key. (client_key in knife.rb) CHEF_SERVER_URL: The URL for the Chef server. (chef_server_url in knife.rb) CHEF_DECRYPTION_KEY_PATH: The location of the file that contains the decryption key. CHEF_SKIP_SSL: Skip SSL verification (for self-signed certs). Set to "1" to activate.

« Previous 20 items Next 20 items » 1 ... 817 818 819 820 821 822 823 ... 2437


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

Sections

Modified items