-
Notifications
You must be signed in to change notification settings - Fork 84
Open
Description
I am a bit puzzled by the permissions on the temporary directory created to be used as rservers' server-data-dir. The directory is initialized here. According to the tempfile docs...
the directory is readable, writable, and searchable only by the creating user ID.
However, when launching RStudio via jupyter-ression-proxy, I see that it has created a server-data-dir with the following permissions:
$ ls -l /tmp | grep tmpmkugxl8q
drwxrwxrwt. 4 testuser testuser 160 Nov 19 13:24 tmpmkugxl8q
$ ls -l /tmp/tmpmkugxl8q
total 76
-rw-------. 1 testuser testuser 4096 Nov 19 13:24 rstudio-os.sqlite
-rw-------. 1 testuser testuser 32768 Nov 19 13:24 rstudio-os.sqlite-shm
-rw-------. 1 testuser testuser 32992 Nov 19 13:24 rstudio-os.sqlite-wal
drwxrwxrwt. 2 testuser testuser 60 Nov 19 13:24 rstudio-rserver
drwxrwxrwt. 2 testuser testuser 40 Nov 19 13:24 rstudio-rsession
-rw-------. 1 testuser testuser 44 Nov 19 13:24 tmp5imqbvf8
So the data dir is readable for other users, and rserver is creating two directories in it that are world readable and writeable. Is this expected behavior? Is there anyway to lock this down?
consideRatio
Metadata
Metadata
Assignees
Labels
No labels