Inadvertent RootFS permission pollution

Inadvertent RootFS permission pollution

[Bollinger, Seth]

Hello,

I recently ran into a problem where I had trouble determining why the setgid bit was set in my rootfs.  It turns out that debian has this bit set on /usr/local (where I was building from), and thus inherited this bit from that directory tree.  This surprised me, so I thought I would pass it along in case it saves anyone else some time.

Thanks,

Seth

Re: Inadvertent RootFS permission pollution

[Christopher Larson]

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth <Seth.Bollinger@digi.com>
wrote:

> I recently ran into a problem where I had trouble determining why the
> setgid bit was set in my rootfs.  It turns out that debian has this bit set
> on /usr/local (where I was building from), and thus inherited this bit from
> that directory tree.  This surprised me, so I thought I would pass it along
> in case it saves anyone else some time.


Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when it's
created?
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 1107 bytes --]

Re: Inadvertent RootFS permission pollution

[Saul Wold]

On 07/09/2014 08:18 AM, Christopher Larson wrote:
> On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth <Seth.Bollinger@digi.com>
> wrote:
>
>> I recently ran into a problem where I had trouble determining why the
>> setgid bit was set in my rootfs.  It turns out that debian has this bit set
>> on /usr/local (where I was building from), and thus inherited this bit from
>> that directory tree.  This surprised me, so I thought I would pass it along
>> in case it saves anyone else some time.
>
>
> Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
> have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when it's
> created?
>
>
>
If you have not already filed a bug for this can some one please do that 
so it does not get lost or forgotten.

Thanks
	Sau!

Re: Inadvertent RootFS permission pollution

[Bollinger, Seth]

On 7/9/14, 11:46 AM, "Saul Wold" <sgw@linux.intel.com> wrote:

>On 07/09/2014 08:18 AM, Christopher Larson wrote:
>> On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth
>><Seth.Bollinger@digi.com>
>> wrote:
>>
>>> I recently ran into a problem where I had trouble determining why the
>>> setgid bit was set in my rootfs.  It turns out that debian has this
>>>bit set
>>> on /usr/local (where I was building from), and thus inherited this bit
>>>from
>>> that directory tree.  This surprised me, so I thought I would pass it
>>>along
>>> in case it saves anyone else some time.
>>
>>
>> Ah, yes, I've hit this in the past too, thanks for bringing it up, we'll
>> have to resolve that -- perhaps have bitbake chmod g-s ${TMPDIR} when
>>it's
>> created?
>>
>>
>>
>If you have not already filed a bug for this can some one please do that
>so it does not get lost or forgotten.

Sure thing, I can do it.

Seth