envkey
prs
envkey | prs | |
---|---|---|
9 | 7 | |
599 | 195 | |
7.8% | - | |
7.0 | 7.2 | |
2 months ago | about 2 months ago | |
TypeScript | Rust | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
envkey
-
Show HN: Envkey-VSCode ā Autocomplete/type-checking for env vars in 46 languages
envkey-vscode is a VSCode extension that provides autocomplete, type checking, and peek-on-hover for environment variables in 46 different programming languages. Instead of a typeless, error-prone blob, the environment now acts like a strongly-typed object in every language you work in.
Iāve been using this extension myself for a couple weeks now and it feels like a pretty significant upgrade to my development workflow, especially when working on integrations across multiple languages, so I thought it was worth showing you all.
envkey-vscode relies on EnvKey, an open-source, end-to-end encrypted configuration and secrets manager that is focused on security and ease-of-use. Itās cross-platform, can integrate with any language or host, and can be cloud-hosted or self-hosted. Getting a project integrated normally takes a couple minutes.
More on EnvKey: https://www.envkey.com
Building and testing it has been an interesting process, as I relied quite heavily on ChatGPT/GPT-4 to cover languages that Iām not very familiar with. It helped me to develop regexes to cover the common forms of environment access in each language, as well as to produce small test cases and Dockerfiles that can run them. While it took a lot of passes and tweaking to root out hallucinations and get each language right, I donāt think thereās any way I could have built a tool like this in a reasonable amount of time. Having a single `test` command that runs examples in dozens of languages is pretty amazingāsort of like a rudimentary version of Replit that runs locally.
All the code for the extension lives in EnvKeyās monorepo here: https://github.com/envkey/envkey/tree/main/public/sdks/tools...
Iām planning to write up a blog post on this process and what Iāve learned about how to get the most out of GPT on a polyglot coding project like this. If youāre interested, you can sign up to get notified here when this post is live: https://envkey.us15.list-manage.com/subscribe?u=623039cd8518...
-
PHP library for EnvKey: an open source, end-to-end encrypted configuration and secrets manager
envkey-source code is here: https://github.com/envkey/envkey/tree/main/public/sdks/envkey-source
-
Show HN: Gut ā An easy-to-use CLI for Git
If anyone needs help keeping secrets out of git, you could give EnvKey[1] a look (disclaimer: I'm the founder). It aims to keep all secrets out of the repo completely so that you can't be burned by forgetting to add something to .gitignore
It takes a few minutes to install and then all your secrets and config will be in the environment, and will stay automatically up-to-date when there are changes.
Might be a way to cut out that particular failure mode when using Gut (which looks interesting btw--kinda like Git: the good parts).
1 - https://github.com/envkey/envkey
-
Bitwarden Design Flaw
We took a similar approach to passphrase stretching in EnvKey[1] v1 (EnvKey is a secrets manager, not a passwords manager, but uses end-to-end encryption in a similar way). We used PBKDF2 with iterations set a bit higher than the currently recommended levels, as well as Dropbox's zxcvbn lib to try to identify and block weak passphrases.
Ultimately, I think it's just not good enough. Even if you're updating iteration counts automatically (which is clearly not a safe assumption, and to be fair not something we did in EnvKey v1 either), and even with safeguards against weak passphrases, using human-generated passphrases as a single line of defense is just fundamentally weak.
That's why in EnvKey v2, we switched to primarily using high entropy device-based keys--a lot like SSH private keys, except that on Mac and Windows the keys get stored in the OS keychain rather than in the file system. Also like SSH, a passphrases can optionally be added on top.
The downside (or upside, depending how you look at it) is that new devices must be specifically granted access. You can't just log in and decrypt on a new device with only your passphrase. But the security is much stronger, and you also avoid all this song and dance around key stretching iterations.
1 - https://github.com/envkey/envkey
2 - https://github.com/dropbox/zxcvbn
-
Seriously, Stop Using RSA
EnvKey[1] moved from OpenPGP(RSA) to NaCl for its v2, which recently launched.
Itās causing a difficult migration for our v1 users. Moving to a new encryption scheme is not fun for a product with client-side end-to-end encryption.
But within a year or so after releasing the v1, it seemed like the writing was on the wall for OpenPGP and RSA. I didnāt want to go down with a dying standard.
NaCl is so much better. In spite of the migration headaches that will likely cost us some users, Iām very happy I made this decision. Itās so much faster, lighter, and more intuitive.
Itās legitimately fun to work with, which I never thought Iād say about an encryption library after cutting my teeth on OpenPGP.
1 - https://github.com/envkey/envkey
-
Show HN: EnvKey 2.0 ā End-To-End Encrypted Environments (now open source)
The process management code lives here: https://github.com/envkey/envkey/blob/main/public/sdks/envke...
Basically the command you pass in to envkey-source is run via:
exec.Command("sh", "-c", c)
(c is the command you passed as a string.)
Stdout/stderr is piped through, and .Wait() is called on the command. If envkey-source is in watch mode, it will send a SIGTERM when the environment is updated, then re-run the process once the initial process has died. I can verify that, for example, if a server listening on ports is restarted in this way, the process will die and the ports will be cleared before the new process is started (this has been well-tested).
Do you see a problem with this approach? We will prioritize making all this bulletproof.
- EnvKey End-to-End Encrypted Environments Is Now Open-Source
prs
-
Bitwarden: Free, open-source password manager
I created `prs` which solves a lot of painpoints I had with pass and other clients.
It is compatible with pass and uses the very same store.
https://github.com/timvisee/prs
-
Bitwarden Design Flaw
Thanks for mentioning prs [1], dev here! :)
Yes it definitely meets those requirements, being written in Rust, supporting pass, TOTP, Tombs amongst other things.
Though its CLI is a bit different than classic pass. That is on purpose in fact, to achieve a better UX and less ambiguous commands.
[1]: https://github.com/timvisee/prs
-
Are we yeet yet?
prs has a hidden yeet to throw secrets/passwords away:
-
Pass: The standard Unix password manager
I've developed `prs` as `pass` alternative with many annoyances fixed for daily use. It provides automatic syncing between multiple devices through git, supports multiple keys and many other things. It simply uses your existing `pass` store.
Some might find it useful: https://github.com/timvisee/prs
-
Wayland in 2021
I've added Wayland (clipboard) support to prs recently. It's a pass compatible client like gopass.
-
Lastpass free limits to single device from March 16
Terminal gurus might like what I've been working on lately:
https://github.com/timvisee/prs
Free and open-source, keep control in your own hands, forever. Encryption with gpg, sync with git. Compatible with pass, which means better support and easy migration.
What are some alternatives?
vault-exfiltrate - proof-of-concept for recovering the master key from a Hashicorp Vault process
gopass - The slightly more awesome standard unix password manager for teams
tini - A tiny but valid `init` for containers
Retroactive - Retroactive only receives limited support. Run Aperture, iPhoto, and iTunes on macOS Sonoma, macOS Ventura, macOS Monterey, macOS Big Sur, and macOS Catalina. Xcode 11.7 on macOS Mojave. Final Cut Pro 7, Logic Pro 9, and iWork ā09 on macOS Mojave or macOS High Sierra.
Vault - A tool for secrets management, encryption as a service, and privileged access management
passforios - Pass for iOS - an iOS client compatible with Pass command line application.
dumb-init - A minimal init system for Linux containers
Pass4Win - Windows version of Pass (http://www.passwordstore.org/)
gut - An alternative git CLI for Windows, macOS, and Linux
pass-otp - A pass extension for managing one-time-password (OTP) tokens
gitless - A simple version control system built on top of Git
git-cli - A git CLI tool which can initialize a repository, add files, and commit files.