Support Hidden Service Connection (kill metadata)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- haskell
- Domain
- backend, networking, security
Research direction
The issue names no files, tests, or entry points. Start by mapping how wire-server exposes and configures client connections, then determine the scope for offering Tor or I2P hidden-service connections; done would require an agreed design and implementation path rather than only a proposal.
Written by the indexing model from the issue text.
Description
Since we know that the clearnet connection based on 2 insecurities DNS&TLS, Its better to use Hidden Services like onion service or I2P service and hopefully can be supported as an option provided to the apps (specially desktop version)
- How come DNS insecure (Wikipedia provide tons of insecurities, As DNS never created to solve security issues):
https://en.wikipedia.org/wiki/Domain_Name_System#Security_issues
https://en.wikipedia.org/wiki/Domain_Name_System#Privacy_and_tracking_issues
- How come HTTPS/TLS insecure: (Thx to Moxie Marlinspike for sslstrip)
https://invidious.snopyta.org/watch?v=5dhSN9aEljg
- Last Thing that the design of a messenger over clearnet means/posses metadata trackabilities issues.
Solutions&Ideas:
-
Using Hidden services like Tor hidden services or I2P eepsite solve DNS/TLS issues (comparison between the two).
-
e.g Messengers which uses Tor/I2P:
*https://briarproject.org/ (Tor)
*https://wahay.org/ (Tor + mumble)
*https://cwtch.im/ (Tor)
*https://github.com/i2pchat/i2pchat (I2P)
- Messengers on the way to allow their servers to support hidden services:
*Matrix #7088
Useful links:
Tor Anti-DOS mechanism: https://onionbalance.readthedocs.io/en/latest/v3/tutorial-v3.html
Onion Header: https://community.torproject.org/onion-services/advanced/onion-location/
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 332
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 49
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wireapp/wire-server
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
wireapp/wire-server#5632 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
wireapp/wire-server#5443 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wireapp/wire-server#5315 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4754 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4613 ·
Maintainers usually reply within 2 days
All issues in wireapp/wire-server
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Possibly taken @renyamamoto2026-cmyk claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/phino#2107 ·
Maintainers usually reply within 1 day
-
30-minutes algorithm any-language codewars dart easy elixir hackerrank hacktoberfest haskell help wanted interview-prep julia leetcode lua open-source r scala students zig
Difficulty 2/5 Under an hour Newbie friendliness 88/100
Huerte/algo-solutions-python#124 ·