Score:0

How to get Cipher details from .ppk file

cn flag
404

Is it possible to get the Cipher name from .ppk file? For e.g. name like TLS-CHACHA20-POLY1305-SHA256 or ECDHE-ECDSA-AES256-GCM-SHA384

Edit: Based on the responses in answers and comments, it seems I posted an invalid query here. Apologies, I am a newbie so was not aware about the concepts.

John Hanley avatar
cn flag
You are confusing a large binary number that is stored in the PPK and the software which implements algorithms that use the number. The PPK does not contain algorithms. Those are implemented in software. The number can be used with algorithms that do not even exist today.
Score:1
se flag

A PPK file is a key file. There is no cipher like the one you've specified inside it - specifically since you specified TLS ciphers which are different from SSH ciphers. So there is no such cipher to get from the PPK file.

cn flag
404
Thanks Steffen. So which file would contain cipher details? To add context, we are to check the below "To ensure that connections to *.concursolutions.com and * api.concursolutions.com are not disrupted, clients and partners who connect to *.concursolutions.com and * api.concursolutions.com through an application that uses an unsupported cipher must update the application to a supported cipher ". We are connecting using SFTP
Steffen Ullrich avatar
se flag
@404: Ciphers are negotiated, i.e. there is no fixed cipher. Assuming that you are using Putty (hence PPK files) see [here](https://documentation.help/PuTTY/config-ssh-encryption.html) on how the ciphers are configured. Note though that the kind of ciphers you mention in the question are TLS ciphers (i.e. for HTTPS in browsers), not SSH/SFTP ciphers.
jp flag
@SteffenUllrich I suspect that these cyphers names (TLS-CHACHA20-POLY1305-SHA256 and ECDHE-ECDSA-AES256-GCM-SHA384) correspond to [email protected] and [email protected].
Steffen Ullrich avatar
se flag
@AlexD: SSH distinguishes between Ciphers (symmetric encryption), Key Exchange Algorithms and Key Algorithms. TLS packs everything together into a cipher string (TLS 1.3 moved key algorithms out of the cipher string). So for me it is not really clear what the OP is asking. My current guess is that somebody gave the OP TLS related instructions with the order to make sure that everything is configured securely and now the OP is trying to apply this to SSH/SFTP w/o having any idea that these are actually different things.
Score:1
jp flag

According to the following PPK format description you can find SSH algorithm encoded as a string with key algorithm-name and the key encryption algorithm as a string encryption-type.

cn flag
404
Thanks AlexD, yes but it only shows ssh-rsa and not the Cipher name
jp flag
I suspect that you are talking about connection cyphers. They are negotiated when a connection is established between a ssh client and a ssh server. They are independent of the key encryption.
cn flag
404
Sorry I am a newbie here. So when we connect to SFTP via SSH certificate, the cipher is not involved? We have one SFTP server where we connect via Public Key/Private key handshake and Essentially we are asked to check this - "To ensure that connections to *.concursolutions.com and * api.concursolutions.com are not disrupted, clients and partners who connect to *.concursolutions.com and * api.concursolutions.com through an application that uses an unsupported cipher must update the application to a supported cipher"
jp flag
When you connect to an SFTP server SSH keys are used for authentication and cyphers are used for encryption. You just need to make sure that you are using an up to date client to connect to your SFTP server and that this client supports at least some cyphers supported by the server. You probably want to open another question with the details of your client software and SFTP server software.
cn flag
404
Thanks, can you update this as an answer so that i can mark it as an answer.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.