Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security issue #30

Open
eine opened this issue Nov 13, 2020 · 8 comments
Open

Security issue #30

eine opened this issue Nov 13, 2020 · 8 comments

Comments

@eine
Copy link

eine commented Nov 13, 2020

Coming from docker/build-push-action#53

Refs:

Behaviour

docker/build-push-action#53 (comment)
It seems that the warning message is hidden from the users, which is misleading as it provides a false feeling of security. As seen in docker/login-action@adb7347/src/docker.ts#L36, on success stderr is not shown. The warning is precisely shown when the login is successful but insecure.

Steps to reproduce this issue

docker/build-push-action#53 (comment)
See eine/login-action@master (commits) and eine/login-action/runs/1354438643?check_suite_focus=true#step:3:8.

Expected behaviour

Login is secure or security warnings are not hidden.

Actual behaviour

Login is reported not to be secure, but warnings are hidden.

@crazy-max crazy-max transferred this issue from docker/build-push-action Nov 13, 2020
@crazy-max
Copy link
Member

crazy-max commented Nov 13, 2020

@eine

It seems that the warning message is hidden from the users, which is misleading as it provides a false feeling of security. As seen in adb7347/src/docker.ts#L36, on success stderr is not shown. The warning is precisely shown when the login is successful but insecure.

This issue concerns the credential store used on the GitHub Runner and not this action itself. Also as you can see on your own fork, credentials are removed when the job is finished.

@eine
Copy link
Author

eine commented Nov 13, 2020

@crazy-max, see actions/starter-workflows#96 (and the ref to docker/cli#2089). Ideally developers/maintainers of Docker and GitHub Actions would communicate with each other for achieving a satisfactory solution.

@crazy-max
Copy link
Member

@eine

Ideally developers/maintainers of Docker and GitHub Actions would communicate with each other for achieving a satisfactory solution.

Maybe GitHub could simply install the pass credential helper on the GitHub Runner. WDYT @clarkbw?

@clarkbw
Copy link
Contributor

clarkbw commented Nov 13, 2020

I've asked for this before. I'll push for it again.

@valentijnscholten

This comment has been minimized.

@clarkbw
Copy link
Contributor

clarkbw commented Dec 2, 2020

In the short term can we only filter out the login message?

@eine
Copy link
Author

eine commented Dec 2, 2020

@clarkbw this issue is about requesting relevant warnings not to be hidden from users. ATM, the warnings are filtered out: #25.

@crazy-max
Copy link
Member

@eine @clarkbw actions/runner-images#2304 has been merged. Will be available ~January (actions/runner-images#2302 (comment)).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants