cwtch and Tor : how many hops + path hops UI #189
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#189
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, i'd like to know whether cwtch works the same way .onion sites in Tor, i.e. 3 hops having their IP address visible, then 3 relays before reaching the .onion destination, without their IP visible, or does cwtch work differently ?
Would be nice to be able to see the path cwtch fetches, as is possible on the Torbrowser. Is this on the roadmap ?
Yes, Cwtch uses the same 6-hop onion routing as Tor, with the client making 3 hops (the 3rd hop being the rendevous point), and the server making 3 hops and then making a final connection to the rendevous point.
Yes (see also: #85)
nice. Can we expect that in the 1.13 version or is it further off the road (on your link it was supposed to be added to the 1.12 beta) ?
It was pushed back as we realized it required a couple of new changes further down the stack and it wasn't as high on the priority list as some other features. Roughly I would expect it in 1.5 or 1.6 - maybe sooner.
ok. Fair enough.