Een automobilist is woensdagavond in Capelle aan den IJssel met z'n voertuig in het water beland.

Een automobilist is woensdagavond in Capelle aan den IJssel met z'n voertuig in het water beland.

Een automobilist is woensdagavond in Capelle aan den IJssel aangehouden voor rijden onder invloed nadat hij met z'n voertuig in het water was beland.

Mark Sansom has added a photo to the pool:

niggyl :) has added a photo to the pool:

Scotsmans Creek where it flows into the sea at The Gardens, larapuna, Bay of Fires, Tasmania.

Phone shot due to believing I had the wrong filters with me on the day. Turns out that yes the were the wrong size but I had a step down ring in the bag to suit. Far too clever for my own good.

Apple iPhone 14 Pro Max, 2.2mm ultra wide back camera lens. EvenLonger App. 5 secs at f/2.2 ISO 32. -1.2/3 EV

Tricky tradeoffs are hard to avoid when designing systems, but the choice not to use LLMs for some tasks is clear

Systems Approach  As we neared the finish line for our network security book, I received a piece of feedback from Brad Karp that my explanation of forward secrecy in the chapter on TLS (Transport Layer Security) was not quite right.…

Lazyweb, I have PAM questions.

I added support for PAM to XScreenSaver in 1998, when PAM itself was a little two-year-old baby. Your keyboard was still PS2 and HDMI hadn't been invented yet. For lo these many decades, nobody could agree on what went in /etc/pam.conf or /etc/pam.d/login and it was all a giant mess.

Things that used to sometimes be true:

• If /etc/pam.d/xscreensaver didn't exist you couldn't unlock the screen at all.
• "cp /etc/pam.d/login /etc/pam.d/xscreensaver" was insufficient, some lines had to be omitted.
• You have to call pam_chauthtok() or an unauthorized user might be able to unlock.
• No, if you call pam_chauthtok() it will always fail so don't do that.
• No wait, actually you have to call pam_chauthtok() because it has side effects but you have to ignore its failure.
• You have to PAM_REFRESH_CRED every time.
• No wait, that doesn't work, you have to PAM_REINITIALIZE_CRED every time instead. But not on Solaris.

I could not even hazard a guess as to which of these things are still true, or how many decades ago they stopped being true, or which of them are influenced by Linux versus BSD versus Solaris versus HPUX versus AIX versus Kerberos or other things that nobody cares about any more.

So I am considering making the following changes:

• Always call pam_chauthtok() and respect its result status. I think sshd does this.
• Remove the configure option --enable-pam-check-account-type (which probably should always have been a runtime option, not a compile-time option, but here we are).
• At installation time, create /etc/pam.d/xscreensaver as a file containing the single line "@include login"

What I would like to know is: will this break things on your system? Particular emphasis for this question on people running weird-assed obscure systems.

AT&T and Verizon are blocking T-Mobile's new "Switching Made Easy" tool that scans their customer accounts to recommend comparable plans. AT&T is also suing, alleging T-Mobile used bots to scrape over 100 fields of sensitive customer data. From The Mobile Report: According to a lawsuit, which AT&T has shared directly with us, T-Mobile updated the T-Life app's scraping abilities three separate times in an attempt to bypass AT&T's detection. Essentially, T-Mobile and AT&T have been in a game of cat and mouse. Not only that, but AT&T alleges that T-Mobile is intentionally hiding the fact that it's their scraper accessing an account, and essentially pretends to be an end user while doing so. Apparently, T-Mobile's scraping bot tries its best to appear as a generic web browser.

AT&T sent T-Mobile a cease and desist letter on November 24th demanding T-Mobile stop the scraping process. T-Mobile responded two days later refusing, stating that the process was legal because "customers themselves ... log into their own wireless account." On November 26th, AT&T says they detected T-Mobile is no longer scraping the AT&T website, and instead asks users to upload a pdf of their bill or enter some info manually. They note, however, that at the time the app still appeared to scrape Verizon accounts. The lawsuit further explains that AT&T reached out to Apple with the claim that T-Mobile's T-Life app is also violating the App Store Review Guidelines. T-Mobile responded to this complaint as well, making similar claims that the scraping process does not violate those guidelines. [...]

According to AT&T, the T-Life app collects way more information than is necessary for a simple carrier switch. The company alleges T-Mobile grabs over 100 separate bits of info from a customer's account, including info about other users on the account and other services not related to wireless service. It's also worth noting that, apparently, T-Mobile is storing this information, not just using it temporarily, even if the customer doesn't end up switching. T-Mobile has responded to our request for comment, and says that actually, AT&T is wrong about the facts, and Easy Switch is safe and secure...

Read more of this story at Slashdot.

An anonymous reader quotes a report from The Verge's Sean Hollister If you wrote off the Steam Frame as yet another VR headset few will want to wear, I guarantee you're not alone. But the Steam Frame isn't just a headset; it's a Trojan horse that contains the tech gamers need to play Steam games on the next Samsung Galaxy, the next Google Pixel, perhaps Arm gaming notebooks to come. I know, because I'm already using that tech on my Samsung Galaxy. There is no official Android version of Hollow Knight: Silksong, one of the best games of 2025, but that doesn't have to stop you anymore. Thanks to a stack of open-source technologies, including a compatibility layer called Proton and an emulator called Fex, games that were developed for x86-based Windows PCs can now run on Linux-based phones with the Arm processor architecture. With Proton, the Steam Deck could already do the Windows-to-Linux part; now, Fex is bridging x86 and Arm, too.

This stack is what powers the Steam Frame's own ability to play Windows games, of course, and it was widely reported that Valve is using the open-source Fex emulator to make it happen. What wasn't widely reported: Valve is behind Fex itself. In an interview, Valve's Pierre-Loup Griffais, one of the architects behind SteamOS and the Steam Deck, tells The Verge that Valve has been quietly funding almost all the open-source technologies required to play Windows games on Arm. And because they're open-source, Valve is effectively shepherding a future where Arm phones, laptops, and desktops could freely do the same. He says the company believes game developers shouldn't be wasting time porting games if there's a better way.

Remember when the Steam Deck handheld showed that a decade of investment in Linux could make Windows gaming portable? Valve paid open-source developers to follow their passions to help achieve that result. Valve has been guiding the effort to bring games to Arm in much the same way: In 2016 and 2017, Griffais tells me, the company began recruiting and funding open-source developers to bring Windows games to Arm chips. Fex lead developer Ryan Houdek tells The Verge he chatted with Griffais himself at conferences those years and whipped up the first prototype in 2018. He tells me Valve pays enough that Fex is his full-time job. "I want to thank the people from Valve for being here from the start and allowing me to kickstart this project," he recently wrote.

Read more of this story at Slashdot.

Steeds vaker zien we hoe landen de economie inzetten als een wapen. Denk aan blokkades en heffingen of het creëren van afhankelijkheden.