Actions in the SAS® Studio interface regarding a connection to Git with Secure Shell (SSH) return the following pop-up error:
SSH authentication failure. The specified URL or Public SSH key is invalid for remote repository.
The corresponding Git function also returns a message similar to the following in the log:
ERROR: return code from GIT is (23). ERROR: You're using an RSA key with SHA-1, which is no client or a different key type.
Here are other possible errors:
ERROR: Return code from GIT is (23). ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
RC=23
SSH authentication failure: The specified Private key could not be opened.
This problem occurs because GitHub dropped support for SHA-1 keys on March 15, 2022. Any SSH key that was generated after November 2, 2021 does not work with SAS Studio.
You encounter the following error if you attempt to clone a repository with the ed25519 algorithm:
ERROR: Failed to authenticate with the remote repository.
See SAS Note 69932 for information about support of the ed25519 keygen algorithm.
For more information, see the following GitHub blog: Improving Git protocol security on GitHub.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Customers who run SAS® Studio 5.2 must install the hot fix to address this issue.
After you apply the hot fix in this note, updated libraries are available for use. After these libraries are installed, you can use the following ssh-keygen command to generate SSH keys. In this command, replace your_email@example.com with your email address:
ssh-keygen -t ecdsa -b 521 -C "your_email@example.com"
Note: This issue is fixed in SAS® Studio 2021.2.6 (Stable) and SAS® Studio Long-Term Support 2022.09.
Operating System and Release Information
SAS System | SAS Studio | Microsoft® Windows® for x64 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8 Enterprise 32-bit | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8 Enterprise x64 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8 Pro 32-bit | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8 Pro x64 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Enterprise 32-bit | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Enterprise x64 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Pro 32-bit | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Pro x64 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows 10 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2008 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2008 R2 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2008 for x64 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 Datacenter | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 R2 Datacenter | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 R2 Std | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 Std | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2016 | 3.8 | | 9.4 TS1M6 | |
Microsoft Windows Server 2019 | 3.8 | | 9.4 TS1M6 | |
Windows 7 Enterprise 32 bit | 3.8 | | 9.4 TS1M6 | |
Windows 7 Enterprise x64 | 3.8 | | 9.4 TS1M6 | |
Windows 7 Home Premium 32 bit | 3.8 | | 9.4 TS1M6 | |
Windows 7 Home Premium x64 | 3.8 | | 9.4 TS1M6 | |
Windows 7 Professional 32 bit | 3.8 | | 9.4 TS1M6 | |
Windows 7 Professional x64 | 3.8 | | 9.4 TS1M6 | |
Windows 7 Ultimate 32 bit | 3.8 | | 9.4 TS1M6 | |
Windows 7 Ultimate x64 | 3.8 | | 9.4 TS1M6 | |
64-bit Enabled AIX | 3.8 | | 9.4 TS1M6 | |
64-bit Enabled Solaris | 3.8 | | 9.4 TS1M6 | |
HP-UX IPF | 3.8 | | 9.4 TS1M6 | |
Linux for x64 | 3.8 | | 9.4 TS1M6 | |
Solaris for x64 | 3.8 | | 9.4 TS1M6 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.