Package - postgresql-17-vault
Primary informations
Download package: https://repo.pigsty.io/apt/pgsql/trixie/pool/main/v/vault/postgresql-17-vault_0.3.1-1PIGSTY~trixie_amd64.deb (Size: 29.8KiB)| Property | Value |
|---|---|
| Package | postgresql-17-vault |
| Source | vault |
| Version | 0.3.1-1PIGSTY~trixie |
| Architecture | amd64 |
| Maintainer | Ruohang Feng |
| Installed-Size | 96 |
| Depends | postgresql-17, libc6 (>= 2.4), libsodium23 (>= 1.0.12), postgresql-17-pgsodium |
| Provides | postgresql-vault |
| Homepage | https://github.com/supabase/vault |
| Priority | optional |
| Section | database |
| Filename | pool/main/v/vault/postgresql-17-vault_0.3.1-1PIGSTY~trixie_amd64.deb |
| Size | 30468 |
| SHA256 | 60a3a70a1f9c648cf3294173150da36cc9faa5e1ab32a36f86f2b370606bee61 |
| SHA1 | cde5b9e21b8414f23ecfb910c2a99bdbefac915f |
| MD5sum | 54871e9051fbbafa79763c7d2d5f304d |
| Description | Extension for storing encrypted secrets in the Vault in PostgreSQL 17 Supabase provides a table called vault.secrets that can be used to store sensitive information like API keys. These secrets will be stored in an encrypted format on disk and in any database dumps. This is often called Encryption At Rest. Decrypting this table is done through a special database view called vault.decrypted_secrets that uses an encryption key that is itself not avaiable to SQL, but can be referred to by ID. Supabase manages these internal keys for you, so you can't leak them out of the database, you can only refer to them by their ids. |
| Description-md5 |