Bug 3059 - remove unencrypted mode
Summary: remove unencrypted mode
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: 2.1.0
Hardware: PC All
: P2 Enhancement
Target Milestone: 4.3.0
Assignee: Pierre Ossman
Keywords: astrand_tester, relnotes
Depends on:
Reported: 2009-04-01 12:36 CEST by Pierre Ossman
Modified: 2014-10-28 13:41 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2009-04-01 12:36:45 CEST
Our "unencrypted" mode means that we let the VNC traffic go outside the SSH tunnel, directly to the server. This feature should be removed as it is rather unintuitive (it breaks the principle of using just port 22 and the GUI suggests that we just tell SSH to not encrypt the data), it's insecure (of course) and I doubt anyone actually uses it.

The only reason to keep it around is for performance, but SSH is not that much of a bottle neck in most cases.
Comment 1 Pierre Ossman cendio 2014-08-20 13:34:55 CEST
Fixed in r29276 and r29277.

Tester should check that there is nothing left in the code or documentation for the unencrypted mode.
Comment 2 Peter Åstrand cendio 2014-09-22 12:55:14 CEST
Still in the usage message:

tlclient_tlclient.cc:                 "                                  - sshcrypt: ssh encryption\n"
Comment 3 Pierre Ossman cendio 2014-09-22 14:40:21 CEST
(In reply to comment #2)
> Still in the usage message:
> tlclient_tlclient.cc:                 "                                  -
> sshcrypt: ssh encryption\n"

Comment 4 Peter Åstrand cendio 2014-09-22 14:54:29 CEST
Ok now.
Comment 5 Henrik Andersson cendio 2014-10-23 15:18:28 CEST
There are still stuff in TAG referencing unencrypted connections see image @

Comment 6 Pierre Ossman cendio 2014-10-23 15:50:48 CEST
The options screen shot is also wrong.
Comment 7 Pierre Ossman cendio 2014-10-23 16:00:19 CEST
Images updated in r29535.
Comment 8 Peter Åstrand cendio 2014-10-28 13:41:57 CET
Fine now.

Note You need to log in before you can comment on or make changes to this bug.