curve25519 | C # .NET Port of the Curve25519 Diffie-Hellman function

I'm working with Homestead and vagrant on my local setup. My Homestead.yaml file looks like this:

I have two ubuntu aws instance and below are following details

1. DevServer: 172.31.29.201
2. QAServer: 172.31.30.52

I establish a passwordless SSH between two machine bu generating ssh-keygen in DevServer and copied it to QAServer using ssh-copy-id ubuntu@172.31.30.52 [ubuntu is username and 172.31.30.52 is private ip address of the QAServer)

I'm able to successfully make a SSH connection to the QAServer from DevServer without any issue

Even scp command to transfer the .war file to the QAServer tomcat8/webapps is successful. File qaapp.war is transferred to the tomcat8/webapps/ folder

I have a playbook that is launched from AWX with machine credentials, ie. with ssh_user_A. In this playbook, i need to perform a couple of tasks with another SSH user, ie. ssh_user_B.

In terms of credentials, I have:

• machine credentials for ssh_user_A that are OK, I can do whatever I need
• a public/private keys couple for ssh_user_B:
  • the public key is present on the remote host in the ~ssh_user_B/.ssh/authorized_keys file
  • if I test this public/private key with a temp machine credentials (not possible in final target) and a dummy playbook or an ad-hoc module call, it works I can do whatever I need

I change the SSH user in the playbook with these instructions:

I have ec2 instance with ubuntu v20.04 and it has python v3.8.10 and pysftp 0.2.9.

I have generate .pem file from .ppk file using below command

puttygen sftp_server.ppk -O private-openssh -o sftp_server.pem

I am able to connect successfully to sftp server using command line-

I have a Python 3 application running on CentOS Linux 7.7 executing SSH commands against remote hosts. It works properly but today I encountered an odd error executing a command against a "new" remote server (server based on RHEL 6.10):

encountered RSA key, expected OPENSSH key

Executing the same command from the system shell (using the same private key of course) works perfectly fine.

On the remote server I discovered in /var/log/secure that when SSH connection and commands are issued from the source server with Python (using Paramiko) sshd complains about unsupported public key algorithm:

userauth_pubkey: unsupported public key algorithm: rsa-sha2-512

Note that target servers with higher RHEL/CentOS like 7.x don't encounter the issue.

It seems like Paramiko picks/offers the wrong algorithm when negotiating with the remote server when on the contrary SSH shell performs the negotiation properly in the context of this "old" target server. How to get the Python program to work as expected?

Python code

I am trying to write a bash script that runs ssh command with debug (ssh -vvv) against a specified host/hosts. I am not trying to login to the server, but rather just trying to see what all kex, mac and ciphers does the server offer.

I did create a script to find the kex algos after negotiation using the -G option.

I've been using ssh keys with github for a while now. Suddenly i can't push and I'm getting a Permission denied (publickey) error. Here's what I've tried so far:

• Checked the ssh key is in the correct directory (~/.ssh)
• Tried reuploading my public key to github (I get a message that the key already exists)
• Double checked that the output of ssh-add -l -E sha256 on my system agrees with the string in my ssh settings on my github account
• Followed all the steps in the "Troubleshooting ssh" section of the github docs. (Everything seems gucci)
• Banged my head against the wall for an hour

So far nothing has helped. This is my last resort. I'll greatly appreciate any and all suggestions. Here's the output of my ssh -vT git@github.com

I've created Azure VM using Terraform:

I am trying to use pip install git+ssh://git@bitbucket.org/my_org/my_package_repo.git to install a custom-made python package (shared by multiple applications) from BitBucket WITHOUT having to enter the SSH password.

There seems to be a lot of good information in one of the answers to this question for doing this in GitLab, etc. There's also some solid supporting information here.

I've already setup an SSH key between my local Mac and this BitBucket account. I'm able to push/pull code all the time to/from this account without having to re-enter the SSH password. Why is the pip install command requiring the password, when it's not required by git commands? Is there a way around this with BitBucket and the setup I've described?

When I run the GIT_SSH_COMMAND='ssh -vvv' pip install git+ssh://git@bitbucket.org/my_org/my_package_repo.git command recommended in the comments, I get the following (sanitized) response: