Re: Packaging a shared library

[Julian Gilbey <J.D.Gilbey@qmw.ac.uk>]

On Mon, Jun 12, 2000 at 06:50:31PM +0200, Ron Rademaker wrote:
> Here's the control file, so you can see what it's for:
> 
> Source: libsafe
> Section: libs
> Priority: optional
> Maintainer: Ron Rademaker <ron@wep.tudelft.nl>
> Standards-Version: 3.1.1
> 
> Package: libsafe
> Architecture: any
> Depends: ${shlibs:Depends}
> Description:  Protection against buffer overflow vulnerabilities
>  Libsafe is a library that works with any pre-compiled executable 
>  and can be used transparently. Libsafe intercepts calls to 
>  functions known as vulnerable, libsafe uses a substitute version 
>  of the function that implements the same functionality, but makes
>  sure any buffer overflows are  contained within the current stack 
>  frame.

So if it only contains a single library, how do you actually use it?
Do you have to type something ghastly like:
$ LD_PRELOAD=/usr/lib/libsafe.0 sh -c 'unsafe-command arg1 arg2 arg3'
Or do you have a wrapper program?

If the latter, have a look at the fakeroot package to see how it's
done, and in either case, you probably want to be storing your library
in /usr/lib/libsafe/libsafe.0.0.

HTH,

   Julian

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
        Debian GNU/Linux Developer,  see http://www.debian.org/~jdg
  Donate free food to the world's hungry: see http://www.thehungersite.com/