From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: SSSD, Kerberized NFSv4 and Bacula
Date: Tue, 29 Aug 2023 17:57:21 +0200 [thread overview]
Message-ID: <c2c9a7a5-0ac7-472d-2a8d-b34c48e7fcb9@crazy-compilers.com> (raw)
In-Reply-To: <cMOFwRA9gmXBeBE-IOM7fgzXfwWTauak1FwsQEZxRqAoNhda8IMZB3CYmWCHhufALw4fWMu2fbR9YpnZ2jpME3Bh31yU7U-LY2gKxQ3Lq7Y=@baulig.is>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Hi,
Am 24.08.23 um 21:55 schrieb Martin Baulig:
>
> 1. My "guix secrets" tool provides a command-line interface to
> maintain a "secrets database" (/etc/guix/secrets.db) that's only
> accessible to root. It can contain simple passwords, arbitrary
> text (like for instance X509 certificates in PEM format) and
> binary data.
>
> 2. …
>
> 3. Finally, "secrets-service-type" depends on all of the above to do
> its work.
>
> It takes a /template file/ - which is typically interned in the
> store - containing special "tokens" that tell it which keys to
> look up from the /secrets database/.
>
This sounds great and like being a major step towards "guixops" [1], [2].
[1]
https://lists.gnu.org/archive/html/guix-devel/2019-07/msg00435.html[2]
https://lists.gnu.org/archive/html/guix-devel/2017-09/msg00196.html
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2119 bytes --]
next prev parent reply other threads:[~2023-08-29 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:55 SSSD, Kerberized NFSv4 and Bacula Martin Baulig
2023-08-25 21:43 ` SSSD, Kerberized NFSv4 and Bacula OFF TOPIC PRAISE jbranso
2023-08-29 15:57 ` Hartmut Goebel [this message]
2023-08-30 9:37 ` SSSD, Kerberized NFSv4 and Bacula Andreas Enge
2023-08-30 12:41 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
-- strict thread matches above, loose matches on Subject: below --
2023-08-25 10:07 Nathan Dehnel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2c9a7a5-0ac7-472d-2a8d-b34c48e7fcb9@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).