On Tue, Oct 23, 2018 at 11:54:08AM +0200, Pierre-Elliott Bécue wrote: > Le lundi 22 octobre 2018 à 16:39:12+0200, Christian Brauner a écrit : > > On Mon, Oct 22, 2018 at 02:29:19PM +0200, Pierre-Elliott Bécue wrote: > > > Cc-ing Christian as he proposed the patch. > > > > > > Le jeudi 18 octobre 2018 à 14:32:12+0200, Matthias Heinz a écrit : > > > > Hi, > > > > > > > > I've tried applying the patch to the 2.0.9 source. Unfortunately there > > > > have > > > > been more changes to conf.c since the release of lxc 2.0.9 and this > > > > patch wont > > > > apply without applying these changes as well. > > > > > > What amount of patches would it represent? Would it be relevant to > > > consider > > > updating lxc in buster to a newer release? > > > > You should definitely consider upgrading to 3.0.0 it will be a huge > > improvement in so many ways. > > But I understand that it is work although this might help you :) > > > > https://lists.linuxcontainers.org/pipermail/lxc-devel/2018-April/017663.html > > Let's give it a try. > > First question : where should one install pam_cgfs.so? > > It has no SOVERSION attached to it, and seems to go in /usr/lib/${ARCH}/ by > default. Would it be better to place it in /usr/lib/security? Do you (as an > upstream) have a recommendation? > > Same goes for LXC maintainers, where should I put this library?
So on Ubuntu this is put into brauner@wittgenstein|~ > ls -al /lib/x86_64-linux-gnu/security/ | grep pam_cgfs -rw-r--r-- 1 root root 71896 Oct 20 02:19 pam_cgfs.so so I think it should wherever all other pam modules are usually put. Christian
