[OE-core] dbus build host uid/gid leaking into target home directory

[Paul Eggleton]

On Sunday 12 October 2014 16:05:41 Peter A. Bigot wrote:
> On 10/11/2014 12:16 PM, Peter A. Bigot wrote:
> > Back at
> > http://lists.openembedded.org/pipermail/openembedded-core/2011-December/05
> > 3836.html it was noted that the dbus home directory /var/lib/dbus on the
> > target was using the build host uid/gid.  Various discussion agreed this
> > shouldn't happen, but there was no resolution in the thread.
> > 
> > I found https://bugzilla.yoctoproject.org/show_bug.cgi?id=1711 which
> > is marked fixed, but on a newly installed system I find:
> > 
> > root at beaglebone:~# ls -l /var/lib
> > total 52
> > drwxr-xr-x 2 root root 4096 Oct 11  2014 alsa
> > drwxr-xr-x 2 root root 4096 Oct 11  2014 arpd
> > drwxr-xr-x 2 root root 4096 Oct 11 12:30 connman
> > drwxr-xr-x 2  102  105 4096 Oct 11  2014 dbus
> > 
> > where the dbus uid/gid is from my host system as shown by:
> > 
> > root at beaglebone:~# grep dbus /etc/passwd
> > messagebus:x:999:998::/var/lib/dbus:/bin/false
> > llc[140]$ grep dbus /etc/passwd
> > messagebus:x:102:105::/var/run/dbus:/bin/false
> 
> Pilot error.  This ultimately turned out to be a side-effect of the way
> I create my image media: I unpacking the rootfs tar file onto a mounted
> sdcard outside the pseudo environment and forgot that tar records
> user/group by name not uid/gid.

I used to use this method previously, and I guess it can still work if you're 
not including certain packages in your image - but I wonder if we should note 
this potential pitfall somewhere in the documentation. I'm not entirely sure 
where such a note would go, though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre