[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd

2019-07-29 Thread Tobias Karnat
I can confirm as well, 237-3ubuntu10.25 fixes the issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart

[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd

2019-06-27 Thread Tobias Karnat
This bug also affects my company. Please integrate the fix soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart

[Touch-packages] [Bug 1804417] Re: runuser doesn't authenticate PAM modules

2018-11-23 Thread Tobias Karnat
As a workaround we now use the following configuration as the maintainer suggested to us: # cat /etc/pam.d/runuser #%PAM-1.0 authsufficient pam_rootok.so session requiredpam_localuser.so Which works as well: # runuser domainuser runuser: cannot open session:

[Touch-packages] [Bug 1804417] [NEW] runuser doesn't authenticate PAM modules

2018-11-21 Thread Tobias Karnat
Public bug reported: We use the pam_localuser.so PAM module to authenticate only local users for root to become. Because we don't want that root can become a domain user (as we use sssd with ad integration). This works well with the su program, but fails with runuser. We added the following in