Fix for SSPCPP-961 overwrites existing ACLs on patch update install
Basics
Logistics
Basics
Logistics
Description
The installer for 3.4.1 with the new ACL restrictions appears to overwrite existing ACLs on a patch upgrade install as well as set them on a new install. Per mailing list discussion this appears to be unintentional, and the installer was expected to only set ACLs for a fresh install and leave any existing ACLs in place for an upgrade patch install.
Environment
None
Activity
Show:
Paul B. Henson March 10, 2023 at 2:51 AM
I installed 3.4.0 and then the prerelease 3.4.1.2 on top of it, the ACL on the install directory didn’t change, so looks good from here, thanks…
(Note these have zlib and curl updated also, which was the original reason I was working on a build.)
I don’t need to release it tomorrow so I can wait for testing into next week if it happens.
Rod Widdowson March 9, 2023 at 2:41 PM
Never say never but I believe that I have fixed this by just not doing the ACL dance if we are upgrading.
Tested on an upgrade and on a clean install. It appears to do the right thing, but if it would be possibvle for to test this before we move the patch from prerelease to release it would be appreciated. As discussed on the list these things are never as easy as one might hope.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The installer for 3.4.1 with the new ACL restrictions appears to overwrite existing ACLs on a patch upgrade install as well as set them on a new install. Per mailing list discussion this appears to be unintentional, and the installer was expected to only set ACLs for a fresh install and leave any existing ACLs in place for an upgrade patch install.