Exceptions thrown on TScSSHClient::Connect

Discussion of open issues, suggestions and bugs regarding network security and data protection solution - SecureBridge
Post Reply
RDTelecom
Posts: 14
Joined: Mon 26 Aug 2013 13:52

Exceptions thrown on TScSSHClient::Connect

Post by RDTelecom » Fri 18 Jul 2014 13:37

Hello,

As I understand the unique way to know what went wrong when connecting from the SSH client is to catch exceptions thrown. The information is stored as an English string in the Message property.

What is the list of possible exceptions thrown ? (looks like it is only an Exception based class so not a derived class that would had some customization).

My need would be to have more specific information when authentication fails than just the "Authentication failed" string. Our SSH server validates the user with a third party (a Radius server) and we'd like to give more feedback to the user on why it failed (such as Radius server unreachable, ).

That might be a restriction of the implementation of the SSH protocol, which I would understand, but I would like to be sure.

PS: password authentication is used for connecting.

ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Exceptions thrown on TScSSHClient::Connect

Post by ViktorV » Wed 30 Jul 2014 07:36

Thank you for your advice.
Currently, TScSSHClient doesn't provide such functionality, but we will support it in the next SecureBridge build.

RDTelecom
Posts: 14
Joined: Mon 26 Aug 2013 13:52

Re: Exceptions thrown on TScSSHClient::Connect

Post by RDTelecom » Fri 01 Aug 2014 12:34

As described in this topic http://forums.devart.com/viewtopic.php?f=27&t=30043
it is the Authentication Response frame that needs to be accessible.

Post Reply