transmission/transmission

daemon: native TLS for RPC

Open

#777 opened on Dec 9, 2018

View on GitHub
 (4 comments) (3 reactions) (0 assignees)C++ (1,154 forks)batch import
help wantedpr welcomescope:coretype:feat

Repository metrics

Stars
 (10,996 stars)
PR merge metrics
 (Avg merge 11d 14h) (30 merged PRs in 30d)

Description

Currently, the RPC communication is via cleartext HTTP. For confidentiality, integrity and authenticity, supporting Transport Layer Security (TLS) would be awesome. Currently, some users do this via a reverse proxy like lighttpd. Native support for this would be awesome, because it's cleaner, more accessible and using less ressources.

Contributor guide

Research direction
Examine the current HTTP based RPC implementation and design integration of TLS using a library like OpenSSL or GnuTLS. Consider configuration options for certificates and compatibility with existing reverse proxy setups.
Tech stack
cpp
Domain
backendnetworkingsecurity
Issue type
Feature
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.
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.
Clear
Prerequisites
C++TLSNetworking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30