Hacker News new | ask | show | jobs
by wzdd 21 days ago
The OP notes that they had to use special phrasing to get their exfil to work, so clearly GitHub was aware of the issue and made an attempt to prevent it.

It seems like the proper fix is for GitHub not to allow their agentic workflow to execute in a public repo context if it also has private repo access. Or, to use your phrasing, for GitHub to flag and disallow this easily-detectable and dangerous type of misconfiguration.
1 comments
brookst 20 days ago
This “detectable and dangerous type of misconfiguration” is used by many developed daily and breaking it would break important workflows.

It’s like saying that an OS should enforce that home directories can only have 0600 permissions. Yes, it prevents accidentally configuring world readable on files, but there are legit reasons for wanting to share a file from your home dir.

link
centuryfall 19 days ago
Why is that an issue though when it is the lesser of two evils? At the very minimum, regardless of “misconfiguration” or not, not having any type of warnings to advise against this behavior is quite bad.

Misconfiguration isn’t really the best word choice, either, because it’s definitely a both-sides problem.

link