From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Root filesystem creation regression
Date: Mon, 22 Jun 2020 09:55:51 +0200 [thread overview]
Message-ID: <202006220955.51237.jbe@pengutronix.de> (raw)
Hi,
since commit 9c0ec1da583f32706372d2a6cefa9a05f77ee8d2
"ptxd_lib_check_dir_permissions: also check parents for directories"
the "install_tree" macro may create directories which makes this test fail and
I'm unable to create root filesystems anymore.
The problem pops up if "install_tree" tries to install a file to a directory
which has different permissions than the usual ones (0775, root:root).
For example: "systemd" sets up the "/usr/share/dbus-1/system-services" with
permissions 0755. If my own package tries to add another file to this directory
the corresponding "install" tool in the install stage creates the whole path
with standard 0755 permissions - because the "filesystem" in the package
directory (e.g. platform-<name>/packages/<package>) is always empty. In a
regular root filesystem it works, because the directory structure already
exists (with the intended permissions), and the "install" tool has to copy the
file only.
Using "install_tree" in my package in this case creates a conflict for
the "system-services" directory (0755 versus 0775). I guess it will fail at
more locations than only "install_tree", if someone adds more and more accurate
permissions due to security reasons.
jb
--
Pengutronix e.K. | Juergen Borleis |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-128 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2020-06-22 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 7:55 Juergen Borleis [this message]
2020-06-22 8:47 ` Michael Olbrich
2020-06-22 9:14 ` Juergen Borleis
2020-06-22 12:37 ` 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=202006220955.51237.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@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