darkoperator
cipher name aes256-ctr for openssh key file is not supported
I don't know why I keep getting this error but it's incredibly annoying.
I'm trying to transfer a file. When I use "scp" I can specify user@host:"file" and it just works.
With get-scpitem, I need to specify other stuff that requires additional parameters and it just makes the whole thing cumbersome.
I need to specify a keyfile? Why? I don't do that with scp, why do I do that with get-scpitem?
I need to specify a password? Why?
When I do specify these things, I get the "key file is not supported" message. Is it because I specified them?
Do I now have to tediously generate a new key and update every single system so the new key will be accepted? Or is there a problem with my key?
There's a chance it won't even work if I update the key, so it's just extra work with no guaranteed payoff, and I might screw something up so that scp won't work either.
Is the key too secure? Is that the issue? Do I need to use a weaker key with potential vulnerabilities? Is that what it wants me to do?
I don't know the difference between the key it wants, and the key I have, but it's probably not something I want to mess with.
I'm not a cryptographer.
Can you share what commands with what parameter combination are you running and also the full output so I can try to replicate and figure out why are you getting that error. My guess it is the target host key but need a bit more info to test and be sureSent from my iPhoneOn Feb 17, 2023, at 11:27 PM, JavAstrologic @.> wrote: I don't know why I keep getting this error but it's incredibly annoying. I'm trying to transfer a file. When I use "scp" I can specify @.:"file" and it just works. With get-scpitem, I need to specify other stuff that requires additional parameters and it just makes the whole thing cumbersome. I need to specify a keyfile? Why? I don't do that with scp, why do I do that with get-scpitem? I need to specify a password? Why? When I do specify these things, I get the "key file is not supported" message. Is it because I specified them? Do I now have to tediously generate a new key and update every single system so the new key will be accepted? Or is there a problem with my key? There's a chance it won't even work if I update the key, so it's just extra work with no guaranteed payoff, and I might screw something up so that scp won't work either. Is the key too secure? Is that the issue? Do I need to use a weaker key with potential vulnerabilities? Is that what it wants me to do? I don't know the difference between the key it wants, and the key I have, but it's probably not something I want to mess with. I'm not a cryptographer.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
