Skip to content

Conversation

vmcj
Copy link
Member

@vmcj vmcj commented Sep 21, 2025

On none standard locations the extended ACLs wouldn't allow this. I've now specified those explicit but I think giving access to the whole images dir would be easier and more future proof as alternative. It would give the web server access to change the DOMjudge logo though which it never needs to do (and would be an indication of broad access).

We set the mask explicit to the most loose configuration to prevent
the ACL effectively allowing less than configured.
@vmcj vmcj force-pushed the makefile_upload_logos branch from 8a2bc71 to 4970bff Compare September 24, 2025 18:56
@meisterT
Copy link
Member

The changes look fine, but I wonder: how comes that we didn't need this before, e.g. my maintainer install is working fine without it. I don't remember doing these steps manually, but perhaps I forgot.

@vmcj
Copy link
Member Author

vmcj commented Sep 24, 2025

The changes look fine, but I wonder: how comes that we didn't need this before, e.g. my maintainer install is working fine without it. I don't remember doing these steps manually, but perhaps I forgot.

I think your git checkout is on a much better location than mine is, you most likely use /home/user/git/domjudge mine lives in /nonFHS/git/domjudge so some defaults are not there at all.

And we've had some issues with those ACLs not being set for WF setups. I think this is part of that problem, every OS can set those defaults different.

@Kevinjil Kevinjil added this to the 9.0 milestone Sep 25, 2025
@vmcj vmcj added this pull request to the merge queue Sep 25, 2025
Merged via the queue into DOMjudge:main with commit ee5b197 Sep 25, 2025
36 checks passed
@vmcj vmcj deleted the makefile_upload_logos branch September 25, 2025 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants