ssh-key was expected to be base64-encoded (base64 --decode), which is inconsistent with ssh-upload and ssh-command, both of which take the raw PEM key directly via env:/printf. Storing the secret in a different encoding per-action is easy to get wrong and silently produces a corrupt/unusable key file if the value isn't actually base64.
Fix
Write $SSH_KEY straight to ~/.ssh/gitea_key instead of piping through base64 --decode.
Action required
Any secret feeding ssh-key into this action needs to be the raw PEM private key (no base64 encoding) going forward — same format as ssh-upload's private_key / ssh-command's private_key.
## Problem
`ssh-key` was expected to be base64-encoded (`base64 --decode`), which is inconsistent with `ssh-upload` and `ssh-command`, both of which take the raw PEM key directly via `env:`/`printf`. Storing the secret in a different encoding per-action is easy to get wrong and silently produces a corrupt/unusable key file if the value isn't actually base64.
## Fix
Write `$SSH_KEY` straight to `~/.ssh/gitea_key` instead of piping through `base64 --decode`.
## Action required
Any secret feeding `ssh-key` into this action needs to be the raw PEM private key (no base64 encoding) going forward — same format as `ssh-upload`'s `private_key` / `ssh-command`'s `private_key`.
ssh-key was expected to be base64-encoded and decoded with
`base64 --decode`, which is inconsistent with ssh-upload and
ssh-command (both take the raw PEM directly) and an easy way to end
up with a silently corrupt key file if the stored secret isn't
actually base64. Write the input straight to the key file instead.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
ssh-keywas expected to be base64-encoded (base64 --decode), which is inconsistent withssh-uploadandssh-command, both of which take the raw PEM key directly viaenv:/printf. Storing the secret in a different encoding per-action is easy to get wrong and silently produces a corrupt/unusable key file if the value isn't actually base64.Fix
Write
$SSH_KEYstraight to~/.ssh/gitea_keyinstead of piping throughbase64 --decode.Action required
Any secret feeding
ssh-keyinto this action needs to be the raw PEM private key (no base64 encoding) going forward — same format asssh-upload'sprivate_key/ssh-command'sprivate_key.