News for hackers. Stuff that matters.
Re:`123456' password used in Danish CPR data breach by zkmon on Saturday October 10, 2026 @06:37AM (#50031527)
I wouldn't the blame the guy. The security teams tend to serve entirely security related goals only, and they don't hesitate to stop all activity, if they are allowed to, to ensure the highest level of security. On the other side, there are people who have goals for productivity and getting work done. They don't hesitate to take the shortest route possible to maximize their productivity. If productivity is not your goal, then security is not my goal.

It's tussle between two counter-acting forces at play. This get's worse when the overarching authority that supervises both departments, has no clue about how to hit a balanced prioritization. For example, security teams rule the financial companies, like mafia bosses. No one, including CEO, can dare to question why so many layer of security is needed.

Re:`123456' password used in Danish CPR data breach by ddosmax556 on Saturday October 10, 2026 @08:16AM (#50032167)
It's not that hard to enable 2fa & force password manager usage. And it's not that hard to use it. In fact a pw manager alone is much more convenient than remembering passwords. The only people I know who "can't remember their passwords and are locked out" are people who don't use the pw manager and have dogs*it passwords with tiny variants they forget. They often need multiple attempts to log in anywhere. Yeah 2fa & pw manager is a tick more complicated but it's not like it take hours, it takes minutes per day. And you protect against stuff like this. No sympathy, sorry.
Re:`123456' password used in Danish CPR data breach by Sick-Poster on Saturday October 10, 2026 @08:29AM (#50032274)
It is actually very hard to force password manager usage. You can encourage it, educate, but forcing it? How do you do that.
Re:`123456' password used in Danish CPR data breach by paulddraper on Saturday October 10, 2026 @09:37AM (#50032857)
Passkeys.
Re:`123456' password used in Danish CPR data breach by jackjeff on Saturday October 10, 2026 @09:49AM (#50032974)
Yeah. I prefer 2FA. My passwords look like 1bTsby#ZNaz1TJDDzglL&MmD&HOCMd^Cc and having a separate device with a TOTP token is more secure.

I won’t be victim of url jacking since the password manager feels the form. And if it can’t then the domain name is wrong.

And if you steal all the keys/passwords, unlike with pass keys, that’s not enough. I don’t like having all my eggs in one basket no matter how shiny.

Re:`123456' password used in Danish CPR data breach by paulddraper on Saturday October 10, 2026 @02:29PM (#50035715)
Passkeys are really long password locked to a domain, i.e. no different* than your setup.

Passwords are just a worse, hacky version of passkeys.

*They are private/public keys, so they can’t be MITM.

Re:`123456' password used in Danish CPR data breach by dwedge on Saturday October 10, 2026 @08:31AM (#50032288)
How do you force password manager usage?
Re:`123456' password used in Danish CPR data breach by misiek08 on Saturday October 10, 2026 @08:41AM (#50032370)
Technically or socially? The second one is hard, the first one can be done easily - just require the passwords to be 14/16+ characters, multiple symbol domains and calculate tempo of input. Slower than 350ms between keystrokes - error message. Those who can type that fast already are using pw manager or you can just skip this 0.001%.
Re:`123456' password used in Danish CPR data breach by GuB-42 on Saturday October 10, 2026 @09:15AM (#50032623)
Doing that will certainly get people to use a password manager.

But it doesn't say which password manager.

The most popular password manager is some text/word/excel document on the desktop.

Re:`123456' password used in Danish CPR data breach by jnovek on Saturday October 10, 2026 @10:35AM (#50033434)
I have no evidence to back this hypothesis, but I wonder if that’s still more secure than using bad passwords.
Re:`123456' password used in Danish CPR data breach by loglog on Saturday October 10, 2026 @09:01AM (#50032523)
Everyone's password is now 1q1q1q1q1q1q1q1q1q1q!Q
Re:`123456' password used in Danish CPR data breach by ulfbert_inc on Saturday October 10, 2026 @06:49AM (#50031597)
You are presenting a false dilemma (probably unintentionally). While security can be at odds with usability, basic measures like password generation and management are a solved problem. In fact using password manager is more convenient than typing password manually, even 123456 :)
Re:`123456' password used in Danish CPR data breach by xandrius on Saturday October 10, 2026 @07:08AM (#50031725)
Ha, I don't need to type 123456, it's stored in my navigator's password manager for convenience. Checkmate.
Re:`123456' password used in Danish CPR data breach by throwawayffffas on Saturday October 10, 2026 @10:10AM (#50033195)
I don't type 123456 either. I stop at 5.
Re:`123456' password used in Danish CPR data breach by hdgvhicv on Sunday October 11, 2026 @03:18AM (#50040492)
It’s worth noting that they still had to kidnap the princess to find out the password. It could have been anything and wouldn’t have made a difference, it’s still vulnerable to the $10 wrench.
Re:`123456' password used in Danish CPR data breach by holowoodman on Saturday October 10, 2026 @08:05AM (#50032078)
Next step in typical security team fashion: Prevent password managers from working, by obscuring the password field, using click-to-type passwords or similar shenanigans, because fuck you, that's why...
Re:`123456' password used in Danish CPR data breach by paulddraper on Saturday October 10, 2026 @09:36AM (#50032848)
You need a better team
Re:`123456' password used in Danish CPR data breach by Muromec on Saturday October 10, 2026 @09:55AM (#50033030)
We can't have nice things.
Re:`123456' password used in Danish CPR data breach by looperhacks on Saturday October 10, 2026 @08:19AM (#50032183)
Unless of course, you need to unlock your password manager, which is not integrated with your browser, because corporate IT doesn't allow browser extensions or desktop apps so you're bound to a web app ...
Re:`123456' password used in Danish CPR data breach by dudul on Saturday October 10, 2026 @10:56AM (#50033606)
Until security forces the password manager session to expire after 1 hour, and forces the master password to be 16 char long with a combination of lower, upper, digit, punctuation, moon phase, astrological sign. And then they force you to change it every 2 months, and you can't reuse it until the next time Halley's comet is in the solar system.

You're missing the systemic problem the parent is talking about.

Re:`123456' password used in Danish CPR data breach by nvme0n1p1 on Saturday October 10, 2026 @11:39AM (#50034006)
None of those hypotheticals apply in a company where "123456" was allowed as a password to begin with.

And if even if they did, which of these two is easier?

1. Typing your 16 char password with the current moon phase once an hour, and remembering the new one every time a comet passes

2. Pressing your password manager keyboard shortcut (or tapping your yubikey) once an hour, the exact same action that never changes for the rest of your life

Re:`123456' password used in Danish CPR data breach by Dylan16807 on Saturday October 10, 2026 @03:16PM (#50036155)
> None of those hypotheticals apply in a company where "123456" was allowed as a password to begin with.

True.

> And if even if they did, which of these two is easier?

You didn't understand their point. The password manager itself locks and tapping doesn't work until you put in the master password again.

Re:`123456' password used in Danish CPR data breach by nvme0n1p1 on Saturday October 10, 2026 @06:54PM (#50037976)
The fact that password managers can be implemented badly, doesn't mean we shouldn't implement them well.
Re:`123456' password used in Danish CPR data breach by Dylan16807 on Saturday October 10, 2026 @07:47PM (#50038293)
Yes, but at the same time we need to remember that "password manager" can only do so much if reducing friction isn't a priority.
Re:`123456' password used in Danish CPR data breach by nottorp on Sunday October 11, 2026 @01:22AM (#50040048)
But the password for the password manager can also be 123456...
Re:`123456' password used in Danish CPR data breach by IAmBroom on Monday October 12, 2026 @08:28AM (#50055432)
And will be, if it's something trivial like the nuclear arming codes.

Or if your boss has pointy hair.

Re:`123456' password used in Danish CPR data breach by ano-ther on Saturday October 10, 2026 @06:46AM (#50031573)
With two people in the company, there is not a lot of room for corporate games though.

> According to Denmark’s Central Business Register, Pays ApS had two employees as of July 2026.

Re:`123456' password used in Danish CPR data breach by tialaramex on Saturday October 10, 2026 @06:49AM (#50031596)
> It's tussle between two counter-acting forces at play.

It really doesn't have to be, and setting things up as adversarial is counter-productive. Pretending that you're "balancing" two competing alternatives when they may not even be opposed is a problem, it gets you C++ std::span, a type which was standardized to be pointlessly dangerous because hey, surely if it's less safe that will make it faster right? [Morgan Freeman's Voice: But it was not faster]

Re:`123456' password used in Danish CPR data breach by tossandthrow on Saturday October 10, 2026 @06:53AM (#50031624)
I would love to hear about a world where security and productivity are not counter acting forces.

For a start, most people would certainly be more productive if they hadn't had to authenticate themselves.

If you can just create a world for that simple case, then I will rest my case.

Re:`123456' password used in Danish CPR data breach by tialaramex on Saturday October 10, 2026 @08:28AM (#50032261)
Single-sign on is actually a really obvious and familiar example where you achieved better security (now all sixty five systems we use are protected by the same security, when we upgrade that security we're upgrading all sixty five systems) and yet you got better productivity because now I can get stuff done without battling two dozen authentication systems to do it, just sign in once.

Another easy thing (unless they did it already and I didn't notice) would be Microsoft Entra could default enable Security Keys for authentication. Less friction than remembering passwords or one of those apps on your Phone, but better security.

Re:`123456' password used in Danish CPR data breach by chrisjj on Saturday October 10, 2026 @09:17AM (#50032644)
> Single-sign on is actually a really obvious and familiar example where you achieved better security

My local all-eggs basket vendor agrees 100%.

Re:`123456' password used in Danish CPR data breach by Dylan16807 on Saturday October 10, 2026 @03:21PM (#50036210)
All the eggs keep being stored in the same place (same computer) either way, but one gives them a deluxe padded package and the other one wraps a random material around each egg.
Re:`123456' password used in Danish CPR data breach by chrisjj on Saturday October 10, 2026 @04:42PM (#50036973)
Because deluxe padding only comes in multi-egg size, I guess.
Re:`123456' password used in Danish CPR data breach by Dylan16807 on Saturday October 10, 2026 @04:57PM (#50037097)
Deluxe padding is a very high quality password and/or a physical device.

You're not convincing a normal person to memorize 20 high quality passwords, and multiple physical devices are going to be put on the same keyring.

So in short, yes.

Re:`123456' password used in Danish CPR data breach by chrisjj on Sunday October 11, 2026 @04:26PM (#50047462)
Nor are we convincing a normal person that a long high-entropy password is high quality.

It is going to get written down. So having multiple is very little extra trouble.

Re:`123456' password used in Danish CPR data breach by Dylan16807 on Sunday October 11, 2026 @06:09PM (#50048397)
> It is going to get written down. So having multiple is very little extra trouble.

Written down in the same place so we're back to one basket holding all the eggs!

Re:`123456' password used in Danish CPR data breach by chrisjj on Thursday October 22, 2026 @01:59PM (#50198902)
One basket that the user can secure personally.
Re:`123456' password used in Danish CPR data breach by tossandthrow on Saturday October 10, 2026 @12:40PM (#50034589)
Arguably, you'd still have better productivity had you not have to sign-in.

So you are still making a trade-off

Re:`123456' password used in Danish CPR data breach by xoa on Saturday October 10, 2026 @01:34PM (#50035171)
>Arguably, you'd still have better productivity had you not have to sign-in.

No, that is not arguable for anyone who takes more than a few seconds to think about it. Signing in has nothing to do with authentication, it's about things like "I want to have my own preferences set for showdead/noprocrast/etc. I want to maintain my own lists of favorites." Authentication & security are about making sure others don't access/alter your account or use your property or the like without permission, not about there being infinite resources and everyone being perfectly identical.

>So you are still making a trade-off

Nope.

Re:`123456' password used in Danish CPR data breach by tossandthrow on Sunday October 11, 2026 @03:14PM (#50046764)
What?

You can easily have you own configuration without logging in.

Re:`123456' password used in Danish CPR data breach by ptx on Sunday October 11, 2026 @06:05PM (#50048360)
No, because someone else will then come along and mess up your configuration and destroy your work, either accidentally or just to be a jerk, which will set your productivity back significantly.
Re:`123456' password used in Danish CPR data breach by tossandthrow on Monday October 12, 2026 @07:34AM (#50054861)
Yes, so you are elevating the probable to the possible.

This is like me saying that it is more productive to work using pen and paper because it is not prone to electric failures in thunderstorms.

It is right under a certain low probability event that I myself can define and you cannot refute it.

Re:`123456' password used in Danish CPR data breach by xoa on Sunday October 11, 2026 @06:41PM (#50048722)
>You can easily have you own configuration without logging in.

Are you trying to gaslight/troll us now? Separate user accounts is precisely the mechanism of having your own configuration on a multiuser system. Log out of Hacker News right now (or open in a private window or whatever), and then tell us how to "easily" configure showdead/noprocrast/topcolor etc without an account. How do I sit down at my Mac or BSD or Linux machine and have everything the way I want with no logging in?

Seriously, what the fuck are you talking about?

Re:`123456' password used in Danish CPR data breach by tossandthrow on Monday October 12, 2026 @07:30AM (#50054822)
Back in the 2006 I did not have to login to my Windows machine, I also did have my configuration.

It is because you guys are entirely logged into a very small subset of systems.

You are apparently also not able to separate the different concerns of authentication and identification.

You could easily envision a system where you can ID without any auth.

You being narrow minded is not me gaslighting.

Re:`123456' password used in Danish CPR data breach by xoa on Saturday October 10, 2026 @08:39AM (#50032361)
>I would love to hear about a world where security and productivity are not counter acting forces.

Well, it's this one? Or at least for a wide array of practices. To take a trivial example, can you explain how switching encryption from DES to AES (a clear improvement to security) is counteractive to productivity? Of course not, whether it's AES or ChaCha20-Poly1305 or ROT13 the choice of underlying cipher is transparent to the higher level user/application. Or how about reducing memory overflow bugs? That improves security, while also reducing a certain class of crashes. How is reducing software crashes counteractive to productivity?

Even if we take your silly example you clearly intend as a gotcha:

>For a start, most people would certainly be more productive if they hadn't had to authenticate themselves.

People have to identify themselves though in a multi-user environment anyway. Even completely putting aside any sort of security, we all of course have our own preferences for work environment, our own collections of data, etc etc etc. Duh. When we access a system (be it via GUI or CLI or web site) we need to say "I want to use xyz account" anyway. So the marginal cost to auth well can be zero. Using a password manager means "entering user name" and "entering user name and password at the same time" both have the exact same cost: 1 click of a button. Or if using a smartcard/USB PIV token or the like instead, it again can be the same effort: insert it, tap something.

Certainly it's true that sometimes there are unavoidable tradeoffs. But there's a lot of low hanging fruit where things can be made more convenient/productive and more secure at the same time.

Re:`123456' password used in Danish CPR data breach by tossandthrow on Saturday October 10, 2026 @10:55AM (#50033589)
You are paltering.

The premise was not to enhance security, but to design a world where security and productivity are not tradeoffs.

Re:`123456' password used in Danish CPR data breach by xoa on Saturday October 10, 2026 @01:30PM (#50035124)
>You are paltering.

No, I'm honestly engaging with the topic and your post, vs tossing around insults.

>The premise was not to enhance security, but to design a world where security and productivity are not tradeoffs.

And I gave you examples, including engaging with your own example/question. You claimed that "most people would certainly be more productive if they hadn't had to authenticate themselves". But IDing and authenticating are different operations, people would need to ID regardless even in a world where no security was necessary. So if the marginal cost of auth over ID is zero, then by definition that means there is no tradeoff between security and productivity. Something like a security key/card is an example of accomplishing that. Plugging that in and typing 6 numbers or touching it is not merely no extra effort vs typing my user name alone, it's literally faster.

And again to other examples, anything transparent to the user is, again, by definition not an impact on productivity. For another not merely "common" but "near universal" example, see full disk encryption (which is now often the default even with no authentication at all). FDE definitely addresses a few classes of threat scenario. What do you argue is the tradeoff in productivity?

Re:`123456' password used in Danish CPR data breach by chrisjj on Saturday October 10, 2026 @09:14AM (#50032618)
> most people would certainly be more productive if they hadn't had to authenticate themselves.

... right up to the moment when they aren't.

I like to think of a law of conservation of productivity.

Before: yours 100%, hacker's 0%.

After: yours 0%, hacker's 100%.

Nonsense, of course. Hacker's boost is nearer 100,000%.

Fact is, modern computer power is inherently far more productive for bad than good. And the economic incentive follows.

Re:`123456' password used in Danish CPR data breach by tossandthrow on Saturday October 10, 2026 @10:56AM (#50033605)
Ah yes, you found the perfect argument to give sec people full and uncontrolled reign.

Not is it probable that people will take over our system. But is it possible.

Re:`123456' password used in Danish CPR data breach by IAmBroom on Monday October 12, 2026 @08:37AM (#50055537)
Bots exist. It is probable.
Re:`123456' password used in Danish CPR data breach by TehCorwiz on Saturday October 10, 2026 @07:45AM (#50031943)
Productivity and Aesthetics could also be said to be counter acting forces. Or really anything that requires contemplation. I think the problem is in how some people define "productive". Is it productive to have significant security problems which cause more work?
Re:`123456' password used in Danish CPR data breach by kay_o on Saturday October 10, 2026 @06:53AM (#50031620)
Touch one hardware key for every interaction then, not 123456, the hell?
Re:`123456' password used in Danish CPR data breach by tokai on Saturday October 10, 2026 @07:03AM (#50031691)
Just because a task is hard it should never absolve anything. Guy could just have quit if he didn't want the responsibility.
Re:`123456' password used in Danish CPR data breach by zweifuss on Saturday October 10, 2026 @08:29AM (#50032271)
The account with the weak password was a former employee. It’s not on her/him that the account remained active and the admin password wasn't changed in the same process.
Re:`123456' password used in Danish CPR data breach by IAmBroom on Monday October 12, 2026 @08:39AM (#50055568)
It IS on her/him that they chose a terrible password. It's the computer equivalent of driving without lights at night.
Re:`123456' password used in Danish CPR data breach by altmanaltman on Saturday October 10, 2026 @06:52AM (#50031618)
Setting '123456' as a password on any non-trivial system is not "the shortest route possible to maximize their productivity." It would be setting the password as "000000"
Re:`123456' password used in Danish CPR data breach by nylonstrung on Saturday October 10, 2026 @07:21AM (#50031796)
The guys who are really into keyboard layouts would argue vehemently that 123456 is more ergonomic as it's an "inward roll" vs 6 consecutive presses of a key that aligns to the pinky
Re:`123456' password used in Danish CPR data breach by PunchyHamster on Saturday October 10, 2026 @10:45AM (#50033510)
121212 would probably be more ergonomic
Re:`123456' password used in Danish CPR data breach by ntoskrnl_exe on Saturday October 10, 2026 @07:10AM (#50031737)
I'm not sure, I think it's a little more ergonomical to hit six different keys compared to hitting a single key precisely six times.
Re:`123456' password used in Danish CPR data breach by IAmBroom on Monday October 12, 2026 @08:38AM (#50055555)
You've created the perfect flytrap for HackrNews gadflies.

"Ackshually..."

Re:`123456' password used in Danish CPR data breach by giveaccountpls on Saturday October 10, 2026 @10:43AM (#50033492)
Sorry, if your job title implies even a smidgen of security responsibility, you deserve to be fired for "123456" as your password. The person who was an administrator would fall under this label. Besides, "If productivity is not your goal, then security is not my goal." is what results in draconic security measures, because employees can't be trusted AT ALL. I really don't understand your comment.
Re:`123456' password used in Danish CPR data breach by vrighter on Monday October 12, 2026 @07:00AM (#50054528)
so security related goals that they sometimes actively stop you from actually doing useful work.

One side wanting us to automate things. And the other refusing us api access to the keyvault.

Re:`123456' password used in Danish CPR data breach by Gepsens on Thursday October 15, 2026 @03:03PM (#50108626)
I see you're conflating utter mediocrity with systemic idiocy