[OE-core] [PATCH 0/2] Ensure a reasonable umask, and fix up permissions (V2)

[Koen Kooi]

Op 27 jun 2011, om 17:26 heeft Mark Hatle het volgende geschreven:

> 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.

Does this rely on the umask feature in bitbake master? If so, we should check the minumum bitbake requirements again