[dead]
Disrupting supply chain attacks on NPM and GitHub Actions
11–20 of 59 posts
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#12the bare minimum award, for the only language and only registry where this regularly happens.
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#13>> high-impact npm accounts are now put into a read-only mode for 72 hours when they change their email or use a 2FA recovery code. This delay allows maintainers time to respond and recover the account before their account can be used to start an attack. 'what time shall we put here?' 'what's the longest hangover you ever had?' 'let's put 72 hours'
A weekend plus a day to deal with things seems like a decent minimum duration when it’s somewhat arbitrary what the right number is.
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#14Earlier quoted context omitted.
[flagged]
These comments should be removed r from HN, because they in no way actually add to the conversation. They aren’t intelligent, they aren’t insightful, they aren’t actionable, and they don’t invite a genuine reply. All you’re saying is that you happen to not use these technologies yourself – something that I’m sure is only by happenstance – and that you feel superior for it. This is a blog post by GitHub. what are you…
[dead]
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#15>> high-impact npm accounts are now put into a read-only mode for 72 hours when they change their email or use a 2FA recovery code. This delay allows maintainers time to respond and recover the account before their account can be used to start an attack. 'what time shall we put here?' 'what's the longest hangover you ever had?' 'let's put 72 hours'
A weekend plus a day to deal with things seems like a decent minimum duration when it’s somewhat arbitrary what the right number is.
I don't think so at all. People go on vacation all the time. This should be 30 days not 3.
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#16Earlier quoted context omitted.
A weekend plus a day to deal with things seems like a decent minimum duration when it’s somewhat arbitrary what the right number is.
I don't think so at all. People go on vacation all the time. This should be 30 days not 3.
That's the usual runaway problem, right? Why not 60 then? People go on sabbaticals! etc etc.
I feel like the only way to be wrong for this class of problem is to believe that there's a singular right answer. Just pick something reasonable (like how weekends are a fairly common thing, so don't make it shorter than 48 hours). Start there, then see how much of an issue persists. No matter what, at scale you'll find someone complaining that the number is too little, and people complaining that it's too much. Eventually you just have to tell the complainers to deal with it.
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#17Earlier quoted context omitted.
A weekend plus a day to deal with things seems like a decent minimum duration when it’s somewhat arbitrary what the right number is.
I don't think so at all. People go on vacation all the time. This should be 30 days not 3.
It's often not the maintainer that removes a poisoned release, it's the npm security team/tools. So unless the whole team takes a month off, we're all safe.
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#18[deleted]
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#19Github owns NPM. Github has unprecedented access to code analysis tools. Github can run static analysis on nearly everything. Introducing a cooldown period seems like the lowest tech solution to a technological problem I have seen in a longwhile.
Re: Disrupting supply chain attacks on NPM and GitHub Actions
#20Earlier quoted context omitted.
I don't think so at all. People go on vacation all the time. This should be 30 days not 3.
That's the usual runaway problem, right? Why not 60 then? People go on sabbaticals! etc etc. I feel like the only way to be wrong for this class of problem is to believe that there's a singular right answer. Just pick something reasonable (like how weekends are a fairly common thing, so don't make it shorter than 48 hours). Start there, then see how much of an issue persists. No matter what, at scale you'll find some…
There is a big difference between 3 days when someone may be sick or traveling and not looking and 30 which aligns better with 99% of scenarios this may be an issue with. 3 days is absurd. Even password apps with kill switches will default to 7 days.
Cyber attacks will frequently happen on a Friday just for this scenario, they anticipate no ones looking over the weekend.