Bug 667252 - screen creates a directory in /var/run/screen that is writable by the user. Is this necessary?
Summary: screen creates a directory in /var/run/screen that is writable by the user. ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: screen
Version: rawhide
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-04 23:05 UTC by Daniel Walsh
Modified: 2011-07-17 16:48 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-04 15:32:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.