Secure Bridge 9.2 inner Exception lost

[Marek-2]

I am trying to use atPublicKey authentication in SFtp component.
It works fine.
I have tested what happens if the key is corrupt (simply edited the key).
I get an exception on TScSFTPClient.Initialize() method - it is right.
The exception message is: "An error occurred when signing data: %s"
I saw in the debugger that another exception appears first: "Invalid PCKS1 padding, data is currupt".
This exception is lost.
It would be nice to see:
"An error occurred when signing data: Invalid PCKS1 padding, data is currupt ".

[ViktorV]

From the security perspective, the behavior is correct. We're not planning to change it, though you may purchase the SecureBridge Professional with source code and implement the needed functionality yourself.