From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Ensure a reasonable umask, and fix up permissions (V2)
Date: Mon, 27 Jun 2011 10:26:55 -0500 [thread overview]
Message-ID: <cover.1309188064.git.mark.hatle@windriver.com> (raw)
Revised the fixup_perms function in package.bbclass. Change to using a
class based approach for the individual permissions entries.
Add support for directory linkages.
Add entries to match base-files recipe in the fs-perms.txt.
(umask commit is unchanged, resending due to time since last sent)
----
V1 log below
Add a new function that is responsible for fixing directory and file
permissions, owners and groups during the packaging process. This will fix
various issues where two packages may create the same directory and end up
with different permissions, owner and/or group.
The issue being resolved is that if two packages conflict in their ownership
of a directory, the first installed into the rootfs sets the permissions.
This leads to a least potentially non-deterministic filesystems, at worst
security defects.
The user can specify their own settings via the configuration files
specified in FILESYSTEM_PERMS_TABLES. If this is not defined, it will
fall back to loading files/fs-perms.txt from BBPATH. The format of this
file is documented within the file.
By default all of the system directories, specified in bitbake.conf, will
be fixed to be 0755, root, root.
The fs-perms.txt contains a few default entries to correct documentation,
locale, headers and debug sources. It was discovered these are often
incorrect due to being directly copied from the build user environment.
Also tweak a couple of warnings to provide more diagnostic information.
The following changes since commit 0009fa951d45c742963279b0d9740c1209b46456:
linux-firmware: Fix file permissions (2011-06-24 13:32:21 -0500)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib mhatle/perms
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/perms
Mark Hatle (3):
Add umask task control
classes/package.bbclass: Add fixup_perms
meta/classes/base.bbclass | 4 +
meta/classes/image.bbclass | 2 +
meta/classes/package.bbclass | 253 +++++++++++++++++++-
meta/classes/staging.bbclass | 1 +
meta/files/fs-perms.txt | 69 ++++++
.../installer/adt-installer_1.0.bb | 2 +
meta/recipes-kernel/linux/linux-tools.inc | 2 +
7 files changed, 346 insertions(+), 14 deletions(-)
create mode 100644 meta/files/fs-perms.txt
--
1.7.3.4
next reply other threads:[~2011-06-27 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 15:26 Mark Hatle [this message]
2011-06-27 15:26 ` [PATCH 1/2] Add umask task control Mark Hatle
2011-06-27 15:26 ` [PATCH 2/2] classes/package.bbclass: Add fixup_perms (V2) Mark Hatle
2011-06-27 15:31 ` [PATCH 0/2] Ensure a reasonable umask, and fix up permissions (V2) Koen Kooi
2011-06-27 15:34 ` Mark Hatle
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=cover.1309188064.git.mark.hatle@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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