dotnet/aspnetcore

allow setting permissions on unix sockets

Open

#17,706 opened on Dec 9, 2019

View on GitHub
 (10 comments) (3 reactions) (0 assignees)C# (10,653 forks)batch import
affected-very-fewarea-networkingenhancementfeature-kestrelgood first issuehelp wantedseverity-nice-to-have

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

Hello, It would be useful to allow setting permissions on unix sockets. There was a recommendation somewhere to run kestrel as same user as www server, but that is not always a good thing to do. For example my security model assumes there are many apps behind my reverse proxy and they do not need access to other apps, and the server also does not need access to directories and files of these apps, just to the socket. Of course one solution to the problem is containerization, but I don't think it is/should be the only solution. Plain user isolation also should work relatively straightforward.

Contributor guide

Research direction
Explore the Kestrel server source code in the aspnetcore repository to locate where Unix sockets are created. Investigate how to set file permissions (e.g., using chmod) on the socket file after creation or during binding. Check if there are existing APIs or configuration options for Unix socket permissions in Kestrel or other parts of ASP.NET Core.
Tech stack
csharp
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#ASP.NET CoreUnix socket permissions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40