* Inadvertent RootFS permission pollution
@ 2014-07-09 14:37 Bollinger, Seth
2014-07-09 15:18 ` Christopher Larson
0 siblings, 1 reply; 4+ messages in thread
From: Bollinger, Seth @ 2014-07-09 14:37 UTC (permalink / raw)
To: yocto
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Inadvertent RootFS permission pollution
2014-07-09 14:37 Inadvertent RootFS permission pollution Bollinger, Seth
@ 2014-07-09 15:18 ` Christopher Larson
2014-07-09 16:46 ` Saul Wold
0 siblings, 1 reply; 4+ messages in thread
From: Christopher Larson @ 2014-07-09 15:18 UTC (permalink / raw)
To: Bollinger, Seth; +Cc: yocto
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Inadvertent RootFS permission pollution
2014-07-09 15:18 ` Christopher Larson
@ 2014-07-09 16:46 ` Saul Wold
2014-07-09 16:48 ` Bollinger, Seth
0 siblings, 1 reply; 4+ messages in thread
From: Saul Wold @ 2014-07-09 16:46 UTC (permalink / raw)
To: Christopher Larson, Bollinger, Seth; +Cc: yocto
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!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Inadvertent RootFS permission pollution
2014-07-09 16:46 ` Saul Wold
@ 2014-07-09 16:48 ` Bollinger, Seth
0 siblings, 0 replies; 4+ messages in thread
From: Bollinger, Seth @ 2014-07-09 16:48 UTC (permalink / raw)
To: Saul Wold, Christopher Larson; +Cc: yocto
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-07-09 16:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-09 14:37 Inadvertent RootFS permission pollution Bollinger, Seth
2014-07-09 15:18 ` Christopher Larson
2014-07-09 16:46 ` Saul Wold
2014-07-09 16:48 ` Bollinger, Seth
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.