Post a reply

Username

Subject

Message body

Font colour:

Font size:

[quote="TheCliGuy"]When a session is opened to an SSH/SFTP server, the WinSCP log includes details of the encryption algorithm that's used.

The PuTTY code responsible for recording the encryption algorithm uses a human readable description. This description has no significance outside of PuTTY, consequently this makes it impossible to cross-reference it against the IANA's Secure Shell Encryption Algorithm Name registry ([url]https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-17[/url]).

Here's the code that's responsible for writing to the log:

https://git.tartarus.org/?p=simon/putty.git;a=blob;f=ssh2bpp.c;hb=2762a2025f094bf8ccb75c0bdd7c655bc953f2f1#l132

[code]
 132         bpp_logevent("Initialised %s outbound encryption",
 133                      ssh_cipher_alg(s->out.cipher)->text_name);
 134     } else {
[/code]

[code]
 190         bpp_logevent("Initialised %s inbound encryption",
 191                      ssh_cipher_alg(s->in.cipher)->text_name);
 192     } else {
[/code]

The description is held in the [i]text_name[/i] property of an initialised [i]ssh_cipheralg[/i] struct. The initialised [i]ssh_cipheralg[/i] also contains the encryption algorithm's official IANA name
in the [i]ssh2_id[/i] property.
  * ssh_cipheralg definition:     https://git.tartarus.org/?p=simon/putty.git;a=blob;f=ssh.h;hb=2762a2025f094bf8ccb75c0bdd7c655bc953f2f1#l627
  * ssh_cipheralg initialisation: https://git.tartarus.org/?p=simon/putty.git;a=blob;f=sshaes.c;hb=2762a2025f094bf8ccb75c0bdd7c655bc953f2f1#l108

Would it be possible to expose the [i]ssh2_id[/i] so it's accessible in the WinSCP .Net assembly (WinSCPnet.dll)?[/quote]

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

martin

Re: Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

2020-07-24

Thanks for your feedback.

I'll make the GUI change, if more people ask for this. Thanks for your understanding.

TheCliGuy

Re: Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

2020-07-20 17:14

Hello Martin,

Thank you for providing the development version with my suggestion implemented and for doing it so quickly.

I did reply to your email to let you know that I had tested it and it worked perfectly - but I'm not sure if you saw this.

I made one more suggestion which was to also make the ssh2_id value visible from the UI under 'Session' > 'Server/Protocol Information'.

martin

Re: Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

2020-07-15

Thanks for your suggestion.

This request has been added to the tracker:
https://winscp.net/tracker/1886

I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.

TheCliGuy

Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

2020-07-13 22:16

When a session is opened to an SSH/SFTP server, the WinSCP log includes details of the encryption algorithm that's used.

The PuTTY code responsible for recording the encryption algorithm uses a human readable description. This description has no significance outside of PuTTY, consequently this makes it impossible to cross-reference it against the IANA's Secure Shell Encryption Algorithm Name registry (https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-17).

Here's the code that's responsible for writing to the log:

https://git.tartarus.org/?p=simon/putty.git;a=blob;f=ssh2bpp.c;hb=2762a2025f094bf8ccb75c0bdd7c655bc953f2f1#l132

 132         bpp_logevent("Initialised %s outbound encryption",

 133                      ssh_cipher_alg(s->out.cipher)->text_name);

 134     } else {

 190         bpp_logevent("Initialised %s inbound encryption",

 191                      ssh_cipher_alg(s->in.cipher)->text_name);

 192     } else {

The description is held in the text_name property of an initialised ssh_cipheralg struct. The initialised ssh_cipheralg also contains the encryption algorithm's official IANA name
in the ssh2_id property.
* ssh_cipheralg definition: https://git.tartarus.org/?p=simon/putty.git;a=blob;f=ssh.h;hb=2762a2025f094bf8ccb75c0bdd7c655bc953f2f1#l627
* ssh_cipheralg initialisation: https://git.tartarus.org/?p=simon/putty.git;a=blob;f=sshaes.c;hb=2762a2025f094bf8ccb75c0bdd7c655bc953f2f1#l108

Would it be possible to expose the ssh2_id so it's accessible in the WinSCP .Net assembly (WinSCPnet.dll)?

Post a reply

Topic review

Re: Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

Re: Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

Re: Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

Make Encryption Algorithm's ssh2_id Property Accessible in .NET Assembly

Documentation

Support

Associations

Follow Us