[SOLVED] wpa_supplicant docs are set to read-only

j_v · 01-13-2014, 07:34 PM

I was looking at the wpa_supplicant package this last weekend. After extracting the package to a separate temporary directory and having looked the contents, I was surprised when my `rm -rf` of the temporary directory failed. The problem was that the whole of the usr/doc/wpa_supplicant-2.0 directory contents were read-only. I looked at the SlackBuild for wpa_supplicant and saw this:

Code:

chmod -R a-w $PKG/usr/doc/$PKGNAM-$VERSION/*

on line 157. Is this a typo? Was it supposed to be:

Code:

chmod -R a-x $PKG/usr/doc/$PKGNAM-$VERSION/*

to ensure that the examples would have to be manually set to +x to be executed?
I realize this is pretty minor, but it seemed weird to me when the dir removal failed.

-John

Richard Cranium · 01-13-2014, 07:43 PM

I can't think of a scenario where I'd want random scripts in the /usr/doc directory executable.

j_v · 01-13-2014, 07:46 PM

Thanks for your response. So probably a typo, then. Since all of the example scripts in /usr/doc/wpa_supplicant-2.0/examples are just that: executable. Not so minor, maybe.

EDIT: Should this be mailed in as a bug to Pat?

EDIT #2: the chmod command should probably be:

Code:

chmod -R -a-x $PKG/usr/doc/$PKGNAM-$VERSION/examples/*

rather than my other code block above.

EDIT #3: or better yet:

Code:

find $PKG/usr/doc/$PKGNAM-$VERSION/* -executable ! -type d -exec chmod a-x {} \;

j_v · 01-27-2014, 11:59 AM

How do I make this into a bug report?

sanjioh · 01-28-2014, 12:28 PM

An email to Pat is usually fine as bug report

j_v · 01-28-2014, 03:32 PM

Thank you. I've looked in several different slackware docs and the most definitive had been the install email that recommends posting bug reports here. I will email a report today.

EDIT: hmmm, easy to say, but I cannot find his address. Perhaps, instead, I should use info@slackware.com?

sanjioh · 01-29-2014, 03:45 AM

ftp://ftp.osuosl.org/pub/slackware/s...lackware-HOWTO

j_v · 01-29-2014, 03:27 PM

Ouch. I would have sworn I had read that one.

j_v · 01-30-2014, 05:15 PM

Closing this thread. It is simple enough to do a search of the /usr/doc heirarchy and set permissions as desired.

Code:

find /usr/doc ! -type l ! -perm -u=w | xargs chmod u+w
find /usr/doc ! -type l -perm -go=w | xargs chmod go-w
find /usr/doc ! -type l ! -type d \( -perm -u=x -o -perm -g=x -o -perm -o=x \) | xargs chmod a-x

sanjioh · 01-30-2014, 05:36 PM

yes, the fix for this is simple indeed. now let's see what Pat will decide about the permissions inside the package

j_v · 01-30-2014, 05:53 PM

sanjioh, you are right.