ElectronNET/Electron.NET

Security considerations

Open

#22 opened on Oct 29, 2017

View on GitHub
 (33 comments) (1 reaction) (0 assignees)C# (7,040 stars) (710 forks)batch import
help wantedquestion

Description

Twitter discussion - currently we launch a plain webserver on localhost. Maybe we could avoid to launch a "real" webserver at all, see here:

https://twitter.com/robert0muehsig/status/924741177525587968

Contributor guide

Tech stack
csharp
Domain
security
Issue type
security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
ASP.NET Core basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue references a Twitter discussion about security of launching a localhost webserver. Consider researching alternative approaches to avoid running a full webserver, such as using IPC or named pipes. Look at Electron.NET's current implementation of the server startup in the codebase (e.g., ElectronNET.Host or startup files). Engage with the maintainers to clarify the acceptable solution scope.