tuzig/webexec

Add daemon with multi-user support

Open

#68 opened on Sep 23, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (3 forks)auto 404
enhancementhacktoberfest

Repository metrics

Stars
 (38 stars)
PR merge metrics
 (PR metrics pending)

Description

To better support a shared dev server, we need a daemon that launches on boot and run as root.

Upon initialization, the daemon will scan all users $HOME looking for ~/.config/webexec if found, it will read the config to get the user's fingerprint (aka public key) and add it to its users list. It will use the users list for two things:

  • Accepting WHIP connection for all the users' fingerprints
  • Update peerbook with the list of users' fingerprints

Upon a SIGHUP signal to the daemon it willclear the peer list and starts the scan.

Once a connection request is received a webexec user agent will be launched and used to establish the peer connection.

Contributor guide

Research direction
Understand the existing webexec architecture, especially the user agent and peer connection setup. Then design the daemon to scan home directories for config files, parse fingerprints, and manage WHIP connections. Implement signal handling for SIGHUP to re scan. Ensure secure handling of root privileges.
Tech stack
go
Domain
backend
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.
3-5 days
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.
Mostly clear
Prerequisites
GoWebRTC basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40