linux/poky.git/meta/recipes-devtools/pseudo/files/pseudo-fchmodat-permissions.patch, branch hardknott

pseudo: remove older version and patches

2014-12-03T12:23:58+00:00

(From OE-Core rev: 73f418ce10a801f0befc06ffe54864563aea986c) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

pseudo: Honor umask again

2014-05-28T07:19:31+00:00

The fchmodat-permissions patch was fine for the fchmod case, but had the unintended side effect of disregarding umask settings for open, mknod, mkdir, and their close relatives. Start tracking umask and masking the umask bits out where appropriate. (From OE-Core rev: ce23c1cc33a015fbd184df6c16658353334ab611) Signed-off-by: Peter Seebach Signed-off-by: Richard Purdie

pseudo: handle fchmodat better, mask out unwanted write bits

2014-05-27T15:11:53+00:00

It turns out that pseudo's decision not to report errors from the host system's fchmodat() can break GNU tar in a very strange way, resulting in directories being mode 0700 instead of whatever they should have been. Additionally, it turns out that if you make directories in your rootfs mode 777, that results in the local copies being mode 777, which could allow a hypothetical attacker with access to the machine to add files to your rootfs image. We should mask out the 022 bits when making actual mode changes in the rootfs. This patch represents a backport to the 1.5.1 branch of three patches from the 1.6 branch, because it took a couple of tries to get this quite right. (From OE-Core rev: 45371858129bbad8f4cfb874e237374a5ba8db4c) Signed-off-by: Peter Seebach Signed-off-by: Saul Wold Signed-off-by: Richard Purdie