Posh-SSH
Posh-SSH copied to clipboard
No authentication with POSH-SSH
Hi,
I've used POSH-SSH several times successfully, but I have a problem with this Qnap-NAS. With New-SshSession
I get a (Renci.SshNet.SshClient: SshClient) [New-SSHSession], SshAuthenticationException
. The connection works for the same target with identical credential via Putty and Windows Open-SSH. What is the difference in POSH-SSH? Does anyone have any advice?
Regards, DA
Limited ciphers, the Posh-SSH is a separate implementation and not a port of OpenSSH like the windows built in ssh client. I would check that host key and what key ciphers are in use.
On May 14, 2021, at 5:35 PM, DrillAble @.***> wrote:
Hi, I've used POSH-SSH several times successfully, but I have a problem with this Qnap-NAS. With New-SshSession I get a (Renci.SshNet.SshClient: SshClient) [New-SSHSession], SshAuthenticationException. The connection works for the same target with identical credential via Putty and Windows Open-SSH. What is the difference in POSH-SSH? Does anyone have any advice? Regards, DA
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/395, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7IHQTDMBD4WEOPN635OTTNWJQZANCNFSM445EIYYQ.
Thanks for the immediate feedback. I had to read a little first, but I can't say that I get it. The first supported client-to-server cipher is AES256-CTR and the RSA key fingerprint is an SHA256. Is there any way to get posh-ssh to connect under these conditions? By the way, the ssh trused host is entered.
what module version you use?
Get-PoshSSHModVersion returns 2.3.0
Can you try the beta?
Sent from my iPhone
On May 17, 2021, at 12:06 PM, DrillAble @.***> wrote:
Get-PoshSSHModVersion returns 2.3.0
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
@darkoperator may be it's time for beta2 ?
Beta 3 :P yep will push it out today
On May 17, 2021, at 3:42 PM, Max Kozlov @.***> wrote:
@darkoperator https://github.com/darkoperator may be it's time for beta2 ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/395#issuecomment-842582766, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7IHVPUKK4LQV7BUOEZULTOFWRRANCNFSM445EIYYQ.
Beta2 was just pushed out to the gallery
On May 17, 2021, at 3:54 PM, Carlos Perez @.***> wrote:
Beta 3 :P yep will push it out today
On May 17, 2021, at 3:42 PM, Max Kozlov @.*** @.***>> wrote:
@darkoperator https://github.com/darkoperator may be it's time for beta2 ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/395#issuecomment-842582766, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7IHVPUKK4LQV7BUOEZULTOFWRRANCNFSM445EIYYQ.
Sorry for the long delay. I asked QNAP about the topic. They told me that they do not yet support POSH-SSH. I don't understand the specifics of SSH that need to be supported, but the beta version hasn't changed either. However, a test after the last update of the QNAP system a few days ago was successful. The next thing to clarify is how to issue multiple commands in the same context to use virsh.
Regards, DA
You will need a stream shell, the write command in to the stream and red output, you will also need to monitor when no more output is present
Sent from my iPhone
On Jul 3, 2021, at 4:29 AM, DrillAble @.***> wrote:
Sorry for the long delay. I asked QNAP about the topic. They told me that they do not yet support POSH-SSH. I don't understand the specifics of SSH that need to be supported, but the beta version hasn't changed either. However, a test after the last update of the QNAP system a few days ago was successful. The next thing to clarify is how to issue multiple commands in the same context to use virsh.
Regards, DA
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.