Harden gh actions#198
Conversation
Signed-off-by: Fabian Kammel <fabian@kammel.dev>
Signed-off-by: Fabian Kammel <fabian@kammel.dev>
Signed-off-by: Fabian Kammel <fabian@kammel.dev>
…ing attacks Signed-off-by: Fabian Kammel <fabian@kammel.dev>
EthanHeilman
left a comment
There was a problem hiding this comment.
LGTM - This is really great
Please do |
|
@datosh This appears to have broken something https://github.com/openpubkey/opkssh/actions/runs/15089597609/job/42416411626 |
|
That's odd - I pulled the changes into my fork and it builds just fine on Also the test I did prior to sending the PR was green: https://github.com/datosh/opkssh/actions/runs/15084082929 Could you rerun the pipeline to see if the action itself might be flaky? edit: This might be another instance of #184 - same exact error message! |
|
@datosh You are right, it has nothing to do with your change. This error seems to occur whenever we make a change to GHA and then merge to main, rerunning makes it go away. |
I had some fun comparing GHA security scanners and needed a victim / beneficiary 😉
I used zizmore, poutine, octoscan and github-actions-scanner.
In the end - all the changes I made were based on findings from zizmore. Here are the specific issues I fixed:
They support running the checks in GHA, which might be a nice addition, if you end up agreeing with the changes.
Additionally, I would suggest that we add either dependabot or renovate to get version upgrade for GHA - as the versions are now pinned - might be nice for Go as well. Happy to create follow-up issues if you like the direction.
I did run each action in my fork using
workflow_dispatchto verify they still work: