> > Other than the obvious approach of enabling systemd-userdb for Ubuntu, > > I don't see how that would help, given that sytemd-userdb.service has > > RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > > You basically have the same issue as with systemd-logind.service. Or am I > missing something here?
I may be misunderstanding how upstream intends it all to work, but I believe that since the userdb service does include AF_INET/AF_INET6 in RestrictAddressFamilies, those are *allowed* families for the userdb service. The naming of the parameter doesn't seem great to me, at first read it's hard to understand if the assigned families are *allowed* or *restricted*...but I'm pretty sure the assigned families are *allowed* and all other (unlisted) families are *restricted* (blocked), meaning userdb is allowed to make inet/inet6 connections, unlike logind, which has only: RestrictAddressFamilies=AF_UNIX AF_NETLINK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
