| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help |
The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...
The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.
OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys. The OpenBao community intends to provide this software under an OSI-approved open-source license, led by a community run under open governance principles. A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where OpenBao steps in. The key features of OpenBao are: * Secure Secret Storage: Arbitrary key/value secrets can be stored in OpenBao. OpenBao encrypts these secrets prior to writing them to persistent storage, so gaining access to the raw storage isn't enough to access your secrets. OpenBao can write to disk, Consul, and more. * Dynamic Secrets: OpenBao can generate secrets on-demand for some systems, such as AWS or SQL databases. For example, when an application needs to access an S3 bucket, it asks OpenBao for credentials, and OpenBao will generate an AWS keypair with valid permissions on demand. After creating these dynamic secrets, OpenBao will also automatically revoke them after the lease is up. * Data Encryption: OpenBao can encrypt and decrypt data without storing it. This allows security teams to define encryption parameters and developers to store encrypted data in a location such as a SQL database without having to design their own encryption methods. * Leasing and Renewal: All secrets in OpenBao have a lease associated with them. At the end of the lease, OpenBao will automatically revoke that secret. Clients are able to renew leases via built-in renew APIs. * Revocation: OpenBao has built-in support for secret revocation. OpenBao can revoke not only single secrets, but a tree of secrets, for example, all secrets read by a specific user, or all secrets of a particular type. Revocation assists in key rolling as well as locking down systems in the case of an intrusion.
| Package | Summary | Distribution | Download |
| openbao-2.0.2-1.1.aarch64.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for aarch64 | openbao-2.0.2-1.1.aarch64.rpm |
| openbao-2.0.2-1.1.armv6hl.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for armv6hl | openbao-2.0.2-1.1.armv6hl.rpm |
| openbao-2.0.2-1.1.armv7hl.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for armv7hl | openbao-2.0.2-1.1.armv7hl.rpm |
| openbao-2.0.2-1.1.i586.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for i586 | openbao-2.0.2-1.1.i586.rpm |
| openbao-2.0.2-1.1.riscv64.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for riscv64 | openbao-2.0.2-1.1.riscv64.rpm |
| openbao-2.0.2-1.1.s390x.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for s390x | openbao-2.0.2-1.1.s390x.rpm |
| openbao-2.0.2-1.1.x86_64.html | Manage, store, and distribute sensitive data | OpenSuSE Tumbleweed for x86_64 | openbao-2.0.2-1.1.x86_64.rpm |
| openbao-2.0.1-1.1.ppc64le.html | Manage, store, and distribute sensitive data | OpenSuSE Ports Tumbleweed for ppc64le | openbao-2.0.1-1.1.ppc64le.rpm |
Generated by rpm2html 1.6