Sass, David

@sassdawe@infosec.exchange
347 Followers
367 Following
4.8K Posts

Black Lives Matter

Dreamer | Speaker | Legend | SRE | MCT | Shadow Architect

He/him/his/Skills

VB better than PowerShell

Have we met?

GitHubhttps://github.com/sassdawe
Bloghttps://kolislab.com
Sessionizehttps://sessionize.com/david-sass/
Linkshttps://davidsass.io

Harvard has found --for the first time-- that lithium occurs naturally in the brain, and it's loss is one of the earliest changes leading to Alzheimer’s. They say lithium shields us from neurodegeneration, and maintains function of all major brain cell types.

They eve found a new lithium compound that actually restored memory after onset in mice...

Lithium levels may turn out to be the missing piece of information in Alzheimer's diagnosis -- and treatment.

https://news.harvard.edu/gazette/story/2025/08/could-lithium-explain-and-treat-alzheimers/

Could lithium explain — and treat — Alzheimer’s?

New study finds deficiency ignites neurodegenerative disease, and restoring it reverses brain aging in mice.

Harvard Gazette

chrome developers: we are thinking of dropping support for rendering RSS feeds as something other than garbage code. does anyone have any reasons not to do this?

developers from many different backgrounds: yes, I rely on normal people being able to understand RSS for my business. dropping support will be disastrous for me because I can't rely on people to have some random extension installed.

chrome devs: OK well we're probably going to do it anyway because we can't be bothered to support web standards. uwu google is only a teensy wee company uwu

https://github.com/whatwg/html/issues/11523

#xslt #standards #openWeb

Should we remove XSLT from the web platform? · Issue #11523 · whatwg/html

What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...

GitHub
The unknown and much-appreciated part of #PSConfEU? The talks and the late-night hallway chats. Early bird deal includes 3 nights at the venue hotel. Sleep on site, stay in the loop. 🎟️ €1,750 (save €400) 📍 #Wiesbaden, #Germany, 1–4 June 2026 👉 psconf.eu

It's insane how we've monetized every part of living, even basic needs.

"I really earned my dinner tonight."
"I deserve some rest."

My brothers and sisters in Christ, you literally need those things to survive.

 
Sshh 🤫 their show is on

OK ... I've got the Deployment and Imaging Tools Environment installed. I've created a dir for my WinPE files, initialized it, mounted it, copied in my BIOS-flashing executable, umounted and committed, and I'm now trying to create the ISO (instead of writing directly to a USB). MakeWinPEMedia fails with a spectacularly unhelpful:

ERROR: Failed to create "petest.iso" file.

I've confirmed that I'm running the DITE thing in an admin-level prompt window, and that I have write perms to the ISO destination. Other ideas?

Looks like the script isn't doing much "catch how this thing can fail" checking on the user's behalf.

Edit: resolved, see:
https://infosec.exchange/@tychotithonus/115041145616038133

2/2

Royce Williams (@tychotithonus@infosec.exchange)

@ocdtrekkie@mastodon.social @sir_anders@whimsy.chat OK, success! Had to: * Disable Windows 11's "Controlled Folder Access" * Write the Hiren's ISO on a Windows system using Rufus, with MBR and Dual UEFI/BIOS enabled (Win-E hotkey to enable) * Copy the HP BIOS file to an *additional* USB drive * Enable Legacy Boot and boot Hiren's * Insert the additional drive (which then appears under Hiren's as C: (!)) * Run the flasher * Leave *both* drives in place (because the flash reboot expects BIOS update files to be in C:?) * wait through *four* reboots' worth of flashing Whew!

Infosec Exchange

I don't see the point of active asset inventory.

I have new stuff that we document as we put it in.

I have old fucking shit that we documented years ago that isn't going to change until we rip it out.

Send capital money, please.

Happy #birb!