Timeline for Setting NOEXEC for all removable drives
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2019 at 3:52 | comment | added | techimperial | It does seem odd that they removed the feature when they moved to udisks2. I have found a couple of requests for the same functionality in udisks2 but it hasn't been implemented. Yeah home can easily be made noexec with fstab. Maybe the holistic method is to disable a low privileged users ability to executes scripts(if that's possible). I have looked into udisk2 wrappers like udiskie maybe I could get something working that way. If all else fails I could write my own auto mounter but this is far from ideal. | |
| Sep 24, 2019 at 3:37 | comment | added | Tom Yan |
Btw some devs also claim that noexec is pointless as one can simply copy the executable to $HOME and execute it instead. (Though perhaps you have measures for that as well, I don't know.)
|
|
| Sep 24, 2019 at 3:35 | comment | added | Tom Yan | For the record, it seems that you can pass mount options to udisks via a udev rules / env var, back in the days when udisks was udisks"1". | |
| Sep 24, 2019 at 3:33 | comment | added | Tom Yan | It seems that from udisks2's devs point of view, the frontend (gnome in this case) should be the one that is responsible for allowing the users to set desired default mount options. If you can't find anything for that in dconf-editor (where you can disable automounting), probably gnome's dev don't think it's necessary (after all they prefer things to be "simple" since version 3), and hence it isn't actually possible. | |
| Sep 24, 2019 at 3:00 | history | asked | techimperial | CC BY-SA 4.0 |