ElectronNET/Electron.NET

Security considerations

Open

#22 opened on Oct 29, 2017

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

Repository metrics

Stars
 (7,040 stars)
PR merge metrics
 (Avg merge 4d 13h) (7 merged PRs in 30d)

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

Research direction
Investigate alternatives to running a plain web server on localhost for security, such as using a named pipe or Unix socket, and evaluate the impact on Electron.NET's architecture.
Tech stack
csharp
Domain
backend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30