Hi, As reported on JBEAP-12374[1], there is some discrepancies between the ZIP file we provided for Widlfy/EAP and the RPM generate. Most of those discrepancies - or the most relevant ones, are some fine tuning performed on the (POSIX) privileges (things such as removing the write privilege for member of the same group as the owner of the file). I've looked into this and because those files are produced by our own Maven plugin (as part of wildfly-build-tools), we can not simply modify the assembly.xml. Which actually is probably for the best, as it would made the assembly file quite cumbersome. Anyhow, I've worked on a proposal[2] for the wildfly-build-tools, but when I reported the problem on WFLY-9574[3], Brian suggested I started a discussion here. So does anyone have a (strong) opinion about this issue and/or how to resolve it ? :) (For the record, I do think it is best to fix the privileges to follow what the RPM does for us for now, but if you feel this issue should not be addressed, and dev- the issue, I'm certainly not opposed to it either). [1] https://issues.jboss.org/browse/JBEAP-12374 [2] https://github.com/wildfly/wildfly-build-tools/pull/40 [3] https://issues.jboss.org/browse/WFLY-9574 _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

I think we need to start with the assumption that the permissions we have in the zip are the way they are for a reason and evaluate possible changes based on discussion here of each type of change. Maybe the RPM settings are better, maybe they are not. Or maybe they are better but the improvement is not worth the disruption a change may cause to our end users, who may rely on the current zip settings. Or maybe what we have in the zip is clearly wrong and doesn't follow our own intent. I expect we'll probably see a little of each category, although hopefully some changes for WF 11 removed the "clearly wrong and doesn't follow our intent" cases. :) On Tue, Nov 28, 2017 at 8:37 AM, Romain Pelisse <belaran(a)redhat.com&gt; wrote: > Hi, > > As reported on JBEAP-12374[1], there is some discrepancies between the > ZIP file we provided for Widlfy/EAP and the RPM generate. Most of those > discrepancies - or the most relevant ones, are some fine tuning performed > on the (POSIX) privileges (things such as removing the write privilege for > member of the same group as the owner of the file). > > I've looked into this and because those files are produced by our own > Maven plugin (as part of wildfly-build-tools), we can not simply modify the > assembly.xml. Which actually is probably for the best, as it would made the > assembly file quite cumbersome. > > Anyhow, I've worked on a proposal[2] for the wildfly-build-tools, but > when I reported the problem on WFLY-9574[3], Brian suggested I started a > discussion here. So does anyone have a (strong) opinion about this issue > and/or how to resolve it ? :) > > (For the record, I do think it is best to fix the privileges to follow > what the RPM does for us for now, but if you feel this issue should not be > addressed, and dev- the issue, I'm certainly not opposed to it either). > > [1] https://issues.jboss.org/browse/JBEAP-12374 > [2] https://github.com/wildfly/wildfly-build-tools/pull/40 > [3] https://issues.jboss.org/browse/WFLY-9574 > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- Brian Stansberry Manager, Senior Principal Software Engineer Red Hat