| 1 |
On Sat, Mar 21, 2020 at 8:39 AM William Kenworthy <billk@×××××××××.au> wrote: |
| 2 |
> |
| 3 |
> I have an encrypted usb thumb drive I use to transfer files from work |
| 4 |
> (Win10) to home (gentoo) - the encryption and access is via a program |
| 5 |
> that is stored and executed from the thumb drive. |
| 6 |
> |
| 7 |
> Some time back, it became impossible to execute files stored on the |
| 8 |
> thumb drive. I found I could get it to work if it was mounted within |
| 9 |
> the users home directory. Since the last round of updates that has |
| 10 |
> become broken as well. |
| 11 |
|
| 12 |
I'm aware of 2 things that would break this: |
| 13 |
|
| 14 |
- The filesystem is mounted with the noexec flag set. |
| 15 |
- For filesystems that don't have permissions natively (like FAT), the |
| 16 |
filesystem is mounted with a umask that prevents the execute bit from |
| 17 |
being set. |
| 18 |
|
| 19 |
You could check both of these things in /proc/mounts when the |
| 20 |
filesystem is mounted. |
| 21 |
|
| 22 |
How to fix it depends on what is actually mounting the filesystem in |
| 23 |
the first place. How do you access the drive after you plug it in? |
Archives