Show HN: Dotenv Mask Editor: No more embarrassing screen leaks of your .env (opens in new tab)

I feel I see these solutions somewhat often, but you can execute a command and use that as a value. To me, I'm not sure why people aren't calling their secret store as part of it. I use direnv mostly, but seems `.env` supports the same thing. e.g:

MY_SECRET=$(pass show path/to/my/secret)

Of course substitute that for Vault/SSM/whatever. There are other solutions to this problem too, but I show this to people as there's so little friction to using it.

As for the solution itself, we shouldn't really be storing secrets as plain text wherever we can help it. Masking them feels like a kludge.

I recently got a phone with a high zoom level - once you factor in digital zooming it's 20x. The photo quality at that zoom level is trash, but it absolutely could be used to read text from people's laptop screens from across a big room, or even another building through a window.

Of course, real cameras have always had this kind of zoom level. The difference is that now, someone could appear to be browsing on their phone from very far away, but actually be reading text on your laptop screen.

It's much more likely they'll be looking for credit card details or something like that rather than .env secrets. But I guess it's better safe than sorry if you frequently work in a public, tech focused environment like a big coworking space.

We're talking someone sitting with their phone 50 meters away from you being able to read text on your laptop screen. That's about the distance where a person with good vision will struggle to recognize faces.

I recently made this as a component in a larger project https://gist.github.com/MatrixManAtYrService/7fc7fb05474d971...

The idea is that even if you can't see the full data for some reason (space constraints, in my case), different values will appear styled differently even if the non-hidden characters don't differ.

I'm not sure how easy/hard vscode makes this, bit it might be fun to use a hash of the secret (salted by that character's index) to determine the back/foreground colors of the *'s

That way even though you can't see the secret, you can tell that it has changed. Also you're in a position to notice if two hidden secrets are the same (this might clue the user into a mistake, like if they didn't actually copy what they think they copied and are instead pasting the previous thing.

Congrats on the launch! This resonates - I've dealt with the "accidentally exposed credentials during a demo" problem a lot.

The .env file is one of the most common culprits, but I've found the problem extends beyond just one file type. What I've learned:

The broader challenge: - .env files in code editors - Config files in various formats (YAML, JSON, TOML) - Database GUIs (showing connection strings, table data) - API tools (Postman, Insomnia showing auth tokens) - Browser tabs (logged into admin panels, showing URLs with tokens) - Terminal windows (commands with API keys) - Slack/email windows (messages with sensitive info)

Most solutions are file-type specific or app-specific. But during a screen share, the sensitivity context switches constantly - one moment you're in VS Code, next you're in a browser, then Postman, then back to the terminal.

How did you decide to focus on .env files specifically vs. trying to tackle the broader problem? Curious about your thinking on scope vs. coverage trade-offs.

Also, what's your approach to detecting what qualifies as a "secret" that needs masking? Pattern matching, or something more sophisticated?

Why would you have "production secrets" in a .env file in the first place? I feel like that's the real problem here.

> I've always had this fear of accidentally flashing my .env file with production secrets to the whole room (or recording).

Can't you just intersperse entries with multiple-screens-worth of blank lines, or add noisy variables?

I'm thinking that 120 blank lines at the beginning and the end might be enough though, no need to make the file really hard to use.

or, don't put secrets in .env files...

OMG,I wish I had this years ago!

Better than masking them in a file, get them out of the file entirely! Pull them declaratively instead - https://varlock.dev

This tool also redacts from your logs if working in js.