On Fri, 6 Oct 2000 [EMAIL PROTECTED] wrote:
> If you want to use rpath then you might want to check it with
> somebody with experience in security (Debian security team?),
rpath has some advantages in this case over hardwiring the paths into the
executable (for example, you can add paths at runti
On Fri, 6 Oct 2000 [EMAIL PROTECTED] wrote:
> If you want to use rpath then you might want to check it with
> somebody with experience in security (Debian security team?),
rpath has some advantages in this case over hardwiring the paths into the
executable (for example, you can add paths at runt
If you want to use rpath then you might want to check it with
somebody with experience in security (Debian security team?),
I think one of the arguments was about security. I may be
totally off here, but IIRC rpath also checks an environment
variable and this is considered very insecure.
HTH
t.aa
If you want to use rpath then you might want to check it with
somebody with experience in security (Debian security team?),
I think one of the arguments was about security. I may be
totally off here, but IIRC rpath also checks an environment
variable and this is considered very insecure.
HTH
t.a
On Thu, 5 Oct 2000, Rick Younie wrote:
> Yeah, I talked to the Regina maintainer about this. He's happier
> leaving the libs in /usr/lib rather than using rpath so I guess
> he'd feel the same about modifying ld.so.conf.
Another option for loadable modules would be to dlopen() them with the
full
On Thu, 5 Oct 2000, Rick Younie wrote:
> Yeah, I talked to the Regina maintainer about this. He's happier
> leaving the libs in /usr/lib rather than using rpath so I guess
> he'd feel the same about modifying ld.so.conf.
Another option for loadable modules would be to dlopen() them with the
ful
> > Another thing you could do is to stuck the libs in a
> subdirectory and have
> > your postinst and postrm edit /etc/ld.so.conf. That sounds like the
> > traditional way to me, but then that was before rpath...
>
> It's a little trickier than the way xaw3d handled it though. A
> half-dozen pa
> > Another thing you could do is to stuck the libs in a
> subdirectory and have
> > your postinst and postrm edit /etc/ld.so.conf. That sounds like the
> > traditional way to me, but then that was before rpath...
>
> It's a little trickier than the way xaw3d handled it though. A
> half-dozen p
> I was wondering about rpath as well. I maintain a couple
> packages that drop 5 function libs for regina-rexx in /usr/lib.
> There are probably another 6-8 that someone might package.
> /usr/lib could soon be as bad as /var/lib/dpkg/info. You can
> pretty much go for coffee on your first 'dpkg
Simon Richter wrote:
> On Tue, 3 Oct 2000, Sean 'Shaleh' Perry wrote:
>
>> rpath hardcodes an item's location. If this item later moves,
>> everything using it gets confused. rpath is generally frowned
>> upon.
>
> rpath adds additional path elements to the search list. Libraries are
> still fou
> I was wondering about rpath as well. I maintain a couple
> packages that drop 5 function libs for regina-rexx in /usr/lib.
> There are probably another 6-8 that someone might package.
> /usr/lib could soon be as bad as /var/lib/dpkg/info. You can
> pretty much go for coffee on your first 'dpkg
Simon Richter wrote:
> On Tue, 3 Oct 2000, Sean 'Shaleh' Perry wrote:
>
>> rpath hardcodes an item's location. If this item later moves,
>> everything using it gets confused. rpath is generally frowned
>> upon.
>
> rpath adds additional path elements to the search list. Libraries are
> still fo
12 matches
Mail list logo
