Synchronize secrets between HashiCorp Vault instances
A poor man's tool to replicate secrets from one Vault instance to another.
How it works
When vault-sync starts, it does a full copy of the secrets from the source
Vault instance to the destination Vault instance. Periodically, vault-sync does
a full reconciliation to make sure all the destination secrets are up to date.
At the same time, you can manually enable the Socket Audit Device for the
source Vault, so Vault will be sending audit logs to vault-sync. Using these
audit logs, vault-sync keeps the secrets in the destination Vault up to date.
Note that vault-sync does not create or delete the audit devices by itself.
It is possible to use the same Vault instance as the source and the
destination. You can use this feature to replicate a "folder" of secrets to
another "folder" on the same server. You need to specify different prefixes
(src.prefix and dst.prefix) in the configuration file to make sure the source
and the destination do not overlap.
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
OpenFactory puede arrancar este sistema operativo en una máquina virtual del navegador, o iniciar una construcción que incluye el nombre nativo del paquete de este registro.
Cada fila es metadato del índice de paquetes para una versión, arquitectura, suite y repositorio. Nombres, URL y tamaños vienen de la fuente; un enlace es un punto de descarga que puede cambiar, no una redistribución de OpenFactory.
Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.
0.9.2-bp160.1.14 / aarch64Observado Sep 1, 2026sha512 a0ca41896f45…5c396b16Resumen de la fuente
Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.
Resumen de la fuente (sha512): a0ca41896f458f05bd049d2c382ce010621d35706244845345e94ff267ac1eb091a0f7a8cd20e31742451679d932db13565057385ad578975d0fa3735c396b16
0.9.2-bp160.1.14 / ppc64leObservado Sep 1, 2026sha512 eddf25f37155…a0cb12e8Resumen de la fuente
Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.
Resumen de la fuente (sha512): eddf25f37155044072c49d0f0dbd474869082468418429ac33dd618bf93e9d6ed5c1d898e1853a84de416babaebee0f1894793f2c721ce28038fa273a0cb12e8
0.9.2-bp160.1.14 / s390xObservado Sep 1, 2026sha512 c195dedbe1fb…8c13c0c8Resumen de la fuente
Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.
Resumen de la fuente (sha512): c195dedbe1fbe43192ab77016469c5b3e8a9c230430e97c0f1e33cb60a6209b46caf2e95fb16ad7d9fe5f141ee3c3cf6af123e0b2eefaeb9d4942f5b8c13c0c8
0.9.2-bp160.1.14 / x86_64Observado Sep 1, 2026sha512 cb68e80a87cc…c8cb64ebResumen de la fuente
Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.
Resumen de la fuente (sha512): cb68e80a87cc56b7012b35874746009d6d092ce72bd7fe69731ce03fc7edd9c8b4becb188fa6f516e1c90f494a1833fd26ceb9cbadbadbf433e8c02bc8cb64eb