LBRYcrd using old onion v2
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
https://support.torproject.org/onionservices/v2-deprecation/
https://en.wikipedia.org/wiki/.onion
```
2022-08-24T13:21:32Z Socks5() connect to 4rv64pye46egezf6.onion:9246 failed: general failure
2022-08-24T13:21:36Z Socks5() connect to 25gsdyotikiihbb7.onion:9246 failed: general failure
2022-08-24T13:21:40Z Socks5() connect to 25gsdyotikiihbb7.onion:9246 failed: general failure
2022-08-24T13:21:43Z Socks5() connect to 25gsdyotikiihbb7.onion:9246 failed: general failure
2022-08-24T13:21:47Z Socks5() connect to 4rv64pye46egezf6.onion:9246 failed: general failure
2022-08-24T13:21:50Z Socks5() connect to 25gsdyotikiihbb7.onion:9246 failed: general failure
2022-08-24T13:21:55Z Socks5() connect to 25gsdyotikiihbb7.onion:9246 failed: general failure
2022-08-24T13:21:58Z Socks5() connect to 25gsdyotikiihbb7.onion:9246 failed: general failure
2022-08-24T13:22:01Z Socks5() connect to 4rv64pye46egezf6.onion:9246 failed: general failure
```
Contributor guide
Research direction
Start with the Tor v2 deprecation link and the recorded Socks5 failures to locate how LBRYcrd handles .onion peer addresses. No source file or test is named, so trace the relevant networking entry point and determine how current onion addresses should be supported. Done should mean these deprecated-address connection failures are addressed and covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100