And Ubuntu, no? Wasn’t that the big selling point of Ubuntu back in the day?

Linux is the backbone of most ransomware infrastructure too.

Sixth and Seventh Generation video game consoles were still using scart/composite/component outputs for CRT up until their discontinuation in 2017 so I’m pretty sure a lot of kids would have had a CRT to game on as well was watch TV in their rooms.

Remember, kids typically get the hand me downs when the adults get new shiny.

In the United Kingdom, people just add a contact to their phone book called “ICE”. You can learn more here.

Good bot

Nice! And MIT too. Perfect; I’ve given it a star now.

I agree. I don’t have the time but someone should point this out to the dev via an issue on GitHub.

So basically don’t use this in anything commercial because the phrase “feel free” is different to legally libre and gratis. I personally wouldn’t touch this until it’s released under a reputable license.

Shame they didn’t use a proper license when publishing.

My very experience at university. Projectile vomit all over the place.

My bad. Must have made a slip up on the swipe keyboard. I meant “years”. I’ve edited my post to correct.

That rear projection beast was the best darn television for tests years until Pioneer made plasmas. I miss ours deeply and wish we’d had the space to keep it (especially for retro gaming and the yearly playing of the Star Wars laser disk).

What’s the reference?

Reference for the admission?

And it’s made by a Bitwarden developer.

They highlighted it was a bug and said it would be fixed very soon after it was flagged. It was addressed in a matter of days. You can build the server with the /p:DefineConstants=“OSS” flag still and you can build the clients with the bitwarden_license folder deleted again (now they’ve fixed it).

I don’t understand why you’re throwing FUD about this. Building without the Bitwarden Licensed code has been possible for years and those components under that license have been enterprise focused (such as SSO). The client is still GPL and the server is still AGPL.

This has been the way for years.

Cool. They got that sorted nice and quickly.

Edit:

I don’t get why people think they’re suddenly doing stuff under a different license to subvert the open nature of the project. They’ve been totally transparent on what isn’t part of the GPL/AGPL licensed code for years.

SSO, the password health service, organisation auth requests, member access report blah blah have been enterprise features under the Bitwarden License for ages and they architected the projects in a clear and transparent way to build without those features since they added them.

Thank you for the smug response however I did indeed read the article and going from 13 months to 10 days is not a trend but a complete rearchitecture of how certificates are managed.

You have no idea how many orgs have to do this manually as their systems won’t enable it to be automated. Following a KBA once a year is fine for most (yet they still forget and websites break for a few days; this literally happened to NVD of all things a few weeks ago).

This change is a 36x increase in effort with no consideration for those who can’t renew and apply certs programmatically / through automation.

Smells like Apple knows something but can’t say anything. What reason would they want lifespans cut so short other than they know of an attack vector that means more than 10 days isn’t safe?

AFAIK they’re not a CA that sells certs so this can’t be some money making scheme. And they’ll be very aware how unpopular 10 day lifespans would be to services that suck and require manual download and upload every time you renew.

Exactly. Source it from upstream at build time or something so it’s transparent.