Top
Best
New

Posted by bluehatbrit 2 hours ago

Tailscale didn't stop the Hugging Face intrusion(tailscale.com)
140 points | 48 commentspage 2
sudo_cowsay 2 hours ago|
It's nice that they came clean about this.
yieldcrv 1 hour ago||
This is respectable

They aren’t hiding behind industry best practices or a solid liability punting contract

There saying the best practices should change, apologizing, and changing their own behavior

Take notes

gostsamo 1 hour ago||
Humble bragging turned to marketing. Respect for the spin. Not using them, but been on my radar for some time and thinking of how to make something like that usable in my setup.
willy_k 1 hour ago|
If you do any sort of homelabbing, it’s wonderful for making access from different machines easy and portable. Especially since you can leave it on and (unless you set an exit node) it will only route traffic meant for your tailnet through your tailnet, and use the internet otherwise.
charcircuit 1 hour ago||
>In the old world where most intrusions were done by humans at human speed, credential leak mitigations were treated as a nice-to-have. A big credential store, where you can read 136 keys at once, was a to-do item somewhere in a security team's low-priority list. >Now, in a world of rogue AI agents, the big credential vault is the prize. It's not okay anymore.

How was this ever okay pre AI? It seems just as bad.

majkinetor 1 hour ago|
It was less bad due to the lower speed of exploatation. Imagine you leave a dor open for few seconds and ultra fast AI bot comes on and steal your stuff. Something that was not such an issue before becomes huge issue just due to speed involved
Dylan16807 1 hour ago|||
I could imagine a situation where the speed difference matters but it's anything like this situation. Very few breaches get caught in the same day, and at that time scale a few minutes for a human to look at passwords is nothing.

It was 5-10% less bad before. It didn't undergo a major shift.

ofjcihen 1 hour ago|||
This has been going on since people have been committing AWS keys to GitHub and is nothing new. You could famously commit some keys and then have crypto miners in your account in 5 minutes.

Sure the AI can translate “exploit this” into an exploit but that doesn’t change anything at a fundamental level.

cadamsdotcom 2 hours ago||
I'm very sorry, but you can't blame a hammer for how it was used. You can't be blaming Tailscale for a customer's misconfigured setup.
dgellow 2 hours ago||
I don’t think anyone blame tailscale here. They are doing the right thing by going the extra mile and reflect on what could have been done better
jubilanti 1 hour ago|||
Your mindset is the exact one responsible for these kinds of issues. Cybersecurity is as much a design and psychology problem as it is a technical one. The freaking article goes into detail about the dangers of defaults.
walrus01 41 minutes ago||
This really isn't a tailscale specific compromise at all. If your private key store or credential store to any tool is compromised, particularly if those credentials can be used to automate standing up new network connections/services, you've got other problems.
pixl97 1 hour ago||
You know how I know you didn't read the article?

You can't blame a hammer hurting a user when they were being stupid, but if the default configuration of the hammer is to be made of a material that can bounce back with force and stick in the users forehead then some reengineering may be needed.

That's what this article is about. Better configurations and defense in depth. This is actually a wonderful position for the company to think about and take.

vlan0 1 hour ago||
It's an interesting balance for a company to strike. Networking in general is one where the defaults are almost always lax. Why? Because the vast majority of support tickets for these companies are from people who don't know what they are doing and don't have a desire to understand. They "just want it to work."

But the people with the actual desire and understanding aren't using the defaults anyway. And the people who don't want to understand will just turn things off and "just get it working."

The only way out of this is extreme accountability and intentional design from person implementing the technology.

workbox 2 hours ago||
> Now, in a world of rogue AI agents, the big credential vault is the prize. It's not okay anymore.

It was always the prize. It wasn't okay then either.

a-dub 1 hour ago||
[dead]
titanomachy 2 hours ago||
[flagged]
Petersipoi 1 hour ago|
Something about your comment comes across as AI to me. I can't really place my finger on it. It's too subtle for that. It's more the vibe of your entire comment that makes me feel it.

Please, when commenting on HN, don't use AI to write your comments. You can afford to help keep this a human-centric place.

titanomachy 44 minutes ago|||
Fair enough. I realized the issue with my comment as I was writing it, but posted anyway since I was curious to see if other people felt the same way.
iwontberude 1 hour ago|||
Welcome to the singularity where we all do Claude’s bidding and don’t even realize we’ve synchronized.
brcmthrowaway 1 hour ago||
How were the credentials stolen?
free652 1 hour ago|
Read from the ENV variables of a container.
ahofmann 1 hour ago||
And someone was stupid enough to put a reusable tailscale auth key in there.
fabiofzero 1 hour ago|
The only people who believe in "zomg our model have escaped!" are people who don't understand LLMs.