Bug#644019: reglookup: Please package latest upstream (1.0.1)
tim-forensics at sentinelchicken.org
Mon Jun 15 16:14:03 UTC 2015
> You can now base your work on this updated package:
Thanks much for putting this together.
> On Mon, 08 Jun 2015, Raphael Hertzog wrote:
> > we just tried the trunk. It's better but there are still multiple
> > problems:
> > - LDFLAGS is not used when you link the executables (it's only used when
> > you link libregfi)
> > - the default value for LDFLAGS is wrong, "-z relro" is an option for "ld" but
> > when you pass it through gcc you need "-Wl,-z,relro"
> > - I saw you tried to hack up some code to setup the SONAME... it does set
> > the SONAME on the library but the library is still installed under the
> > wrong name (libregfi.so instead of the name set in the SONAME)
> > - the SONAME must not encode the full version... it's only a simple
> > counter of API/ABI compatibility. Please use "libregfi.so.0" as
> > the first SONAME (and then bump to libregfi.so.1 when you break
> > the ABI/API, etc.) (and 99.99.99.X looks really wrong as a version number :))
> Tim, I hope you can fix those issues quickly now that we have identified
> how to properly handle versioned libraries and that you can make a new
I'll try. I'm super busy this summer, as I was accepted as a Blackhat
speaker and have a lot of prep to do. It is definitely on my list.
> For reference, we only have the attached two patches in use in Kali.
> One to disable the build of the python module (we do it ourselves
> in debian/rules) and one to use a proper versioned library.
> > While lookinto in Scons support for versioned shared library I found this:
> > http://stackoverflow.com/questions/2997001/how-to-get-shared-library-names-like-libhello-so-0-0-1-with-scons
> > http://www.scons.org/doc/production/HTML/scons-user/apb.html#b-SharedLibrary
> The attached patches make use of that.
Great, thanks for the info.
More information about the forensics-devel