dotnet/aspnetcore

allow setting permissions on unix sockets

Open

#17 706 ouverte le 9 déc. 2019

Voir sur GitHub
 (10 commentaires) (3 réactions) (0 assignés)C# (10 653 forks)batch import
affected-very-fewarea-networkingenhancementfeature-kestrelgood first issuehelp wantedseverity-nice-to-have

Métriques du dépôt

Stars
 (37 933 stars)
Métriques de merge PR
 (Merge moyen 16j 9h) (258 PRs mergées en 30 j)

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.

Guide contributeur