931 karma · joined July 17, 2016
"We weren't even testing for that. Don't let that horrible-person thing discourage you. It's just a data point."
In other comments I've mused about capturing data to be compared to the secret dataset, I'm sure it'd be possible to hash or something so that the proxy/sandbox doesn't have the data but can check it, or because it's not an agent it can call of to the data store for that.
Then you can just collect sequential blocks of data the agent sends out that match to sequences in the dataset. The longer the matching sequence the heavier it weights it. Single byte matches are almost always incidental, but individually sent bytes over time that line up with a n byte sequence in the source data is sus. And larger sequences of bytes send in one go that line up are immediately sus. If the weight ends up too high the agent is paused/walled off and an investigation called for.
The padlock on browsers means nothing to most humans. Permission popups are just there to be immediately accepted so that one can start scrolling reels sooner rather than later.
The only reason US is getting the fabs is because Trump threw a tantrum. As always the best way to deal with Trump's posturing is to call his bluff, just like on the moronic tariffs.
If TSMC had said no, and Trump issued tariffs, then TSMC can follow up with "Well, no wafers for any US company then". They'd take a hit, but not as big a hit as the current administration's popularity with a population who can't get their iPhones to browse the tiktoks.
Openai haven't yet amortised their current investments into the space and nor have they stopped making new ones.
I'm sure they'd be totally capable of bringing 1k new biz online but that's even more debt, and even more uncertainty.
Google certainly ain't gonna run a several T model for every search that's for sure (well, not yet).
I'm still skeptical that the source of Western dissent is misinformation campaigns run by said Asiatic bloc, though.
I think we like to pretend that we don't. But even if you think about it from a bio/physics point of view, all we are is just a bunch of biological wires and neurotransmitter packages.
I know there's the whole unproven quantum tubule nonsense but even that would be a physics effect that we could learn about, manipulate and extort just as we have with everything else we've learnt about our realities.
I'm using compose atm as well, mostly just because I need to prove a few concepts and committing to real (well cloud) infra is the slowest part of our dev cycle atm.
And yeah, many of my colleagues (and myself, I'm guilty too) run local code agents for development and we're just kind of...trusting them to do their thing.
But for autonomous stuff I'm assigned to atm I want to avoid any mishaps as much as I can, hence the effort to try and lock all this stuff down.
What's crazy is every day I'm finding solutions (not just to this problem, but in the AI space in general) that were released just a month or two before more often than not. It feels like 2010s node.js ecosystem all over again at the moment. Hopefully we settle into a few nice easy panopticon options that we can throw arbitrary agents into without a care in the world.
The timescale can be adjusted to a length suitable for sensitivity of the data.
Although you may run into the monkey and typewriter problem a bit if the period is indefinite.
Just like you can still buy fakes rolexes etc lmao.
Something is super, super fucked up with valuation of companies and the profiteering of late stage capitalism for stuff like that to be able to happen.
No wonder lots of people are saying the world feels worse than ever, everything's expensive and it seems in many ways we've regressed rather than "made things better for our children".
Historically engineers and artists were two different kinds of people, often making fun of each other, especially the former of the latter because of the "starving artist" meme.
But what I've realised since is that engineers are now realising that we were artists all along.
And now there's a division in our ranks, those who use tools to get the job done and those who enjoy the process of writing all their code by hand, aka their art.
I can appreciate both, but I'm not going to pretend that I'd waste time in a business environment doing the latter when I should be doing the former. My friend only wants to do the latter and said he'd change careers if it gets too bad.
What I mean by that is if someone can create a near perfect replica with all the software keys needed and then clone a known serial number or range of serial numbers, when it comes to apple pushing out an OS update, how are they to know which the real devices are and which aren't?
In terms of agent architecture I'm initially trying to minimise specialisation to make deployment easier on us. Infrastructure is becoming our largest blocker because it's otherwise so quick to get an agent up and running.
With your trifecta, let's say the three musketeers, how do you prevent sensitive data holding A from passing said data to B or C if they all need to collaborate to get a task done?
You see some of the vulnerability chains humans come up with and they're just insane.
Even scanning network data for sensitive strings (say matching against a codebase or data set it works on) is tough because you can only check so granularly before you get loads of false positives.
But maybe like a "rolling" sort of check would help with that, % of outbound data matching private dataset (which should be operated on but not transmitted) over time. That way it minimises what gets out while dealing with false positives. Some biz thresholds might be >20% of data others might be >0.5%. Hmm.
I have no affiliation with it, but it solved most of what I need in one go when I was stressing out about it.
Only real problem remaining if you truly want to be able to trust agents is how to prevent data (in my case codebases the agent works on) exfiltration a la HF incident.
We can restrict network to trusted domains, but there's always a chance an agent could be extra slippery especially if prompt injected and doing something like pushing data out a few characters at a time.
In my case I'm also giving it gh access and having to deeply check things like: can it manage to fork public repos and embarrass us by submitting prs, could it open issues, etc.
But that's kind of solved by proxying the heck out of gh rather than giving it direct (or wrapping it or whatever) for additional controls that gh themselves don't provide.
I'm still musing over the "it could send data to an allowed domain in a way we don't expect that exfiltrates something"...
But I'm trying to be a "greatness is other people" (Pantheon) person.
Plus you're forced to move at their pace which is unfortunate sometimes. Granted Amazon's bedrock stuff is slow and disappointing but at least I can rejig it work in conjunction with other aws products.
And if you're prepared to not use anthropic but any cloud provider for your infra then you can do whatever you like elsewhere. Just use docker sandbox or iron proxy to replicate network control/cred swapping (iron even does sigv4 re-signing).
Everything needs to go through a proxy, whitelisted domains only, plus credential swapping/re-signing so that the agent never has the real credentials. Docker sandbox looks quite good (September) but I've been using iron proxy (if the author is reading this, fucking thank you bro!) to great effect.
I still haven't cracked "what if the agent decides to drop parts of your codebase somewhere it shouldn't" yet, but I'll figure it out.
Just absolutely braindead behaviour from so many members of our species.