From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vault: chown config dir to service user
Date: Mon, 25 Jan 2021 04:13:19 +0100 [thread overview]
Message-ID: <20210125031319.ydR9iU9A4gKeBtwHaO8lEpaL7Vp21-LEX76txOCySG0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28200@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/28200#issuecomment-766511811
Comment:
CLI seems to work okay:
```
$ ./xbps-src pkg vault && xi vault
<...>
vault-1.6.1_1: updating to 1.6.1_2 ...
<...>
$ sudo sv start vault
ok: run: vault: (pid 19733) 1s
$ vault --version
Vault v1.6.1 (6d2db3f033e02e70202bef9ec896360062b88b03) (cgo)
$ vault operator unseal
<...>
$ vault login
Token (will be hidden):
Success! You are now authenticated. The token information displayed below
is already stored in the token helper. You do NOT need to run "vault login"
again. Future Vault requests will automatically use this token.
<...>
$ vault secrets list | sed -E 's/_[a-z0-9]+/_<...>/'
Path Type Accessor Description
---- ---- -------- -----------
cubbyhole/ cubbyhole cubbyhole_<...> per-token private secret storage
identity/ identity identity_<...> identity store
secret/ kv kv_<...> n/a
sys/ system system_<...> system endpoints used for control, policy and debugging
```
next prev parent reply other threads:[~2021-01-25 3:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 21:38 [PR PATCH] " Goorzhel
2021-01-24 21:45 ` Goorzhel
2021-01-24 22:59 ` ericonr
2021-01-24 23:00 ` [PR PATCH] [Updated] " Goorzhel
2021-01-24 23:35 ` the-maldridge
2021-01-25 3:13 ` Goorzhel [this message]
2021-01-28 4:12 ` ericonr
2021-02-19 2:21 ` Goorzhel
2021-08-16 15:51 ` [PR PATCH] [Updated] " Goorzhel
2021-08-16 15:58 ` Goorzhel
2021-08-16 16:01 ` [PR PATCH] [Updated] " Goorzhel
2021-10-13 5:40 ` Goorzhel
2021-10-13 5:53 ` Goorzhel
2021-10-13 5:53 ` Goorzhel
2021-11-15 2:42 ` [PR PATCH] [Updated] " Goorzhel
2021-11-15 6:02 ` Goorzhel
2021-11-18 5:26 ` Goorzhel
2021-11-18 5:29 ` Goorzhel
2021-11-18 13:25 ` Duncaen
2021-11-19 1:53 ` Goorzhel
2021-11-19 2:49 ` the-maldridge
2021-11-19 3:38 ` [PR PATCH] [Updated] " Goorzhel
2021-11-19 11:10 ` Duncaen
2021-11-19 18:05 ` [PR PATCH] [Updated] " Goorzhel
2021-11-21 19:23 ` ericonr
2022-01-07 6:54 ` [PR PATCH] [Merged]: " the-maldridge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210125031319.ydR9iU9A4gKeBtwHaO8lEpaL7Vp21-LEX76txOCySG0@z \
--to=goorzhel@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).