Erica Windisch

Erica Windisch

@ewindisch.ontological.observer

Working on: Hyprstream.com - RL environments for distributed open AI-RSI Ferruleos.org - hardened Linux sandbox OS Onionshell.ch - tor from a static website

2.3K followers592 following2.6K posts

Erica Windisch reposted

In the pursuit of a fast, functional, and embeddable x86_64 emulator with both a JIT and interpreter, I had Claude cook up a GPLv2 emulator in Rust, with a fast and correct branch of QEMU TCG as a reference: github.com/azenla/uemul... My ultimate plan is to try to make an iOS app like iSH :)

github.comGitHub - azenla/uemulator: uemulator: minimal embeddable x86_64 emulator capable of booting Linuxuemulator: minimal embeddable x86_64 emulator capable of booting Linux - azenla/uemulator

I could write a book about the negative experiences I've had with coordinated vulnerability disclosure programs. Arguably the worst experience was with CPU speculative execution vulns, 3 years before Spectre/Meltdown But the other experiences sucked too It's the users who suffer the most from CVD

It's out.

Cyberdione Labs@cyberdione.bsky.social

Our researchers have discovered vulnerabilities in the open source Tailscale software. These have been reported upstream. Take the appropriate precautions. Our primary recommendation is to disable the "tailscale ssh" feature and App Connectors. www.tailworm.com

Erica Windisch reposted

Our researchers have discovered vulnerabilities in the open source Tailscale software. These have been reported upstream. Take the appropriate precautions. Our primary recommendation is to disable the "tailscale ssh" feature and App Connectors. www.tailworm.com

Erica Windisch reposted

Replying to @ewindisch.ontological.observer

Some people think "responsible disclosure" is some golden rule written down by the ancients and not an optional compromise with its own downsides to weigh against the benefits of full disclosure.

Erica Windisch reposted

These series of dangerous vulnerabilities is scary for sure. But, the really scary part is that state sponsored intelligence services have been playing with these models for a long time now. With less restrictions.

View full thread

I'm working on writing up a report for tomorrow. The highlight is `tailscale ssh` privilege escalation but there's a few other issues planned for the report that will have a broader, but less severe impact. Good night and good luck everyone!

Tailscale SSH is off by default, that much is reassuring.

apenwarr@apenwarr.ca

If you don't trust your SSO, you have a problem, yes. Even so, Tailnet Lock provides solid defense: tailscale.com/docs/feature... Tailscale SSH skips the security theatre of a separate leakable key sitting in your homedir, accessible to any program you run. It's also off by default.

This does *not* impact all tailnet devices. Attacker must be on the tailnet. Systems must be in a non-default but widely deployed and supported configuration. Impact includes systems using headscale.

As a cybersecurity professional, I must say I have loved this week — the asymmetric advantage between their adversaries and the 76ers with Lebron on the team is sending me as a Philadelphian. 🏀

Responsible disclosure is fake

Andrew Couts@couts.bsky.social

NEW: AWS detected attempts to exploit the PHP vulnerabilities on October 17, four days before they were patched. Logs indicate multiple malicious actors tried to use the flaws. @lhn.bsky.social reports: www.wired.com/story/hacker...

I believe The Onion Shell is *NOT* vulnerable to the number 4, or any of the other exposed Intermediary CAs. I designed it to be secure against a MITM against the Root and Intermediary CAs, and this was the first live test of that design.

The Onion Shell establishes an encrypted tunnel to the Tor network via a pinned Snowflake bridge identities, and then proxies through the Tor network to .onion addresses or internet hosts via exits. These connections to not rely on the public CAs.

There is a separate serious warning for all Onion Shell users, however: There is a known MITM attack being executed in the wild at exit nodes intercepting SSH traffic. This attack directly targets The Onion Shell. You must protect yourself by verifying remote SSH key fingerprints!