Re: deken - about file/folder permissions in archive
IOhannes m zmoelnig via Pd-list <[email protected]> Thu, 8 Jan 2026 16:55:37 +0100
| Newsgroups | gmane.comp.multimedia.puredata.general |
|---|---|
| Message-ID | <[email protected]> |
On 1/8/26 15:21, [email protected] wrote: > Hi, > What are the guidelines for file and folder permissions in the compressed archives used in deken ? they should be read/writeable by the user, and at most readable by groups/others. this is my personal opinion (and not some formally agreed upon "guideline") files should never be installed as world-writeable, as this is simply a huge security hole. > As a side question : how to force file/folders permission with deken command line utility ? there's no flag or somesuch (and i don't really see a reason to add one; see above). but of course you could just invoke `chmod -R` after running `deken install`. if you are talking about the other way (for creating packages with 'deken') then I also don't see a reason why to allow the user to specify permissions of the file. *however*, 'deken package' should make sure that the permissions are "correct" (that is: readable by the user). in the past I have seen deken archives that had "ugo-rwx" permissions (nobody is allowed to do anything). this is now handled by deken-plugin (when installing), but of course packages should have proper permissions in the first place. > > I had trouble installing a package of abstraction (audiolab), specifically on plugdata (both Windows & OSX), but I also encoutered non-critical errors with puredata on windows 11.> I recreated an .dek archive using Windows compress menu, pulled it on the deken server and this resolved all troubles. > Here is a screenshot that shows the file and folder permissions in the .dek packages for audiolab(0.7.1) and for the modified version (audiolab_debug). > I'm looking for an explanation why the modified archive resolves the issue. the data you have given is very vague. we only now that there is "trouble installing" and "non-critical errors". it's hard to come up with an "explanation" without more information. if we have a better understanding of your actual problem, my opinion might change (honestly, I doubt it; but I do not understand your problem, so it's hard to tell) gdasr IOhannes -- please do not CC me for list-emails --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/CFFADIK56C3HMSHT7S4L27FGZR3TXNOQ/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmlf03kFAwAAAAAACgkQtlAZxH96Nvhc CxAAiNJHn9wAEzqrC8YF9gYzN7KnTBxzV55Yt3wlL6mFvPTNtj0Nq/cZGcUBMT8AsLnl/tkQMZr3 szyYsZRcxfDAHSy1IKgzZZzurAF/TuOEhmwUlX9qLY6vHzihfLweE6vEjgmfIlgKixXFM3zDPSTw 4KPiDCvZP+ZiB61w13CD5kNW4avsevsAQ2pa79CUcEpeu9CQh8hKaln/Um/uz+ZS0ivk5lvL7HQ+ SepospidBSLvDR4QlhQgUV7PWzTfcHjPqv5+74SQah+6RzNnKmX2Cxlo4qlAUazn/Qd5NxEaUANk BlTAJMAMvOZ93EOqwSywd2WdYdG8zlPelbcI6QS3TBKyKcnirJ+FK4NDJFBjIpXJUPraUcCCDwN3 Ke6GhumGqgyh9tqfqnX8NXI310gwZ53LF9qKo1glF2MhyRAzXUBK6kOklt1/1aTNsWXBqsXLUNwD XeDp9ayz92Xw1ECT+25QIKinJhG0la5vsWm17pdVXpZVX9P8vO8W80dA75Rn1z6zJ/tONuc3nPOm ELdng6RIC+3Y3PFwP/C78Ng4ROBh3yrjPoO/9iKvDYbGMafcLqixLgzv7fGWLtLpp1albBPM1trT 3iISp2FVC4x/GQWDJUcO1ZZzPIYtB72dhIAhjvDIO8auwZZV5TXYlxDM49w4yeZvpD7VxZcnmOmH 2xA= =XKiL -----END PGP SIGNATURE-----