Bug 667252

Summary: screen creates a directory in /var/run/screen that is writable by the user. Is this necessary?
Product: [Fedora] Fedora Reporter: Daniel Walsh <dwalsh>
Component: screenAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: mlichvar, redhat-bugzilla, sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-04 15:32:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Walsh 2011-01-04 23:05:20 UTC
Description of problem:

This would allow a user to get around quota constraints.

Comment 1 Miroslav Lichvar 2011-02-04 12:11:28 UTC
We could configure screen to use $HOME/.screen directory instead, but then the multiuser feature couldn't be enabled just by adding suid bit to the screen binary. Not sure how many users actually use that and if it's worth keeping /var/run/screen.

Also, updating to a screen using a different directory might cause problems for users as new screen won't find the sockets created by old screen.

Comment 2 Miroslav Lichvar 2011-02-04 13:40:21 UTC
I'm considering update to a 4.1.0 pre snapshot. It uses an incompatible protocol with 4.0.3, so reattaching to old sessions won't be possible anyway and we might as well switch to the $HOME directory and support the multiuser feature only through a spec build-time option.

Comment 3 Miroslav Lichvar 2011-02-04 15:32:10 UTC
$HOME/.screen is now used in screen-4.1.0-0.1.20101110git066b098.fc15.

Comment 4 Miroslav Lichvar 2011-02-10 17:27:08 UTC
This was reverted due to bug #676663.