

Ich liebe dieses Bild, es ist ein Symbolbild für den Ausbau von Fahrradinfrastruktur in Deutschland...

Dem klagenden Netflix-Kunden stehen nun Rückzahlungen für die Preiserhöhungen ab 2019 zu. Die Ansprüche für die Jahre 2017 und 2018 wies das Gericht als verjährt zurück. Andere Kundinnen und Kunden müssten Rückforderungen selbst durchsetzen.
In was für einer schönen Welt wir leben, dass man Unternehmen erst vor Gericht zerren muss, um ungerechtfertigt zu viel gezahltes Geld zurückzubekommen.

"Nicht jeder Computerbegeisterte kann sich selbst zum Sicherheitsforscher ernennen und damit einen Freibrief zum Hacking bekommen", so CDU-Politiker Günter Krings auf Anfrage der ARD-Rechtsredaktion.
Ich möchte kotzen. Herr Krings hat nichts verstanden. Es geht doch nicht darum, wer mit welcher Expertise Sicherheitslücken findet. Es geht darum, damit verantwortungsvoll umzugehen und Responsible Disclosure zu betreiben, damit die Lücke geschlossen werden kann und Schäden für eine Vielzahl von Menschen und ggf. das Unternehmen abgewendet werden können...

Typecasting Typengießung für Nudeln sozusagen.

Haust du mich, wenn ich Löffel sage?

Die Grenze zwischen mutig und lebensmüde ist fließend oder so

Wieso darf ich nicht einfach meine TES (Tu es selbst) Fadennudeln herstellen? 😢

Take a look into borg backup.

Seven countries need to reach the threshold and 1.000.000 signatures are required in total. The seven countries goal has already been reached, so right now only signatures are needed, regardless of the countries they are coming from.

Try a Reddit mirror like RedLib, i.e. https://redlib.privacyredirect.com/

Soweit ich weiß, kannst du über mo.pla gekaufte Tickets bis zu 24h vor Monatsende kündigen oder pausieren. :)

Wäre es Sahne gewesen, hätts bestimmt auch für die 5% gereicht.

Usually I just send an email template asking them to delete my data per the GDPR (I'm an EU citizen). I'm not sure if you can force them to delete anything if they don't have to by law, but I guess asking is free.

I went through some old accounts when I migrated from KeePass to Vaultwarden. From start to finish, it roughly took five weeks for all 25 inquiries to be completed. I check on my accounts every few moons.
Giving a ballpark estimate, 30% of services offer a (semi-) automated delete function in the account setting, 60% comply to emails within a few days and 10% are absolute pains.
RANT INTERMISSION
One of those 10% is Twilio (This expressly doesn't apply if you only use Authy, their 2FA service). They don't have an automated delete possibility, which is already a huge ick for a company of their size. But it got infinitely worse.
THEY DON'T LET YOU CREATE TICKETS WHEN YOU'RE A FREE CUSTOMER AND FORCE YOU TO USE THEIR AI BOT WHICH CAN'T DO SHIT AND WILL HALLUCINATE A WAY TO DELETE YOUR ACCOUNT BY YOURSELF. Their FAQs have conflicting information which some showing options that don't even exist (anymore). And you have to dig through a lot of policy pages to even find an email address to contact that THEY DON'T WANT YOU TO CONTACT BECAUSE THEY "cannot delete data on your behalf because we cannot authenticate your request by email" (quote of one of their FAQ pages).
When I finally found an email address (that was for reporting data of minors being processed, but I didn't care at that point) and pointed out to them that this is likely illegal, it was processed like a normal ticket and my account got deleted within a few days. I wonder why their legal department followed up a few days after that, apologizing for my "experience" and telling me that they would "review their processes"?
Anyway, that is that. If you want to use SendGrid or any other Twilio service except for Authy, save yourself the pain and just email [email protected] instead of trying to follow their processes which even they themselves don't seem to know.
INTERMISSION END
So far, every account I deleted, I couldn't log into after deletion. I can't really check if they deleted the rest without breaking into their data centers.
And I'm not very strict with creating accounts nowadays but I'm much stricter with documenting them to my password manager now so I know that they exist. If I don't need them anymore, they'll get caught in the next rotation.

Is my AiO block getting eaten by corrosion?
Today I was testing the RAM of a friend in my PC and since I had it opened up anyway, I thought I could renew my thermal paste as well. When removing the block from the CPU, I saw this:


To me, this looks like corrosion. The AiO is roughly 6 years old, so it's nearing its end of life anyway, but is that normal? Should I still use this?
Thanks for any advice.

Da man bei keinem der beiden Bilder die Hand sieht, die es hält, ist keines wirklich transparent 🤔

I am a Patreon supporter of Jim Browning. Incidentally, I got this email today:
At last, I can reveal something I've been working on in conjunction with a major UK cellphone operator, O2. Meet dAIsy. Daisy is an AI bot who answers scam phone calls. Thanks to the mobile operator who can fingerprint scam phone calls via the calling pattern, source, sequence of calls and other markers, scam calls are being diverted to an AI bot who has been trained to keep the scammers on the phone as long as possible.
This is my recording of a Zoom interview I had today with Channel 5 news in the UK where you can see dAIsy in action.
I will continue to train dAIsy with real scam phone calls. When we perfect her, the aim is to work with other cell and landline operators to divert scam calls to thousands of instances of dAIsy. [...]
So you're not wrong about this being a project of some anti-scam YouTuber, you just guessed the wrong one.

Yeah, what a disappointment. This guy brought shame to the security community because he was salty that his vulnerability didn't get the attention it "deserved".

Copying my reply from another thread:
This link should be working.
Quoting from the OP tweet:
Unauthenticated RCE vs all GNU/Linux systems (plus others) disclosed 3 weeks ago.
Full disclosure happening in less than 2 weeks (as agreed with devs).
Still no CVE assigned (there should be at least 3, possibly 4, ideally 6).
Still no working fix.
Canonical, RedHat and others have confirmed the severity, a 9.9, check screenshot.
Devs are still arguing about whether or not some of the issues have a security impact.I've spent the last 3 weeks of my sabbatical working full time on this research, reporting, coordination and so on with the sole purpose of helping and pretty much only got patronized because the devs just can't accept that their code is crap - responsible disclosure: no more.

This link should be working.
Quoting from the OP tweet:
Unauthenticated RCE vs all GNU/Linux systems (plus others) disclosed 3 weeks ago.
Full disclosure happening in less than 2 weeks (as agreed with devs).
Still no CVE assigned (there should be at least 3, possibly 4, ideally 6).
Still no working fix.
Canonical, RedHat and others have confirmed the severity, a 9.9, check screenshot.
Devs are still arguing about whether or not some of the issues have a security impact.I've spent the last 3 weeks of my sabbatical working full time on this research, reporting, coordination and so on with the sole purpose of helping and pretty much only got patronized because the devs just can't accept that their code is crap - responsible disclosure: no more.

Unauthenticated RCE vs all GNU/Linux systems to be fully disclosed in 2 weeks with no working fix yet
EDIT: Original post seems to have been removed, try this Nitter mirror instead.

Unauthenticated RCE vs all GNU/Linux systems to be fully disclosed in 2 weeks with no working fix yet
EDIT: Original post seems to have been removed, try this Nitter mirror instead.


Lumpi would like scritchies until the universe ends


...touching the belly is still deadly though.