mainsail file permissions 403 errors -- set umask to 022 #458

New Issue

2024-04-21T10:58:57+02:00

slashbeast commented

2024-04-21 10:58:57 +02:00

(Migrated from github.com)

Linux Distribution

Raspbian

What happened

I've run update from shell that had umask set to 077 which made ~/mainsail with permissions of 700 that then prevents it from working as the nginx cannot enter the directory if it lacks +x permissions.

What did you expect to happen

I would expect the permissions to be enforced. Best would be to just add umask 022 at the very top of kiauh.sh and it will have no effect on most default configurations but will fix any potential permissions issues for those that have umask of different value. I copied my .zshrc and this is how umask got changed.

How to reproduce

run umask 077
run kiauh.sh and update mainsail
try to access webui, 403 forbidden until you chmod 755 ~/mainsail.

Additional information

### Linux Distribution Raspbian ### What happened I've run update from shell that had `umask` set to `077` which made `~/mainsail` with permissions of `700` that then prevents it from working as the `nginx` cannot enter the directory if it lacks `+x` permissions. ### What did you expect to happen I would expect the permissions to be enforced. Best would be to just add `umask 022` at the very top of `kiauh.sh` and it will have no effect on most default configurations but will fix any potential permissions issues for those that have umask of different value. I copied my `.zshrc` and this is how umask got changed. ### How to reproduce - run `umask 077` - run `kiauh.sh` and update mainsail - try to access webui, `403 forbidden` until you `chmod 755 ~/mainsail`. ### Additional information -

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: h3n3/kiauh#458