user is in debian-tor group on fresh install

[Joshua Powers]

Summary:
Unexpectedly, after a fresh install a user belongs to the debian-tor group

Expected Result:
The user should not belong to the debian-tor group

Actual Result:
https://paste.ubuntu.com/p/zCcBFCJw2C/

Steps to reproduce:
1. Download latest (20180605) server-live Bionic ISO
2. Do a default install
3. On reboot, run id or groups and observe the groups you belong to

[Robie Basak (racb)]

> The user should not belong to the debian-tor group

According to https://git.launchpad.net/ubuntu/+source/user-setup/tree/user-setup-apply#n251 it's intentional that a user will end up in debian-tor if that group exists. However I'm confused as to why the group is being created in the first place. Does the same behaviour apply also to the libvirtd group?

On Bionic release cloud VM images and lxd images I don't see a debian-tor on the system at all, as expected.

[Joshua Powers (powersj)]

An install of the daily Bionic d-i ISO did not reproduce this issue:

https://paste.ubuntu.com/p/5WWy9CHDRb/

Of note, the d-i install was not part of the debian-tor or libvirtd groups.

[Michael Hudson-Doyle (mwhudson)]

I guess cloud-init must create any listed groups that are mentioned in
users.groups. I suppose subiquity could filter the default groups it gets
from user-setup through /target/etc/groups or something?

On 6 June 2018 at 06:05, Joshua Powers <email address hidden> wrote:

> An install of the daily Bionic d-i ISO did not reproduce this issue:
>
> https://paste.ubuntu.com/p/5WWy9CHDRb/
>
> Of note, the d-i install was not part of the debian-tor or libvirtd
> groups.
>
> --
> You received this bug notification because you are subscribed to
> subiquity.
> https://bugs.launchpad.net/bugs/1775228
>
> Title:
> user is in debian-tor group on fresh install
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/subiquity/+bug/1775228/+subscriptions
>