https://bugs.kde.org/show_bug.cgi?id=471994
Bug ID: 471994
Summary: Support hidden services from TOR (.onion) or I2P to
allow connections between devices in different
networks
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Other
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: fisc...@unix-ag.uni-kl.de
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
If a mobile device running KDE Connect and the corresponding desktop are
located in different network subnets (e.g. mobile network and an organization's
firewalled LAN, respectively) and the distance in between is too large for
Bluetooth, communication between both endpoints may be impossible unless manual
steps like establishing a VPN first are taken.
My proposal is that all KDE Connect instances (mobile and desktop apps) have
either TOR or I2P or both built-in, so that both endpoints have a better chance
of communicating with each other if other means fail.
Using either hidden service comes at the cost of additional latency and limited
bandwidth, so it should only be a fallback if 'normal' network and Bluetooth
are not available.
To avoid security/trust issues and to not bother the user with technical
questions, two endpoints should automatically exchange public keys and hashes
when connected the first time via WiFi or Bluetooth, and make use of those
credentials for future connections via hidden services if the need arises.
The use of hidden services should be both compile-time configurable (if
packages do not want to have this feature included) and run-time configurable
(if users want to avoid generating traffic that may look suspicious to network
security).
--
You are receiving this mail because:
You are watching all bug changes.
