Bug 4674 - Better report of connection failure when portforwarding is disabled/restricted
Summary: Better report of connection failure when portforwarding is disabled/restricted
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-03 08:29 CEST by Henrik Andersson
Modified: 2022-12-06 13:15 CET (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Henrik Andersson cendio 2013-06-03 08:29:16 CEST 
As an example, if using portforward restrictions (#4591) while connecting and forwarding of port is restricted the only message the client is presented is that the session only lived less then 10 seconds and nothing related to the access deny.

When looking in client log file there is a line following line which we should trigg upon to present a more decent message for the end user.

'ssh[E]: channel 2: open failed: administratively prohibited: open failed'

This problem is also trigged if someone installs ThinLinc server on a system wich is configured to no allow portforward, and on some systems this is also the defaults.
Note You need to log in before you can comment on or make changes to this bug.