From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] sudo: targetinstall /etc/sudoers.d with 4 digit permission
Date: Wed, 19 Aug 2020 13:11:35 +0200 [thread overview]
Message-ID: <319569693.M9ZyiqoN1p@ada> (raw)
In-Reply-To: <20200819104722.xqfrbwgg6mghrpk7@pengutronix.de>
Hello Roland,
Am Mittwoch, 19. August 2020, 12:47:22 CEST schrieb Roland Hieber:
> On Tue, Aug 18, 2020 at 12:35:32PM +0200, Alexander Dahl wrote:
> > When installing additional files into /etc/sudoers.d from another
> >
> > package, we got this error (redacted):
> > Incompatible ownership or permissions for '/etc/sudoers.d':
> > sudo: 0.0 755
> > *****: 0.0 0755 (implicit)
> >
> > One of these packages must be fixed!
> >
> > Build is successful again, if fixed in the sudo package.
> >
> > Signed-off-by: Alexander Dahl <ada@thorsis.com>
> > ---
> >
> > Notes:
> > Besides: how would one fix this in the other package? I have that case
> > for another set of packages where one creates a folder with 2775 and
> > others should copy files in it, which fails because 0755 are the
> > implicit rights. Recreate that folder in each package?
>
> A start could be to grep for install_copy calls and sort them by their
> last parameter:
>
> git grep '$(call install_copy,' | sort -k 8
>
> … but we still need to handle those lines which are wrapped using a \ at
> the end…
I think you misunderstood what I meant. Let me give an example. Assume package
'foo' creates a folder like this:
@$(call install_copy, foo, root, daemon, 2775, /etc/daemon)
And now another package 'bar' installs a file like this:
@$(call install_alternative, bar, root, root, 0644, /etc/daemon/bar)
This will clash with an error message (roughly) like this:
Incompatible ownership or permissions for '/etc/daemon':
foo: 0.1 2775
bar: 0.0 0755 (implicit)
One of these packages must be fixed!
Now the question again: how would one fix this in package 'bar' without
touching package 'foo'?
Greets
Alex
_______________________________________________
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-08-19 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 10:35 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 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-08-19 11:11 ` Alexander Dahl [this message]
2020-08-19 11:29 ` [ptxdist] [PATCH] sudo: targetinstall /etc/sudoers.d with 4 digit permission 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=319569693.M9ZyiqoN1p@ada \
--to=ada@thorsis.com \
--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