Trying to build statically linked nss-winbind & pam-winbind

[Louis Bouchard]

Hello,

Le 11/10/2016 14:04, L.P.H. van Belle a écrit :
> Hai,
> 
>  
> 
> Saw you message on samba-technical.
> 
> Have you tried to change you nsswitch.conf to this setup.
> 
> 
> winbind [success=return notfound=continue unavail=continue tryagain=continue] compat
> 
> which seems more logical to me.
> 
>  
> 
>  
> 

Thank you for the suggestion, but it will still leads to failure to upgrade. The
winbind statement still being the first, it will trigger SEGV since it will
still try to dlopen() to an inexistant library.

The problem is fairly trivial to test :
1) Start an ubuntu Trusty container
2) Disable the trusty-updates and trusty-security archives in /etc/apt/sources.list
3) sudo apt-get update
4) sudo apt-get install samba winbind libnss-winbind libpam-winbind
5) Set /etc/nsswitch.conf to : passwd: winbind compat
6) Enable trusty-updates & trusty-security in /etc/apt/sources.list
7) sudo apt-get install samba winbind libnss-winbind libpam-winbind

While installing, you will see things similar to this :

> Unpacking libnss-winbind:amd64 (2:4.3.11+dfsg-0ubuntu0.14.04.1) over (2:4.1.6+dfsg-1ubuntu2) ...
> dpkg-deb: error: subprocess tar was killed by signal (Segmentation fault), core dumped
> dpkg: error processing archive /var/cache/apt/archives/libpam-winbind_2%3a4.3.11+dfsg-0ubuntu0.14.04.1_amd64.deb (-
> -unpack):
>  subprocess dpkg-deb --control returned error exit status 2
> dpkg-deb: error: subprocess tar was killed by signal (Segmentation fault), core dumped

Inverting the winbind & compat statements and running "sudo apt-get -f install"
will fix the situation.

I agree that this is not a samba issue, but a possible solution is to have those
libraries statically linked so they don't need to dlopen().

Kind regards,

...Louis

-- 
Louis Bouchard
Software engineer,
Ubuntu Developer / Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61