[SSSD] cwrap test roadblock

Lukas Slebodnik lslebodn at redhat.com
Mon Dec 1 08:27:11 UTC 2014


On (29/11/14 23:32), Simo Sorce wrote:
>On Fri, 28 Nov 2014 12:01:29 +0100
>Sumit Bose <sbose at redhat.com> wrote:
>
>> On Thu, Nov 27, 2014 at 03:09:32PM +0200, Nikolai Kondrashov wrote:
>> > Hi everyone,
>> > 
>> > While trying to arrange running sssd under cwrap in "make check" I
>> > came upon this roadblock:
>> > 
>> > There doesn't seem to be a way to make libnsss_sss use server
>> > sockets in non-default location at runtime, only at build time. And
>> > it seems that doing it at runtime would be a security issue.
>> > 
>> > That means that we can't include tests involving libnss_sss into
>> > "make check", as that is not guaranteed to be invoked on a build
>> > with a special location where the current user can write to.
>> > 
>> > This leaves us with being able to run these tests under CI only,
>> > which can arrange for special configure options and thus locations.
>> > 
>> > Could there be another way? Am I missing something?
>> 
>> It is a bit hackish, but maybe with something like
>> http://ohnopub.net/~ohnobinki/bin_replace_string/ a copy of the
>> libnss_sss can be created during makr test with alternative paths
>> which are better suited for the tests?
>
>I do something like that (binary patching) here:
>https://fedorapeople.org/cgit/simo/public_git/gss-proxy.git/tree/proxy/tests/runtests.py#n238
>
>Works ok :-)
>
Why is it better than different prefix?

LS



More information about the sssd-devel mailing list