@stragu sounds pretty cruel/inconsiderate to me...

It is okay to release a F/OSS project where the expected set of users is you.

It is okay to declare that a F/OSS project that you maintain is feature complete and stop.

It is okay to stop writing new code in a F/OSS project and just review patches from other people.

It is okay to stop reviewing patches once other people are familiar enough with the codebase to do so.

It is okay to admit that a F/OSS project that you created has so much technical debt that people would be better off reimplementing it than depending on it (especially if you write down the lessons that they should learn).

It is okay if your F/OSS project doesn't meet the requirements of some potential group of users, as long as no one applies pressure to force them to adopt it.

It is okay to tell a company that depends on your F/OSS project that it's unsupported and they can pay developers to contribute if they really need it.

It's okay to say 'I created this F/OSS project to meet my personal needs, but someone else made something that meets those needs better and so I'll use theirs instead'.

It's okay to say 'I made this F/OSS project as an experiment, and the result was that I learned that this approach is a bad idea'.

New release: #PEbear 0.7.2: https://github.com/hasherezade/pe-bear/releases/
- with important bugfixes and new features:

Almost 25 years ago, I wrote a blog post with the title ‘jumping ship slowly’ about leaving Windows (XP was awful, it was mind boggling to me that Vista managed to make people nostalgic for XP). My advice remains the same:

Don’t try switching OS first. The OS is the most easily replaceable bit in the stack. Switch applications first. Most ‘Linux’ apps are cross platform. They’ll run on Windows, and the few that don’t will run in WSL2. You can switch out apps one at a time, and take the time to get comfortable with the alternatives.

Once you’re comfortable not using any Windows-only apps, changing the OS but using all of the same applications is very easy to do. Changing OS and application stack at the same time is an enormous obstacle.

I believe this is also why a lot of corporate and government Linux migrations fail: they try to change everything at the same time and that’s too steep a learning curve.

Wired: Meta Silently Added Face-Recognition Code for Its Smart Glasses to Millions of Phones

Code reviewed by WIRED uncovered an unreleased face-recognition system embedded in Meta’s smart glasses platform. It’s designed to identify people via biometric data stored on users’ phones.

https://www.wired.com/story/meta-smart-glasses-face-recognition-nametag-connections/

#privacy #cybersecurity #meta

Just released our (@ThinkstCanary) internal tool for managing supply-chain risk from compromised packages: https://blog.thinkst.com/2026/06/introducing-package-proxy-supply-chain-safety-checks-without-client-side-software.html

#pypi #npm #cargo #opensource

From prompt 😃to pwned 😢:
Implementing an LLM in your org? Useful.
Trusting its output? That's how a low-priv user became admin.

Ship the feature, don't extend it your trust.
https://blog.quarkslab.com/from-prompt-to-pwned-chaining-llm-and-web-bugs-to-admin.html

@cR0w Please tell me this is fake!

@aleksi Thanks for your work! Keep in mind that it's OK to declare software finished - I'll complain when I find any bugs :)

This was a fun Linux kernel bug (though it only existed on >=6.10 and requires access to network namespaces): https://project-zero.issues.chromium.org/496923375

One of those rare bugs where, if you pass a kernel address in the right place, with the right setup, the kernel will just read from that kernel address as if it was userspace memory, and give you the data that was read.

Somebody released a PoC for Firefox CVE-2026-8389, and it works.

The PoC doesn't include a sandbox escape, and claims that poc-win-sbx.html includes the escape. This file was not shared in the repo.

The python server on localhost seems unnecessary, as the exploit web server can surely serve up primer.js the first time that payload.js is requested, and the actual payload.js the second time. 🤔

Project Excalibur and Edward Teller might have burnt up tens of billions of dollars and prevented nuclear disarmament, but at least we got some hilariously unhinged sentences like that out of it

https://en.wikipedia.org/wiki/Project_Excalibur

absolute gem of a Wikipedia image description

@joxean The brand is legendary, it's worth to listen to their other stuff too ;)

https://www.youtube.com/watch?v=UfUpgWG8bLk

@joxean https://www.youtube.com/watch?v=QjL7D33xpS4

New Project Zero issue:

Linux >=6.10: io_uring: kernel memory read via unchecked address in ITER_UBUF/ITER_IOVEC iov_iter combined with non-checking nocache/flushcache accessors

https://project-zero.issues.chromium.org/issues/496923375

CVE-2026-43073

To save you 34 minutes, researchers had previously found 72 days on which there were second-long jamming events of GPS in most of Europe (as described in https://radionavlab.ae.utexas.edu/wp-content/uploads/Clements-space-interference-iongnss25.pdf ) Later they were able to record such an event & could locate the source of the disruption to a Russian military satellite. https://www.youtube.com/watch?v=tz23G_UXCGA

ti84 game programming about to enter a new golden era
https://bird.makeup/users/coffeededo_o/statuses/2062166308809269495

Unauthenticated RCE as QSECOFR via #IBMi Management Central

https://blog.silentsignal.eu/2026/06/05/unauthenticated-rce-as-qsecofr-via-ibm-i-management-central/

#Java #Deserialization #0day #NoCVE

The idea of banning minors from using social media is at its heart an attempt to punish victims instead of going against the perpetrator. If minors are more easily victimized by the predatory practices of large tech corporations it's not their fault. The blame lies squarely on the corporations. They must stop using predatory practices. And that's doubly important because those practices hurt adults and minors alike.