[Slackbuilds-users] find in SlackBuilds: again

[Erik Hanson]

On Sun, 24 Apr 2016 16:51:01 +0200
Andrzej Telszewski <atelszewski at gmail.com> wrote:

> On 24/04/16 16:41, Willy Sudiarto Raharjo wrote:
> >> I don't understand what you mean;)
> >> When I wrote -current, I meant Slackware -current.
> >> Should the -L switch be there or not in SlackBuilds.org? :)
> >>
> >> Also, there is a difference between the permissions in
> >> SlackBuilds.org and Slackware's -current:
> >>
> >> SlackBuilds.org:
> >> find -L . \
> >>  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
> >>   -o -perm 511 \) -exec chmod 755 {} \; -o \
> >>  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
> >>   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
> >>
> >> Slackware's -current:
> >> find . \
> >>   \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511
> >> \) \ -exec chmod 755 {} \; -o \
> >>   \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440
> >> -o -perm 400 \) \
> >>   -exec chmod 644 {} \;
> >>
> >>
> >> 750 and 640 are not present in Slackware's SlackBuilds.  
> >
> > we expect that maintainers stick to the template, so we should use
> > -L 
> 
> Maybe it is a good time to change it? It does not sound too secure.
> Somebody might place something bad in the source tarball. And it
> might be just by accident, like in my case. And bad things can follow.
> 
> >

This is where -L was added, with explanation:

https://slackbuilds.org/cgit/templates/commit/?h=14.1&id=2ca255d617118e


-- 
Erik