Darshaka Pathirana
Darshaka Pathirana
I sometimes want to allow all my users on the system to use the restic binary (mostly Linux Desktop systems). I then need `restic` to have executable right for `other`....
(Sorry for the delay, somehow missed your answer). I think I get your point, but in our scenario we (the admins) would like to be able to run `restic snapshots`...
@TheLastProject Sorry, you lost me here. Why / Where are these capabilities set? Is this somehow specific to restic itself (shall we file a security bug there)?
Hey @paulfantom, @TheLastProject, sorry for the very long delay. What about only setting the capability when the "other" execute permission is not set? (I updated my PR (also rebased it...
Oh, yes... Good point! I'll update my PR...
And: shouldn't we also unset the capability when owner and group are 'root' (again)? (I so sorry for this comment flood... )
@jeffgoh Did you solve the problem? I just installed cells-sync on LMDE5 (Linux Mint Debian Edition 5) based on Debian/bullseye and have the same problem.
Oh, sure! I'm running the latest stable version of cells-sync v0.9.2 on Debian/bullseye. Please note, that cells-sync fails to start on Debian/bullseye, see #41, but I installed `libindicator3-7_0.5.0-4_amd64.deb` + `libappindicator3-1_0.4.92-7_amd64.deb`...
I have a quite similar setup. Server is (still) running Debian/bullseye + Docker Image pydio/cells:4.3.4. Desktop is Debian/bookworm. I haven't seen corrupt files so far, but quite a lot of...
This is still an issue in Debian/bullseye. Is there anything I can do to help to resolve this issue. Thanks!