--- Em ter, 22/1/13, Armin K. escreveu:

> De: Armin K.
> Assunto: Re: [blfs-dev] Xulrunner-18.0.1: libxpcom.so permissions
> Para: "BLFS Development List"
> Data: Terça-feira, 22 de Janeiro de 2013, 13:31
> On 01/22/2013 04:27 PM, Fernando de
> Oliveira wrote:
> > Hi, Armin,
> >
> > I reinstalled Xulrunner/Firefox to comply with the new
> page you
> > modified (only difference, I did not install system
> libevent), and
> > again, it is even smaller (disk space) than my previous
> install script/mozconfig, thank you for the good work!
> >
> > As written in
> >
> > <http://wiki.linuxfromscratch.org/blfs/ticket/3658#comment:4>
> >
> > I was expecting something like
> >
> > chmod -v 0755
> /usr/lib/xulrunner-devel-${some-version-some-day}/sdk/bin/xpcshell
> >
> > But I noticed that you have also included
> >
> > chmod -v 755 /usr/lib/xulrunner-18.0.1/libxpcom.so
> >
> > In LFS/BLFS many /usr/lib files are 0664 and many are
> 0755, in Lubuntu
> > (happened to have an ssh netbook connected) only one is
> 0755, all other
> > seem to be 0644.
> >
> > Pardon my ignorance, is the command setting permissions
> for libxpcom.so
> > necessary, is there a rule, or is it a question
> personal of preference?
> >
> > More important, should they be changed in my machine,
> for security
> > reasons?
> >
> > []s,
> > Fernando
> >
> 
> We do this for lot of packages, but we never had time to
> finish it for 
> every single one.
> 
> You'll notice when you run a ldd on a non-executable library
> that you'll 
> get a warning about a library not executable.
> 
> Also, libtool by default installs libraries as 755 so I
> guess it has 
> been some sort of standard.
> 
> Nothing will happen to library if or if it's not executable
> though.

Ok. Thanks, Armin.

As I replied to Matt, keeping them as they are.

Good to know about the warning and about libtools default install 
permission settings.

[]s,
Fernando
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to