2.2.8 source save set protections

[COLLOT Jean-Yves]

Once more, you are perfectly right, And I am going to fix those issues :

- by adding the /INTERCHANGE switch in my BACKUPs commands. In fact, I
sincerely though that there was no site-dependent ACLs in the kit, but I was
wrong. Shame on me.

- All files will be owned by SYSTEM ([1,4]) and  correctly protected
(S:RWED,O:RWED,G:RE,W)

- I'll find some way to give a specific name to upcoming versions. What do
you think of adding the release date (such as samba-2_2_8-09-AUG-2004.zip) ?

JYC


-----Message d'origine-----
De : John E. Malmberg [mailto:wb8tyw at qsl.net] 
Envoyé : vendredi 13 août 2004 01:02
À : samba-vms at lists.samba.org
Objet : 2.2.8 source save set protections

There seems to be some minor issues with the backup save set for the 
sources.

It appears that the backup save-set has some of the source files 
protected world write access.

Also it appears that /INTERCHANGE was not used when making the saveset.

If you are making a BACKUP saveset for distribution, /INTERCHANGE is 
needed so that the binary security identifiers that may be unique to the 
site are not recorded on the backup copy.

Also, can the you tag zip file and backup save set name with an 
identifier to indicate which sub release it is for?  This will make it 
easier to determine if people are running the current version.

Something like samba-2_2_8_JYC_009-src would help.

Thanks,
-John
wb8tyw at qsl.net
Personal Opinion Only

PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:

http://www.catb.org/~esr/faqs/smart-questions.html