News for hackers. Stuff that matters.
Re:A way to exclude sensitive files issue still open for Ope... by cowsandmilk on Sunday June 28, 2026 @09:23AM (#48707064)
100% this. The idea that Codex should enforce this is putting the security boundary at the wrong layer. If you don’t want codes to access something, make it so it doesn’t have access.
Re:A way to exclude sensitive files issue still open for Ope... by embedding-shape on Sunday June 28, 2026 @10:21AM (#48707524)
The Codex bug tracker is a great insight into how wide the knowledge gap seem to be between users. The issue where people ask them to add back /undo or whatever it is instead of just learning to use git, probably reached 100 comments at least by now. People seemingly don't really understand the computers they use on a daily basis, and refuse to learn too.
Re:A way to exclude sensitive files issue still open for Ope... by atomicnumber3 on Sunday June 28, 2026 @11:51AM (#48708455)
We managed to generate probably-correct code, which can then be probably-corrected recursively to get to something that runs (usually).

This made everyone scream and lose their minds saying that code is finished, people think they don't need a technical cofounder anymore, think they don't need engineers anymore, etc. Then they're, at varying speeds, finding out they're wrong.

It seems oddly circular to me that the _exact hubris_ non-engineers have long accused engineers of - and we have indeed been too often guilty of - they themselves turn out to be JUST as guilty of! Just like engineers thought all sales did was bother people, and all marketing did was send emails, and all support did was tell people to turn it off and on again, and all product did was copy google... they all apparently thought all engineers did was tik-tak-click-clack type code all day and when it compiled it was done. Not knowing how much higher-order... well, engineering, there is to it.

Where are all the CTOs during all of this? I thought someone was supposed to be sticking up for their org? Sales, marketing, etc all seem to have entrenched C-suite people keeping their fiefdoms resistant to erosion by outsourcing, downsizing, etc. But all our CTOs seems to have collectively thrown us to the wolves.

Re:A way to exclude sensitive files issue still open for Ope... by aleph_minus_one on Sunday June 28, 2026 @12:43PM (#48709013)
> It seems oddly circular to me that the _exact hubris_ non-engineers have long accused engineers of - and we have indeed been too often guilty of - they themselves turn out to be JUST as guilty of!

I have hardly ever seen this kind of hubris among software developers. The only thing that was common was many software developers were - let's say - somewhat direct in their feedback towards people who are not willing to learn.

I thus rather have the feeling that this kind of accusation of hubris towards software developers rather originates in business people projecting their own overconfidence (hubris) onto software developers.

Re:A way to exclude sensitive files issue still open for Ope... by akoboldfrying on Sunday June 28, 2026 @07:11PM (#48712751)
> I have hardly ever seen this kind of hubris among software developers.

Dilbert's entire schtick is the profound ineptitude of "business people".

Re:A way to exclude sensitive files issue still open for Ope... by cataphract on Sunday June 28, 2026 @01:28PM (#48709496)
That is not a fault that's specific to engineers. Lots of smart lawyers think they can learn basically anything over a weekend of hard study. It's probably a blind spot of intelligent people.
Re:A way to exclude sensitive files issue still open for Ope... by kgwgk on Sunday June 28, 2026 @03:27PM (#48710646)
Re:A way to exclude sensitive files issue still open for Ope... by blamemods4accnt on Sunday June 28, 2026 @04:15PM (#48711152)
In my limited experience CTOs rarely get a seat at the big boys table, they mostly just take matching orders from the CEO, CFO, and sometimes sales.
Re:A way to exclude sensitive files issue still open for Ope... by dijksterhuis on Sunday June 28, 2026 @07:18PM (#48712812)
> Just like engineers thought all sales did was bother people, and all marketing did was send emails

i mean, sure, the marketing one may be a bit simplified as the emails also need to have pretty pictures in them. and yeah, sure, sales people do need to find the people they’ll eventually start bothering later.

/s

> But all our CTOs seems to have collectively thrown us to the wolves.

the kind of person who usually finds their way into the executive class doesn’t get there by looking after those under them. they get there by avoiding blame and taking credit.

which, funnily enough, is exactly what a hype cycle is all about.

Re:A way to exclude sensitive files issue still open for Ope... by tern on Sunday June 28, 2026 @11:01AM (#48707922)
I suspect most people don't even know there's a there there.

For instance, while I now know that file systems have permissions, before I became a programmer, I spent maybe ten years thinking of permissions as a special, obscure system thing that you should never touch.

For that matter, I suspect many people don't know basic things like that a file system isn't inherently the operating system.

And, where would you go to learn this information? Your Mac doesn't ship with a manual—how would you know one exists? Furthermore, I would wager that perhaps most people have never learned how anything works requiring a manual and are simply unaware that that's a thing.

All to say, I'm not sure "refusal" is the right term.

Re:A way to exclude sensitive files issue still open for Ope... by tingletech on Sunday June 28, 2026 @11:53AM (#48708474)
When I was an undergraduate biology student in 1991 a suitemate told me I should go to some desk in some building over by Muir and get an account on the VAX. There were strange rooms all over campus that were open 24/7 and were loaded with green and amber screen terminals with integrated keyboards. Lots of sessions for CS lectures were held in these rooms and there was always interesting notes on the white boards (most rooms still had black boards or green boards, but think the chalk was too dusty so these rooms usually had the white boards.

Once I saw an instruction that was circled with an arrow pointing to is that said:

  man man
  man -k -or- apropos
and that was how I learned about computers.

I just typed `man man` in a terminal on my Mac, and luckily its still there.

Re:A way to exclude sensitive files issue still open for Ope... by fingerlocks on Monday June 29, 2026 @02:31AM (#48715590)
Nit: Your Mac does ship with a manual. Tips.app and of course the man pages. Point stands.
Re:A way to exclude sensitive files issue still open for Ope... by LtWorf on Sunday June 28, 2026 @12:02PM (#48708568)
That's the product that is being sold here… why shame the users for expecting what was marketed to them?
Re:A way to exclude sensitive files issue still open for Ope... by fragmede on Sunday June 28, 2026 @12:26PM (#48708825)
The knowledge gap is very real. Because unsavvy users are just going to paste the API key into codex and say "make it work". For the truly lazy/uninformed, codex has computer use, and are going to tell it go into Vercel/Netlify/Stripe/Cloudflare for them, and get the API key, and save it to .env for them. So users knowing they need such a feature in the first place should be celebrated when the alternative is even dumber.
Re:A way to exclude sensitive files issue still open for Ope... by wonnage on Sunday June 28, 2026 @01:26PM (#48709482)
I mean based on all the "coding is solved" hype that's what these companies are aiming for
Re:A way to exclude sensitive files issue still open for Ope... by laweijfmvo on Sunday June 28, 2026 @03:59PM (#48710982)
huh, but what if the AI trashes my git repo? maybe it just deletes the .git folder entirely. a deterministic undo wouldn’t be the silliest feature, for the current definition of “AI”.
Re:A way to exclude sensitive files issue still open for Ope... by mirashii on Sunday June 28, 2026 @04:05PM (#48711049)
The default sandboxing for Codex does not allow the agent to access .git
Re:A way to exclude sensitive files issue still open for Ope... by valleyer on Sunday June 28, 2026 @04:56PM (#48711566)
I think this is what you meant, but just to clarify: it doesn't allow it to write to .git. Read access is allowed.
Re:A way to exclude sensitive files issue still open for Ope... by pamcake on Sunday June 28, 2026 @06:43PM (#48712514)
The answer is the same: You give it either read-only or its own copy separate from the one you care about.

The requested feature wouldn't be a robust solution here either for the same reasons.

Besides, have you noticed the amount of other amateur-hour bugs anf jank in Codex going for weeks or months without proper resolution? Given that, why would you want and trust their solution here over alternatives, specifically?

Re:A way to exclude sensitive files issue still open for Ope... by AlienRobot on Monday June 29, 2026 @06:22AM (#48717302)
You mean they went to the codex bug tracker, on github, and they don't know how to use git?

Well that is kind of ironic, isn't it?

Re:A way to exclude sensitive files issue still open for Ope... by MattDamonSpace on Sunday June 28, 2026 @10:07AM (#48707374)
Not sure I agree?

It’s not like gitignore should be independent from git

Re:A way to exclude sensitive files issue still open for Ope... by TheDong on Sunday June 28, 2026 @10:27AM (#48707596)
The difference is that git is a traditional programming tool which executes deterministically.

agents are not deterministic tools, they're not sandboxes or container runtimes or languages with capabilities models.

They're a way to run arbitrary commands.

It would be like saying that "xterm" should have a ".xtermnoexec" list of commands you can't run, or that VLC should have an option for actors it won't show.

terminals run shells which run commands, it's not really deeply aware of what commands your shell ultimately run, and it's not in xterm's job to setup a sandbox and strip out executables.

VLC displays pixels, it's not up to it to figure out if those pixels are a certain actor.

codex pipes text and tool calls back and forth between OpenAI's servers, and it barely understands what that text and those tool calls are, and especially if a given tool touched a file. If you want VLC to not display an actor, you need to add a layer on top of VLC to stop it displaying a list of movies. If you want codex to not display a file's contents, you need a layer on top of codex to prevent it going near that file.

Re:A way to exclude sensitive files issue still open for Ope... by SoftTalker on Sunday June 28, 2026 @10:52AM (#48707838)
bash actually has a "restricted" mode which is sort of like that. In restricted mode, the following are disallowed:

- Changing directories with cd.

- Setting or unsetting the values of SHELL, PATH, HISTFILE, ENV, or BASH_ENV.

- Specifying command names containing /.

- Importing function definitions from the shell environment at startup.

- Parsing the values of BASHOPTS and SHELLOPTS from the shell environment at startup.

... some other things mainly preventing you from escaping or disabling the restricted mode.

Re:A way to exclude sensitive files issue still open for Ope... by 8organicbits on Sunday June 28, 2026 @11:10AM (#48708016)
Does that work? I've never seen it used. It seems easy to escape.

The docs seem to suggest using alternate approaches.

> Modern systems provide more secure ways to implement a restricted environment, such as jails, zones, or containers.

https://www.gnu.org/software/bash/manual/html_node/The-Restr...

Re:A way to exclude sensitive files issue still open for Ope... by SoftTalker on Sunday June 28, 2026 @11:19AM (#48708115)
I don't think I've ever seen it used. I think the idea was back in the day when you wanted to let a user have a shell login (because that's the only way you could use a shared computer) but wanted to confine them to a specific directory and prevent them running anything that wasn't in the pre-defined PATH that you set for them.
Re:A way to exclude sensitive files issue still open for Ope... by ryoshu on Sunday June 28, 2026 @12:45PM (#48709033)
Can't you do that with regular Unix permissions?
Re:A way to exclude sensitive files issue still open for Ope... by tingletech on Sunday June 28, 2026 @12:50PM (#48709092)
You could also produce special purpose applications this way, say to provide access to the online library catalog, or a run a gopher client for use in a public terminal lab. Telnetting to a unix account running some sort of restricted shell was how these often worked.

A sibling comment I can't reply to asks if you can do with with unix permissions.

These were really intended for anonymous guest access, or at least often used for this purpose. You couldn't do the same things with the file permissions systems at the time.

Re:A way to exclude sensitive files issue still open for Ope... by 4ndrewl on Sunday June 28, 2026 @06:47PM (#48712546)
Back in the day we'd use chroot to achieve something similar

https://linux.die.net/man/1/chroot

Re:A way to exclude sensitive files issue still open for Ope... by SoftTalker on Monday June 29, 2026 @10:09AM (#48719488)
Yes, in reality you might use chroot, limited filesystem permissions, and a restricted shell as a belt-and-suspenders approach.
Re:A way to exclude sensitive files issue still open for Ope... by AdieuToLogic on Sunday June 28, 2026 @11:05PM (#48714321)
>> bash actually has a "restricted" mode ...

> Does that work? I've never seen it used. It seems easy to escape.

Yes, it does work for its intended purpose. It has often been used in combination with chroot[0] as well.

> The docs seem to suggest using alternate approaches.

>> Modern systems provide more secure ways to implement a restricted environment, such as jails, zones, or containers.

These approaches are not mutually exclusive with restricted shell use. For example, one could use FreeBSD jails to secure Apache httpd and/or Nginx and still employ a restricted shell to evaluate requests.

0 - https://man.freebsd.org/cgi/man.cgi?query=chroot&apropos=0&s...

Re:A way to exclude sensitive files issue still open for Ope... by 8organicbits on Monday June 29, 2026 @08:45AM (#48718566)
I'm seeing a ton of restricted mode escapes documented online, like https://0xffsec.com/handbook/shells/restricted-shells/ so I'm not so sure. When basic utilities like less, man, and awk can run subshells it's quite a mess.

Bash restricted mode needing a chroot may suggest that Claude also needs a chroot (or restricted file permissions, jail, etc).

Re:A way to exclude sensitive files issue still open for Ope... by AdieuToLogic on Monday June 29, 2026 @08:21PM (#48727065)
> Bash restricted mode needing a chroot may suggest that Claude also needs a chroot (or restricted file permissions, jail, etc).

I believe running coding agents within a jail/container is a "best practice" to limit their blast radius. At least, this is what people I respect have conveyed to me.

Re:A way to exclude sensitive files issue still open for Ope... by dns_snek on Sunday June 28, 2026 @12:37PM (#48708957)
> they're not sandboxes

Yes they can be, and Codex offers one. It uses Bubblewrap and seccomp on Linux which are perfectly capable of restricting filesystem access.

In a default setup every command is executed inside a restrictive sandbox and you're only asked for permission to run that command if the execution fails.

I don't necessarily think that it's a good idea to rely on these sandboxes as your only line of defense but that's absolutely a feature that they can, should, and do offer.

Re:A way to exclude sensitive files issue still open for Ope... by jxf on Sunday June 28, 2026 @10:24AM (#48707560)
.gitignore doesn't have the same security implications.

If you fail to prevent a private key from being added to your repository, you can reverse this and purge it from the blobs and reflog as if it never happened.

If you fail to prevent OpenAI from ingesting a private key, you have created a security incident.

Re:A way to exclude sensitive files issue still open for Ope... by tmp10423288442 on Sunday June 28, 2026 @01:19PM (#48709414)
> If you fail to prevent a private key from being added to your repository, you can reverse this and purge it from the blobs and reflog as if it never happened.

Only if you’re absolutely sure that it’s never been pushed to a public repository. I would treat a push of a private key to GitHub as a much higher emergency than it being sent to OpenAI (or even being accidentally used in a Google search), since there are bots that actively scan GitHub for private keys, such that your private key might be found within a few minutes of push.

Re:A way to exclude sensitive files issue still open for Ope... by throwatdem12311 on Sunday June 28, 2026 @04:05PM (#48711054)
Will git drop your production database because it feels like it when the stars align?
Re:A way to exclude sensitive files issue still open for Ope... by londons_explore on Sunday June 28, 2026 @09:58AM (#48707304)
I could imagine perhaps some system which rather than denying access might instead replace the key material from your .env key with "** redacted. This key material can be used via make, but can never be exfoltrated directly **" whenever that key is seen heading out towards the network...
Re:A way to exclude sensitive files issue still open for Ope... by brookst on Sunday June 28, 2026 @10:03AM (#48707348)
But that means the process can’t use the key for network requests, right?
Re:A way to exclude sensitive files issue still open for Ope... by mcintyre1994 on Sunday June 28, 2026 @10:12AM (#48707440)
OnePassword can do something like this where you put references to a path there instead of the key material, and then you wrap the invoke command with their CLI and it replaces them. So your local env file never has anything sensitive. A malicious agent could still exfiltrate if you give it access to debug tools on the running code though.
Re:A way to exclude sensitive files issue still open for Ope... by jgalt212 on Sunday June 28, 2026 @10:15AM (#48707463)
I'm a fan of belt and suspenders.
Re:A way to exclude sensitive files issue still open for Ope... by albedoa on Sunday June 28, 2026 @06:55PM (#48712622)
Where did you run off to little boy.
Re:A way to exclude sensitive files issue still open for Ope... by throwatdem12311 on Sunday June 28, 2026 @04:04PM (#48711034)
You expect Joe Blow vibe coder running Codex on his Dell to understand this?
Re:A way to exclude sensitive files issue still open for Ope... by matheusmoreira on Sunday June 28, 2026 @04:07PM (#48711073)
Yes.
Re:A way to exclude sensitive files issue still open for Ope... by throwatdem12311 on Sunday June 28, 2026 @04:09PM (#48711098)
lol I don’t you realize how tech illiterate most normies are
Re:A way to exclude sensitive files issue still open for Ope... by matheusmoreira on Monday June 29, 2026 @02:00AM (#48715395)
It's not that I don't understand, it's that I don't care. Normies routinely hurt themselves trying to do professional work. We don't blame the tools when that happens, we blame the normies.
Re:A way to exclude sensitive files issue still open for Ope... by datsci_est_2015 on Monday June 29, 2026 @08:01AM (#48718127)
“You didn’t even watch a single YouTube video before powering up that table saw?”