[dead]
Show HN: enveil – hide your .env secrets from prAIng eyes
41–50 of 152 posts
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#42The way I did it now is to put everything in 1Password and just use the `op://vault/item/field` references in .env or configs
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#43I think it would be best if AI agents would honor either .gitignore or .aiexclude ( https://developers.google.com/gemini-code-assist/docs/create... ).
The problem is, you cannot force the agent to do anything. A suitably motivated AI will work around any instructions or controls you put in place.
We could simply make the "view file" tool not able to see .env. Same for other "grep-like" tools.
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#44as you have stated 'And yes, this project was built almost entirely with Claude Code with a bunch of manual verification and testing.' this code is not copyright protected, therefore you are not allowed to apply a MIT LICENSE to this project.
That has not been established in the courts, at least not precisely enough to assert that for sure this project isn’t copyrightable.
“ But the decision does raise the question of how much human input is necessary to qualify the user of an AI system as the “author” of a generated work. While that question was not before the court, the court’s dicta suggests that some amount of human input into a generative AI tool could render the relevant human an author of the resulting output.”
“Thaler did not address how much human authorship is necessary to make a work generated using AI tools copyrightable. The impact of this unaddressed issue is worth underscoring.”
https://www.mofo.com/resources/insights/230829-district-cour...
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#45[dead]
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#46https://github.com/getsops/sops This software has done this for years
Came to say this.
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#47Alternative, and more robust approach is to give the agent surrogate credentials and replace them on the way out in a proxy. If proxy runs in an environment to which agent has no access to, the real secrets are not available to it directly; it can only make requests to scoped hosts with those. I’ve built this in Airut and so far seems to handle all the common cases (GitHub, Anthropic / Google API keys, and even AWS,…
That's great for API credentials but some secrets are ment for local use, like encryption keys.
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#48Alternative, and more robust approach is to give the agent surrogate credentials and replace them on the way out in a proxy. If proxy runs in an environment to which agent has no access to, the real secrets are not available to it directly; it can only make requests to scoped hosts with those. I’ve built this in Airut and so far seems to handle all the common cases (GitHub, Anthropic / Google API keys, and even AWS,…
This is cool! Solving the same problem (authority delegation to resources like Github and Gmail) but in a slightly different way at https://agentblocks.ai
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#49[deleted]
Re: Show HN: enveil – hide your .env secrets from prAIng eyes
#50[dead]