4/1/2023 0 Comments Git config ssh proxy![]() Sudo touch /home/azure/.ssh/authorized_keys ![]() Sudo runuser -u azure - ssh -v Ĭheck for " debug1: Authentication succeeded (publickey)."įollowup error(s) like " shell request failed on channel 0" are fine.Īllow Lagoon access to the azure user. !! Add the private key from your Azure account to: ` /home/azure/.ssh/id_azure` This will enable the less secure algorithm required for Azure. !! Enable PubkeyAcceptedAlgorithms / HostkeyAlgorithms if you run OpenSSH >=8.8 (use ` ssh -V` to check version) Sudo echo "IdentityFile /home/azure/.ssh/id_azure" > /home/azure/.ssh/config Sudo echo "User git" > /home/azure/.ssh/config Sudo echo "#HostkeyAlgorithms +ssh-rsa" > /home/azure/.ssh/config Sudo echo "#PubkeyAcceptedAlgorithms +ssh-rsa" > /home/azure/.ssh/config Sudo echo "HostkeyAlgorithms +ssh-rsa" > /home/azure/.ssh/config Sudo echo "Host " > /home/azure/.ssh/config It is assumed that you already have a key-pair for the Azure account you'd like to use to access Azure git.Ĭreating Azure User: sudo useradd -m azure In following scenario we used the username azure. You need to create a dedicated a proxy user on a server where you've full control over the ssh service. ![]() The SSH proxy will accept connections from Open SSH >=8.8 systems and forward them to azure using a less secure algorithm that keeps Azure happy. Now if you don't have full access to whatever system runs Open SSH >=8.8 you're between a rock and a hard place.Īzure isn't likely to move, but why should the other party move and enable less secure algorithms?įor us the only alternative to get a quick solution was to configure a dedicated SSH proxy on one of our existing servers. More inforamtion about the lack of SHA-2 in Azure Git: Currently Microsoft Azure Git seems to lack support for SHA-2.Īnd as of Open SSH 8.8 support for less secure algorithms have has been disabled by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |