Bug 5762 - user socket handling is very complex
Summary: user socket handling is very complex
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Henrik Andersson
Depends on:
Reported: 2015-12-28 14:24 CET by Pierre Ossman
Modified: 2024-03-19 23:45 CET (History)
2 users (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2015-12-28 14:24:00 CET
Right now our handling of sockets for communication with the master is a bit messy. We listen on TCP for a call to create a user specific Unix socket, which is then dynamically created and cleaned up after a while. This is the mechanism used to enforce authentication for the master.

Bug 2796 introduced the requirement of SO_PASSCRED for communicating over the user sockets (at least for connecting to sessions). Using this mechanism for authentication would be much simpler. There would be just a single Unix socket that could exist for as long as vsmserver is running. No more TCP or cleanup timeouts or all of that complexity.

Note You need to log in before you can comment on or make changes to this bug.