bugGNU Screen - Bugs: bug #59013, Incorrect logic for SOCKET_DIR...

 
 

bug #59013: Incorrect logic for SOCKET_DIR (/run/screen) permissions

Submitter:  None
Submitted:  Wed 26 Aug 2020 02:22:40 AM UTC
 
Category:  Program Logic Severity:  3 - Normal
Priority:  * 5 - Normal Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  4.6.2
Fixed Release:  None Planned Release:  None
Work Required:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Wed 26 Aug 2020 02:22:40 AM UTC, original submission:  

screen.c (near lines 809 - 812)
Program is using the running user and their access as the master permissions on the directory for all users.  Hence, screen constantly panics mandating different permissions when multiple users (of differing privleges) attempt execution.

Program should not be mandating permissions for access beyond current user's scope.

Tested in Fedora 31 with packaged RPM.
SOCKET_DIR = /run/screen and is a common base directory for user sub-directory holding sockets.

When /run/screen is not 755:
User owning directory receives panic demanding 755 permissions.
(This demonstrates the bug.)

When /run/screen is 777:
User with group access receives panic demanding 775 permissions.
(This demonstrates the bug.)

When /run/screen is 775:
User with world access receives panic demanding 777 permissions.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

 

 

 

No changes have been made to this item

Back to the top


Powered by Savane 3.9