pull down to refresh

115 sats \ 7 replies \ @supratic OP 6 Aug \ parent \ on: Bitcoin Red Team update: 4,962 issues in 390 projects, 85 critical, 635 high sev bitcoin

At least help builders be aware of vulnerabilities that they wouldn't see otherwise.

write
compose
154 sats \ 6 replies \ @k00b 6 Aug

I'm very happy they're doing it. I'm questioning the very loud promotion of it even if it is vague.

reply
77 sats \ 4 replies \ @Natalia 6 Aug

I thought the same, shouldn't they share with each project in private?

reply
147 sats \ 3 replies \ @k00b 6 Aug

That's usually how this kind of thing is done. I think because they're excited to help and, because they are being vague, they think it's maybe not the same thing. But when red teaming = skilled programmers pointing uncensored models at projects, it's not exactly vague anymore.

reply
85 sats \ 2 replies \ @optimism 6 Aug

Usually you don't disclose that you're working on something until the fix is deployed. This has gone out of the window it seems, which is extra dangerous now, because anyone can ask a bot to write a script to feed repos into bots.

reply
126 sats \ 1 reply \ @supratic OP 6 Aug

Good intention is not enough sometimes; it feels a bit improvised. Some people with dirty broken keyboards and more field experience in these matters should jump in.

reply
1 sat \ 0 replies \ @optimism 6 Aug

I think what they'll need most is case managers. Those are expensive though. Can't outsource that to a bot.

reply
113 sats \ 0 replies \ @SimpleStacker 6 Aug

Maybe the promotion is the point (even if they've convinced themselves it isn't)

reply