Why Does CircleCI Show \'Agent Key Returned Incorrect Signature Type\' and \'No Tracking Information\' Errors?

Incorrect Signature Type Error in CircleCI

The "agent key returned incorrect signature type" error in CircleCI's default Go template stems from the discrepancy between the expected and provided SSH signature algorithms.

SHA-1 vs. Stronger Hash Algorithms

RSA SSH keys can sign using various hash algorithms, including SHA-1, SHA-256, and SHA-512. The error occurs when a connection negotiates using SHA-256 or SHA-512, but the agent provides an SHA-1 signature. This violates the SSH protocol.

Non-Fatal Error

While not inherently fatal, the error may cause the remote side to reject the connection if it does not support SHA-1 signatures.

Git Merge Request Error

The second error, "There is no tracking information for the current branch," indicates that a git pull command is being executed without an established remote for the branch. This typically occurs when using Go get with an existing repository.

Solutions

• Incorrect Signature Error:

  • Check the SSH agent configuration to ensure it supports the expected hash algorithm.
  • Consider ignoring the warning if it does not cause connection issues.

• Git Merge Request Error:

  • Set up a remote for the branch by running git branch --set-upstream-to=origin/ develop.
  • Alternatively, use git build instead of git get to install dependencies automatically.

The above is the detailed content of Why Does CircleCI Show \'Agent Key Returned Incorrect Signature Type\' and \'No Tracking Information\' Errors?. For more information, please follow other related articles on the PHP Chinese website!