PK
05O( _rels/.rels ( PK 05O_ٸ] B vault.nuspec ( Xks6ޙ6_qQqɮz-'3LX Eٶ8sǦf:e鳟nrqWv?>oO܉J6e8SL&k^ӽ|2םk]5{pj?q%l?۟mz땯coX7<5{]$^~YeحH;aa禮v<-Hk%vą+ncU2Q^,HF[k~,H2eY>Z(,_S +ɫ\TF{MAuq]XayP 2Y0IOB7aJ2 Qc
w6@ߍ)m %5oR̔=eqɝd/
Q#м&)(ͮ
)b8u¤!ueB̆)h dxS[ɋ
+T0Q=CKe!W$\P~YM5AGMk hhÑLt0gm¦u%a>qhP1d@SJN8B\ʭ
rIc5*^F5`\Ky>(0y^JxMD!U1 ]U7KVY*-{Dx-ZdAֆKC&TG@x*hZic S+S1
W`' zk^mKYI s`3 8#'!řKXCom;;*1S_Ek=(\|ı؍mCgumk3-;g{B`VP^5I=($c:[b`}g
`V<-oZt[?]Ϩ_24B?$sO
A"(+M
vCէAGdH.vGLщ(G?~_a^IrPGY><度A?gYƺYg
ݐMo_^,%̝<
r+4By][TTf-πⰷ(%Mh=!jRTZ/c<k#\*[{-$LzP!h SɃȊww?m]İ&{BԵ4 aՔwP!+ʎtآ+X(-NG|o~x┍by
7Eho%jTL57{[?dE?D|`iqҗg/mk]_JmiZErKo,I_"O_ᱼPpZ41oev|1٩$;[8@ J&Ahfє4SԖnQï
IUuj8LXq$WJF
}4u%Wή ɧ>XH^71+.Hu*)P4+TMV?<~$Uˬ)g8*: n,}/͇y*=GTfu[_/fT?ꇯXCchDf[wb#ܟ6@k
Ugy)ـn-KxÏ8WPK 05Ohj tools/chocolateyInstall.ps1 ( J1Cl6ԋ"/eL&Vd|$_V];7
`[OxDF;
WܗaJz Y%G4]}E
;_4FYCQ/S%Ǣtic Oh-0iցDgze*m|q+ *+wEWM,dfQV:"e
T$V[6q\$U"3Äs+2d}nqs`E#D&Cfy"@)RZTQiRя@M*5m*?lr,fBƣh<:}.4%\PK
05Oj Q package/services/metadata/core-properties/b4f38318588d43eab112523b85f4bb27.psmdcp ( Mitchell Hashimoto, HashiCorpVault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.
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 Vault steps in.
The key features of Vault are:
* **Secure Secret Storage**: Arbitrary key/value secrets can be stored in Vault. Vault encrypts these secrets prior to writing them to persistent storage, so gaining access to the raw storage isn't enough to access your secrets. Vault can write to disk, [Consul](https://www.consul.io), and more.
* **Dynamic Secrets**: Vault 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 Vault for credentials, and Vault will generate an AWS keypair with valid permissions on demand. After creating these dynamic secrets, Vault will also automatically revoke them after the lease is up.
* **Data Encryption**: Vault 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 SQL without having to design their own encryption methods.
* **Leasing and Renewal**: All secrets in Vault have a _lease_ associated with it. At the end of the lease, Vault will automatically revoke that secret. Clients are able to renew leases via built-in renew APIs.
* **Revocation**: Vault has built-in support for secret revocation. Vault 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.
For more information, see the [introduction section](https://www.vaultproject.io/intro) of the Vault website.vault1.2.2vault hashicorpVaultchoco, Version=0.10.15.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb;Microsoft Windows NT 10.0.18362.0;.NET Framework 4PK
05OUd, [Content_Types].xml ( PK-
05O( _rels/.relsPK- 05O_ٸ] B / vault.nuspecPK- 05Ohj
tools/chocolateyInstall.ps1PK-
05Oj Q package/services/metadata/core-properties/b4f38318588d43eab112523b85f4bb27.psmdcpPK-
05OUd, [Content_Types].xmlPK |