summaryrefslogtreecommitdiffstats
path: root/krfb/TODO
diff options
context:
space:
mode:
authortoma <toma@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2009-11-25 17:56:58 +0000
committertoma <toma@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2009-11-25 17:56:58 +0000
commitbcb704366cb5e333a626c18c308c7e0448a8e69f (patch)
treef0d6ab7d78ecdd9207cf46536376b44b91a1ca71 /krfb/TODO
downloadtdenetwork-bcb704366cb5e333a626c18c308c7e0448a8e69f.tar.gz
tdenetwork-bcb704366cb5e333a626c18c308c7e0448a8e69f.zip
Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.
BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdenetwork@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Diffstat (limited to 'krfb/TODO')
-rw-r--r--krfb/TODO28
1 files changed, 28 insertions, 0 deletions
diff --git a/krfb/TODO b/krfb/TODO
new file mode 100644
index 00000000..1258e590
--- /dev/null
+++ b/krfb/TODO
@@ -0,0 +1,28 @@
+
+For 3.2:
+- write SLP service template for remote desktop protocols
+ (documentation)
+- enhance RFB with SASL authentication (Kerberos)
+- encrypted connections (using SASL and/or SSL/TLS)
+- with kerberos/ssl: display name of remote user in connection dialog,
+ kpassivepopup and systray (if name is available)
+- mention that invitations are one-time on personal invitation dialog
+
+Todo (unscheduled features):
+- when krfb is started with URL arguments and without connection
+ quality, add some kind of smart algorithm to determine whether the
+ other host is local (maybe using SLP to announce the connectivity
+ of a LAN)
+- NAT traversal support if I can find an acceptable implementation
+ (probably using TURN, as soon as there is a server and newer spec for that)
+- when OpenSLP supports this, allow scope configuration
+- split krfb into 2 separate programs (server and invitation)
+- look into adding an extension to xfree to improve speed (get noticed of
+ screen updates)
+- cut & paste support
+
+Known bugs/problems:
+- the IP address sent in invitation may be wrong on multi-homed machines,
+ and it is always incorrect behind a NAT. Right now it is not possible
+ to solve these problems.
+