Skip to contentSkip to conversation

Inadvertent RootFS permission pollution

DISCUSSION Bollinger, Seth 3 participants 4 messages Jul 9, 2014

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 5 lines · Seth

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?

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#2 lore raw
Quoted 10 lines · Christopher Larson
Quoted 5 lines · Seth

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.

Quoted 6 lines

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!

#3 lore raw
Quoted 22 lines · Saul Wold
Quoted 14 lines · Christopher Larson
Quoted 8 lines · Seth

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.

Quoted 7 lines

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?

Quoted 2 lines

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