Date: Wed, 5 Sep 2018 03:15:33 +0200 From: Outback Dingo <outbackdingo@gmail.com> To: aimass@yabarana.com Cc: freebsd-questions@freebsd.org Subject: Re: Credentials/keychain/keystore for server applications on FreeBSD? Message-ID: <CAKYr3zzOPUy9eAhnT3mPKF0Py6Czd2CKk3iKnBR5ZeAfYMw8-Q@mail.gmail.com> In-Reply-To: <CAHieY7THk%2BwsbuSmYe8BoWN%2BzuQOqX%2BM-FGLhBqOvptdfYXspA@mail.gmail.com> References: <CAHieY7THk%2BwsbuSmYe8BoWN%2BzuQOqX%2BM-FGLhBqOvptdfYXspA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 5, 2018 at 2:53 AM Alejandro Imass <aimass@yabarana.com> wrote: > > Hi, > > Are there any tools that can store application credentials in encrypted > form and then provide them to applications in a secure manner at runtime = ? > > I=E2=80=99m looking for a generic tool that provides some sort of protoco= l with > timeouts etc. > > For example, a server application needs user and password for database > access and can query this tool for them on startup exactly one time. > > Maybe the tool could control the number of times it gives out the > credentials or timeout after a certain period (e.g. 2 minutes after reboo= t) > Then would require authentication to open up the vault again. > > There must be a better way of managing all the disparate credentials that > several applications may need in a secure way instead of storing these > credentials in clear text in some config file which is what most people > do.. maybe something like the JKS but generic to any type of app with som= e > relatively secure protocol. > > TIA for any pointers or ideas. hashicorps vault is in ports https://www.vaultproject.io/ > > Alex > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKYr3zzOPUy9eAhnT3mPKF0Py6Czd2CKk3iKnBR5ZeAfYMw8-Q>