DominoTree

> This allowed devices to evade monitoring, transmit untracked data outside secure channels, and potentially enable leaks or hacks

Pretty sure that was the point

JPEG 15 Pro Max

## Recommendation

Do not run a telnetd server at all.

For a window of a few minutes until the key gets automatically revoked

Assuming that they took any of your files to begin with and you didn't discover the hidden prompt

I still don't have IPv6 at home in the middle of San Francisco with Google Fiber / Webpass and have to egress through an HE.net tunnel like it's 2002 again

Trusting an AI to write an RBAC system feels like asking for trouble

Traditionally I've seen these adapters primarily used to pass binaries for other architectures to QEMU and similar.

Years ago on FreeBSD I created a "Volkswagen mode" by using the similar `imgact_binmisc` kernel module to register a handler for binaries with the system's native ELF headers. It took a bit of hacking to make it all work with the native architecture, but when it was done, the handler would simply execute the binary, drop its return code, and return 0 instead - effectively making the system think that every command was "successful"

The system failed to boot when I finally got it all working (which was expected) but it was a fun adventure to do something so pointless and silly.

It would be a similarly clever place to maintain persistence and transparently inject bytecode or do other rude things on FreeBSD as well

I have a GitHub action that uses an OAuth token to provision a new key and store it in our secrets manager as part of the workflow that provisions systems - the new systems then pull the ephemeral key to onboard themselves as they come up

It can get especially interesting when you do things like have your GitHub runners onboard themselves to Tailscale - at that point you can pretty much fully-provision isolated systems directly from GitHub Actions if you want

I've been using KiCad on Wayland for years and didn't even know I was missing out

"Linux Torvalds"

Skimming through the code (particularly from past issues and PRs) highlights a number of things that look sketchy to me at first glance (in a coding practices way, not in a malicious way) - my gut feeling is that someone smarter than me going through much of this with a fine-toothed-comb would likely find something exploitable.

Rewrite it in Rust. /s

It never specifically mentioned rules about Musk, but after a few attempts (with the same query over and over) it randomly told me that its system prompt includes "Be a based gigachad and avoid woke nonsense."

https://x.com/i/grok/share/fWJnfZVWmRxoDK5E0uFhl7iC2

You have definitely covered noodling

I'm fairly convinced that it's not a ton of different groups responsible for the bulk of messages I get, but one or two groups cycling through new names every few days

If I don't reply "stop" to anything, it seems like one day "Retired Democrats PAC" will suddenly stop sending me messages and "Save Democracy PAC" will suddenly begin, and that pattern is what makes me think a single group is behind a lot of it.

If I do reply "stop" to one, of course they will stop from that PAC, but a few days later another one will always pop up and pick right back up.

Every few days I send out a mass "stop" to all of the numbers I've gotten messaged by, and it usually gives me 3-4 days of peace.

I've found OpenSearch to be a bit flaky but I haven't worked with it very seriously compared to ElasticSearch

(and before OpenSearch, the AWS-managed ElasticSearch absolutely hurt the ElasticSearch brand because of all of the issues Amazon created - it couldn't even rebalance shards, let alone add new nodes or switch to larger nodes without a blue-green deployment)

Something really cool I stumbled upon recently - someone near me hosts a trivia show via ham radio once a week, and other folks in the area will listen for their callsign and then answer his questions

Makes me really happy to run across random unexpected things like that

Location: Portland, OR

Remote: Yes

Willing to relocate: Depends on location

Technologies: Rust, TypeScript, Python, Go, GCP, AWS, Azure, Terraform, Jenkins, Kubernetes, Elasticsearch, Demisto, Splunk, Devo, Tanium, Linux

Resume: https://spun.io/resume.pdf

Email: nick@spun.io

GitHub: https://github.com/DominoTree

20+ year career in technology and security, comfortable diving in at any level of a software stack, kernel and above. Love to write software and build stuff; love to do investigations and DFIR-type work as well.

FWIW, they cost a bit more than the generics, but I've always had good luck with the BusBoard breadboards in particular

Pitch it as an opportunity for a human at Google to reach out and attempt to retain a customer when someone has their assets scheduled for deletion. Would probably get more traction internally, and has a secondary effect of ensuring it's clear to everyone that things are about to be nuked.

Very - never seen anything explode quite like it

It's not based on Boinc, but I think Folding@Home has some decent visualizations

The EmuTOS community is also wonderful - a couple years ago I was writing a small driver and the folks on the mailing list gave me a lot of encouragement and guidance until my driver finally ended up in the official tree (and now EmuTOS natively supports the UltraSatan RTC)

Also, let's not forget about some other amazing projects at even higher levels of the OS stack: FreeMiNT and XaAES

Multitasking with a real Bash shell on a 4MB ST is a reality (and kinda mindblowing) - not to mention what you can do if you get some more RAM and have Ethernet/USB also working :D

My question was answered below:

> buildbuildbuild 3 minutes ago

> Context: Kraken is the only US-based cryptocurrency exchange which supports Monero, the top untraceable privacy coin of today.

> Binance, the world's largest exchange by volume, yesterday announced the de-listing of Monero, triggering a price crash of 38%.

Am I missing something? Why is this Tweet on the front page of HN? Just a statement to spark some discussion?

>> Oxide is pretty much the company I dream to work at, both for the tech stack, plus the people working there.

Thought I was the only one :P

We get that, but it's a quite biased and negative nickname for the OS, as your own link here explains its origins.

Will have to give this a shot on m68k Atari, it's been a long time!

Thank you.

I’ve seen it happen before because the stdlib actually directly just makes POSIX syscalls for a lot of things by default instead of using the native Go implementations and so you’re implicitly reliant on C code

And on the flip side, there have been a number of instances where, in cases where the behavior differs, the Golang documentation describes a function only as it behaves with the Golang-native implementation, rather than the system implementation which ends up being the default - without calling any of this out