treasure

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.

Unpaywalled link

85°C is still fine. You wouldn't want your system running at those temps all the time but if those are only spikes during intensive tasks, you're good.

If you want your PC to run a bit cooler, check your airflow, set manual fan curves, or try out a mild undervolt.

Löten ist hier nicht mal erforderlich. Der Akku hat einen Flachstecker, der sehr einfach zu lösen ist. Die eigentliche Herausforderung wird Kleber sein, da man das Handy zum Lösen der Rückplatte erst erhitzen und dann mit viel Vorsicht und Geduld abhebeln muss. Der Akku ist ebenfalls verklebt, sodass man erstmal mit Isopropanol rangehen muss und auch hier wieder viel Vorsicht und Geduld braucht.

Hier findest du ein YouTube-Video dazu. Ist zwar ein allgemeiner Teardown statt ein Batterietausch, aber die Schritte sind auch da enthalten.

Cannot complain.

Spotted the German.

Are you passing CloudFlare captchas with that? I'm using a VPN and whenever I hit a CloudFlare captcha with a modified user agent, it doesn't let me pass.

That's mentioned in the article I believe. I was just trying to save some people a minute or two. :)

TLDR: Avoid Telegram and WhatsApp. Recommended messengers are Session, Signal, SimpleX and Threema. Honorable mention: Briar.