Their password was 12345

That's the stupidest password I've ever heard in my life! That's the kind of thing an idiot would have on his luggage!

And yet it consistently ranks high on passwords still in use. This is a clickbaity article but there are better ones out there https://www.cnbc.com/2022/11/23/most-common-passwords-of-202...

Just FYI for those who missed it:

The previous comments were referring to the famous and really hilarious Mel Brooks movie "Spaceballs", this scene in particular:

https://youtu.be/a6iW-8xPw3k

I see that your schwartz is as big as mine

Now let's see how well you handle it.

Definetly not true. This can be the best password in certain conditions. You should not put your "good" passwords to any shady site out there. You have no idea how passwords are stored on all these platforms one is registering to. If you can live with the fact, that an account may be hacked, then go for a super easy password if you want.

You missed the joke. https://m.youtube.com/watch?v=a6iW-8xPw3k

If you are following the policy of unique passwords per login then there is no need for "saving up the good passwords".

Yeah, everyone in the world is tech savvy enough to work with password managers. Reality looks different, trust me.

Excusing the fact it was a joke, on the serious side, a person shouldn't have any kind of set of "good" passwords. They should just have secure passwords they have auto-generated and have some way of retrieving the password from where they are stored when needed.

Or, just have a unique password for every site stored in a password manager, and then they can all be “good” passwords, with no big concerns about how they are stored!

Other than your eggs in one basket password apps being hacked and exfiltrating them all which would never happen.

https://www.macrumors.com/2022/12/02/lastpass-hacked-second-...

"Our customers' passwords remain safely encrypted due to LastPass’s Zero Knowledge architecture."

I take your point but I'm not aware of any hack of a major provider which resulted in exfiltration of decrypted customer secrets. Providers often enumerate how they prevent exactly this scenario [1][2], but you'd be correct that if your endpoint were compromised, it's probably game over. To be fair in this scenario just typing in your password (not using a manager) would also be game over.

If you want other options, it is possible to self-host (i.e. Vaultwarden). Personally I've been using 1Password for a long time, and their "Families" offering [3] is exceptional for me and has meaningfully improved my family security since the UX is easy enough my loved ones don't find a unique password per site "a chore".

[1] https://support.1password.com/1password-security/ [2] https://1passwordstatic.com/files/security/1password-white-p... [3] https://1password.com/families/

All it takes is a supply chain attack and it's all gone

Remind me to change the combination on my luggage...

solarwinds123

You're assuming that the breach was done through the UI and not for example an oauth token or ssh key that was stolen from a developer's machine and used to download the source code by the attacker.

Another comment mentions GitHub themselves detecting the breach - in this case it's unlikely to be done via a compromised developer's laptop as the access would otherwise look normal and wouldn't trigger GH's security alerts.

It would look abnormal if it was accessed from a dubious geolocation compared to normal access, which are things github can track and detect.

Depends, if someone suddenly starts pulling down every single repository in the org, that should ring some bells.

Meh... I do this every 6-8 months as a principal engineer. I've had many legit use cases.: Understanding our overall dependency tree, validating code coverage assumptions, seeing which projects built still, testing out prototype profiler reports, inspecting the code to see how hard adding x pattern would be, quantifying code change patterns over the pandemic, seeing which uses of the AWS sdk or internal clients were instrumented with metrics, seeing what pct would build under make/go build/bazel/etc.

Anyway many legit reasons. Should it set off an alarm? Probably. Can you say before you do it? For sure!

Depends on the number of repositories I would assume. There are orgs with thousands of them.

Last I downloaded it was around 3600 of them.

I think that they have alerts for when an access token is found in the wild, for instance. So it is quite possible.

Why would it always look normal? Different IP, different usage patterns could trigger the alert.