Github messages for voidlinux
 help / color / mirror / Atom feed
From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] vault: chown config dir to service user
Date: Mon, 16 Aug 2021 18:01:48 +0200	[thread overview]
Message-ID: <20210816160148.t-q8Ri7Yz_DCMxXjn0e_X9z0K2FZ0RA5rVEvKpos834@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: 646 bytes --]

There is an updated pull request by Goorzhel against master on the void-packages repository

https://github.com/Goorzhel/void-packages vault
https://github.com/void-linux/void-packages/pull/28200

vault: chown config dir to service user
Dunno why I missed this before, but:
```
$ sudo -u _vault vault server -config=/etc/vault
Password:
error loading configuration from /etc/vault: open /etc/vault: permission denied
$ sudo chown _vault:_vault /etc/vault
$ sudo -u _vault vault server -config=/etc/vault
==> Vault server configuration:
<...>
```

A patch file from https://github.com/void-linux/void-packages/pull/28200.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vault-28200.patch --]
[-- Type: text/x-diff, Size: 1031 bytes --]

From e9ccf90a354a2c275fd6d506a41af3a77cbf800a Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Mon, 16 Aug 2021 09:01:42 -0700
Subject: [PATCH] vault: chown config dir to service user

---
 srcpkgs/vault/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/vault/template b/srcpkgs/vault/template
index a0d4649a461f..5e7625c3e4d3 100644
--- a/srcpkgs/vault/template
+++ b/srcpkgs/vault/template
@@ -1,7 +1,7 @@
 # Template file for 'vault'
 pkgname=vault
 version=1.8.1
-revision=1
+revision=2
 build_style=go
 go_import_path="github.com/hashicorp/vault"
 go_build_tags="release"
@@ -16,7 +16,7 @@ distfiles="https://github.com/hashicorp/vault/archive/v${version}.tar.gz"
 checksum=dbf389458fddeb5f8c567d00b6d17ce054f5b7667c226dbb598aa2c0f9048004
 system_accounts="_vault"
 make_dirs="/var/lib/vault 0700 _vault _vault
- /etc/vault 0700 root root"
+ /etc/vault 0700 _vault _vault"
 
 case "$XBPS_TARGET_MACHINE" in
 	arm*) go_ldflags="$go_ldflags -linkmode=external";;

  parent reply	other threads:[~2021-08-16 16:01 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
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 ` Goorzhel [this message]
2021-10-13  5:40 ` [PR PATCH] [Updated] " 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=20210816160148.t-q8Ri7Yz_DCMxXjn0e_X9z0K2FZ0RA5rVEvKpos834@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).