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

Clarify external workflow. Fixes #63 #103

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

david-a-wheeler
Copy link
Contributor

The original requirement is unclear. The discussion on 2024-12-10 tried to clarify what was intended.
This is one attempt to clarify things.

The original requirement is unclear. The discussion
on 2024-12-10 tried to clarify what was intended.
This is one attempt to clarify things.

Signed-off-by: David A. Wheeler <[email protected]>
Copy link
Contributor

@funnelfiasco funnelfiasco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have significant objections to this, but I'll hold off on adding approval until I submit my version and then we can let the WG compare them and see how we should best blend them.

baseline.yaml Outdated Show resolved Hide resolved
@david-a-wheeler
Copy link
Contributor Author

@funnelfiasco - here's my try!

Co-authored-by: Ben Cotton <[email protected]>
Signed-off-by: David A. Wheeler <[email protected]>
@david-a-wheeler
Copy link
Contributor Author

I accepted the change. I'm a little worried that removing the word "external" removes too much, since the objective is really about external code, but maybe this is okay. It's at least clearer than it was before.

Comment on lines +132 to +133
A build process that either leads to release or can read secret data
MUST NOT execute untrusted code.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'd also need to cover any build pipelines that produce artifacts that would be used on a system that might contain sensitive information, such as an end user or developer machine. 🤔 Effectively any pipeline that produces any artifact that could be used by any machine that isn't ephemeral.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this work?: s/secret/sensitive/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or, s/secret/secret or sensitive/

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

Successfully merging this pull request may close these issues.

3 participants