Copilot CLI (we get that at work) often uses slightly low-level and cryptic git commands. Never noticed that it would use --end-of-options though.
Should check what it does with branch names starting with a dash.
Of course that wouldn't be a security vulnerability, but a user error. It asks user approvals to execute those things and has disclaimers to check results. Which of course every user does all the time... /s
Unless it has changed recently Germany has no general database of biometric data. Of course law enforcement has for the cases they work on, but for the average passport holder the data gets destroyed once the passport has been accepted by the citizen. So it remains only decentralized in passport chips.
It is exactly the same in Sweden: biometrics are stored only until the passport/ID is manufactured, then destroyed. Only copy is on the chip.
At least this is what the law says, and how it is supposed to be. Reality on the ground, though? I am skeptical that the implementation is as perfect as the law requires it to be, especially judging by the quality of the average government IT system...
I was figthing a bit recently to make my 9210 Communicator charge again after well over 20 years in the drawer. But it eventually worked. The first phone with a color screen and a keyboard!
Isn't this anti-news? I vaguely remember they have stopped introducing leap seconds until further notice because they cause too much trouble with today's computing systems. On my phone now and did not research it, as I say vaguely remember. Now we are 37 seconds off. Nobody of us will have to worry that Christmas is around Easter time. We can leave that problem to future generations much more responsibly than many other problems.
That the notice comes every 6 months is just to meet the letter of the original international treaty.
No, they haven't done that yet. It's just a proposal, but it's not likely to be formally stopped until 2035.
The reason we've stopped having leap seconds is because the drift between TAI and UT1 slowed down and has actually been very slowly drifting in the other direction.
The fact that it’s only 6 months seems insane to me and probably the cause of the problem, if time was +- 60 seconds nobody would notice, so a more manageable solution would be to implement an arbitrary leap about once a decade, with a decades notice so everyone can sort their systems with plenty of notice. 6 months for a world wide coordinated execution is laughably optimistic.
I have a German bank sccount that can be used with a standalone code generator, that uses the chip on your bank card.
I have a Finnish bank account that use a completely standalone, purely time-based code generator.
Alternatives exist. But with current know your customer requirements it's increasingly difficult to open new ones if you are a foreigner and/or non-resident.
In Finland many news outlets had the same headline, but needed to correct it. It's the last big operator who closed their network. There are still a couple of smaller local operators that have not yet stopped. Finland traditionally had many local phone companies and a few have obviosly survived.
Should check what it does with branch names starting with a dash.
Of course that wouldn't be a security vulnerability, but a user error. It asks user approvals to execute those things and has disclaimers to check results. Which of course every user does all the time... /s
reply