243 Followers
658 Following
661 Posts

#Blueteam in #infosec / #cybersecurity at a place.

Outside of tech, interested in #camping, #gardening and family.

Instead of reporting on the dollar amounts of corporate fines, the news should just say how many minutes of profit the fine represents. "The EPA slapped Apple with a two second fine," is much more honest.

> AB 1043 passed the California Assembly 76–0 and the Senate 38–0. Not a single legislator voted against it. The bill had the explicit support of Apple, Google, and the major platform companies. Ask yourself why.

https://agelesslinux.org/

Ageless Linux — Software for Humans of Indeterminate Age

You are being manipulated.

#Israel #IranWar #RussianWar #Despots #IsraelWar

Israel deliberately targeting medical facilities in south Lebanon, say health workers

Medics and officials say there is systematic use of double-tap strikes in campaign to make the south uninhabitable

The Guardian

if you're working on trusted computing at a tech company, know i'll be very mad at you in 20 years when we won't be able to buy real computers anymore and we'll have to either rent a shitty vps from azure or go tear down whatever 2020s era iot devices are still left to steal their MCUs

don't make stuff you know will be used against humanity pretty please

#trustedcomputing

@flesh @benjojo The $ is a unix crypt hash symbol, which indicates the string that follows is an encrypted password string. If the password were to be stored in say plain text, the program to check the password might infer some things about the password that are untrue if it starts with a $ and always error out since it's comparing what it thinks is a hash to a plaintext of the password, and they don't match. One might reasonably assume from this that this restriction is in place because they do indeed save the passwords as plain text...
Making an account on something today when I came across a novel to me password restriction

Interesting article about Atlassian and the experiences of staff.

My view is the company is probably borked and will only get worse. They have clearly been on a downward trajectory for a few years now.

The pivot-to-AI will probably backfire too.

https://www.theguardian.com/technology/2026/mar/21/atlassian-cuts-layoffs-staff-now-looking-for-work-ai

#Atlassian

First came the AI ‘teammates’, then the layoffs: the new reality for Atlassian staff now looking for work

‘These AI agents have been really, really helpful,’ says a former Sydney employee. ‘But you couldn’t use something like that to replace an actual human worker’

The Guardian

iocaine 3.3.0 released, this one's a big milestone!

It has experimental support for firewalling certain IPs off (on Linux, and requires opting in with the default script), and the Rust crate was split up: there's now an iocaine-powder crate, meant to be usable as a library if someone wants to embed iocaine in another application.

The documentation has not been fully updated yet (the language reference is missing the firewall bits), I'm working on that.

This is likely going to be the last release in the 3.x series, too. Patch releases may happen, but 3.4.0 is unlikely. The next release will be iocaine 4.0, with improved performance1, scripting environment, and perhaps even some other goodies!

  • Yes, even further. ↩︎

  • Cookie monster!

    @NNN @archigato Pixel stock OS no longer has nearly as many changes in the monthly releases beyond the security patch backports. QPR1 and QPR3 will be smaller releases than previously and stock Pixel OS exclusive. These releases are only relevant to GrapheneOS for Pixel support. We don't need to deal with it for another device.

    GrapheneOS has security preview patch access already which we didn't receive from Motorola but rather from another OEM not working on devices supporting GrapheneOS.