From: Michael Olbrich <mol@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: ref_make_macros: make clear that permission should be four digits
Date: Fri, 04 Sep 2020 19:01:29 +0200 [thread overview]
Message-ID: <E1kEF5d-0005Zd-5m@dude02.hi.pengutronix.de> (raw)
In-Reply-To: <20200819105909.21441-1-rhi@pengutronix.de>
Thanks, applied as 455015358553bade699536203a16da6a87a67fdf.
Michael
[sent from post-receive hook]
On Fri, 04 Sep 2020 19:01:29 +0200, Roland Hieber <rhi@pengutronix.de> wrote:
> Three octal digits are not enough, we must also respect the
> sticky/setuid/setgid bits. Even if these are mostly implied to be 0, we
> should be explicit here. This should also help to prevent permission
> clashes when more than one packages install the same directory.
>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Acked-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20200819105909.21441-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/ref_make_macros.rst b/doc/ref_make_macros.rst
> index 6f056adf3e7d..ae65cb9408cf 100644
> --- a/doc/ref_make_macros.rst
> +++ b/doc/ref_make_macros.rst
> @@ -173,7 +173,7 @@ Some of the parameters have fixed meanings:
> **<GID>**
> Group ID the file should use in the target's root filesystem
> **<permission>**
> - Permission (in an octal value) the file should use in the target's root filesystem
> + Permission (as a four-digit octal value) the file should use in the target's root filesystem
>
> The remaining parameters vary with the use case:
>
> @@ -384,7 +384,7 @@ The base parameters and their meanings:
> **<GID>**
> Group ID the file should use in the target's root filesystem
> **<permission>**
> - Permission (in an octal value) the file should use in the target's root filesystem
> + Permission (as a four-digit octal value) the file should use in the target's root filesystem
>
> The parameter <destination> is meant as an absolute path
> and filename in target's root filesystem. PTXdist searches for the source
> @@ -581,7 +581,7 @@ The parameters and their meanings:
> **<GID>**
> Group ID the directories and files should use in the target's root filesystem
> **<permission>**
> - Permission (as an octal value) the library should use in the target's root
> + Permission (as a four-digit octal value) the library should use in the target's root
> filesystem (mostly 0644)
> **<libname>**
> Basename of the library without any extension and path
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-09-04 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 10:35 [ptxdist] [PATCH] sudo: targetinstall /etc/sudoers.d with 4 digit permission Alexander Dahl
2020-08-19 10:47 ` Roland Hieber
2020-08-19 10:51 ` [ptxdist] [PATCH 1/2] doc: ref_make_macros: make clear that permission should be four digits Roland Hieber
2020-08-19 10:51 ` [ptxdist] [PATCH 2/2] rules: explicitly specify sticky/setuid/setgid bits for install_* macros Roland Hieber
2020-08-19 10:55 ` Roland Hieber
2020-08-19 10:59 ` [ptxdist] [PATCH v2 1/2] doc: ref_make_macros: make clear that permission should be four digits Roland Hieber
2020-08-19 10:59 ` [ptxdist] [PATCH v2 2/2] rules: explicitly specify sticky/setuid/setgid bits for install_* macros Roland Hieber
2020-09-04 17:01 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-19 11:04 ` [ptxdist] [PATCH v2 1/2] doc: ref_make_macros: make clear that permission should be four digits Alexander Dahl
2020-08-21 7:52 ` Michael Olbrich
2020-08-21 12:06 ` Alexander Dahl
2020-08-23 19:17 ` Roland Hieber
2020-09-04 17:01 ` Michael Olbrich [this message]
2020-08-19 11:11 ` [ptxdist] [PATCH] sudo: targetinstall /etc/sudoers.d with 4 digit permission Alexander Dahl
2020-08-19 11:29 ` Roland Hieber
2020-08-21 6:54 ` [ptxdist] [APPLIED] " Michael Olbrich
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=E1kEF5d-0005Zd-5m@dude02.hi.pengutronix.de \
--to=mol@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/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