Father of 2. Mathematician, Physicist, Data Scientist and Software Dev/‘Engineer’; and now comedian! Aspiring to be Bandit Heeler.
Australia
Joined April 2014
- Tweets33.7K
- Following2K
- Followers1.1K
- Likes305K
They do a welcome to country on both ANZAC and Australia Day too, so treat it as an embarrassment on those days too.
If it had spread beyond Russian borders, we probably would have. But thankfully it was just a local issue. Wouldn’t surprise me if they quietly update biosecurity rules in a few years though and point to it as ‘proof of an ongoing threat of pandemics’…
Governments will never let an opportunity to grab more control and take more power go to waste. Covid, Climate Change, CFCs, Fuel Crisis, Wars, migration, housing... they take more control and subsequently abuse it to enrich themselves and their mates.
Yep, while theoretically possible, when men are lactating it's usually a sign that something is very, VERY wrong in your body...
Jon Klaric retweeted
ok update on the deleted repo thing, since it kind of blew up
first, some context on why i posted it like that. there have been so many security incidents lately that my brain is basically stuck in alert mode. so when i saw a stranger in our audit log deleting a private repo, i assumed the worst.
we figured out what happened. nobody hacked us, and it wasn't a github bug.
that repo was a private fork of a repo owned by @StainlessAPI, the company that generated our SDKs. our entire SDK pipeline ran on it.
Stainless got acquired by @AnthropicAI back in may. and on october 27, with zero heads-up to us, someone there deleted their copy of the repo.
turns out when you delete a private repo on github, every private fork of it gets deleted too. same request, under two seconds. and our audit log shows the person who deleted *their* repo as the one who deleted *ours*. that's why it looked like a random outsider walked into our org and nuked something.
no email. no "hey, we're cleaning these up, grab a copy." just gone, along with the production repo behind every one of our SDKs.
github support walked us through all of it within a day, which, genuinely, thank you.
one ask though @github: put this in the audit log. right now the event for our repo just says "repo.destroy" by an outside user. if it said "deleted because upstream fork parent X was deleted", we'd have understood it in two minutes instead of spending a night thinking we'd been breached.
we had a local clone, so we pushed it back up as a standalone repo and the SDKs are running again.
if you were a Stainless customer and you've got anything living as a private fork of one of their repos, go detach it today. it takes ten minutes. their delete is your delete.
someone outside our GitHub org deleted one of our private repos.
no membership or invite or role. nothing in our org or enterprise audit logs gave them access. just one repo.destroy from the gh CLI.
and it's not in deleted repositories, so no restore.
@github how is this possible, what sorcery is this?
What MacOS software has gotten better over the last decade? Their hardware is next level but holy shit their software is woeful.
Yeah this was when I was in high school too. It just bored the players, so they swapped to other teams/clubs or other sports.
The problem is that while previously you’d expect someone to have to be some sort of ‘sworn/mortal enemy’ to want to dedicate that much time and resources to taking your company out, but now with abliterated OSS models you could probably just set up and forget a few malicious agents to periodically target rival companies (or lie to the agents and tell them you’re doing pen-testing, supply chain attack testing etc on their behalf) to just wreck havoc.
Brown-hat hacker is from The Primeagen - hackers who aren’t black or white hat, but just want to shit-up the joint lol.
We do. But if they can do it once without auth, what stops them setting up agents/scripts to just to constantly delete a team, company or person’s repos, workflows/actions etc? It’s not just about having backups but the constant spam and time sink of dealing with such BS that is terrifying. The potential to use this for brown-hat hacking/disruption is extremely high.
The rules of soccer dictate that he cannot call it except for insufficient players, medical emergency or unsafe playing conditions.
Be careful with your son’s team… There was a superstar team like that one year when I played soccer as a kid: they were a Div 1 team but the top few competitions were full so they had to be shunted down to Div 4. Beat every other team by 10+ goals, but 2/3rds of the season half the team had left because they were bored of not having any real challenge whatsoever.
Please tell me this is a Halloween tale designed to scare the sh*t out of devs…
someone outside our GitHub org deleted one of our private repos.
no membership or invite or role. nothing in our org or enterprise audit logs gave them access. just one repo.destroy from the gh CLI.
and it's not in deleted repositories, so no restore.
@github how is this possible, what sorcery is this?