awsume
git-crypt
awsume | git-crypt | |
---|---|---|
12 | 50 | |
475 | 7,978 | |
0.4% | - | |
7.5 | 0.0 | |
about 1 month ago | 3 months ago | |
Python | C++ | |
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.
awsume
-
Switch & Leapp-cli - AWS session management 100% command line
I have used awsume a long time. Then I got a new Macbook and lost 1/2 hour installing different python versions. So I programmed switchaws in go to get a single executable. And, yes: I declare guilty of the "not invented here" syndrom :) .
-
Script or software that automatically populate specific profile in ~/.aws/credentials
Bonus comment: After setting up your aws credentials, have a look at awsume, which makes rapid switches between accounts and roles a lot easier.. :)
-
Falling for Kubernetes
Has anyone on AWS gotten k9s to work with Awsume [0] authentication?
[0] https://awsu.me/
-
Learning AWS from a GCP Background
Learn how to WORK with AWS well, for instance set up Awsume (https://awsu.me/, install the Switch Roles extension (https://chrome.google.com/webstore/detail/aws-extend-switch-roles/jpmkfafbacpgapdghgdpembnojdlgkdl). Try to make working with it as painless as possible. I went through a long phase of bitching and hating AWS but I've recently just given in.
- Stop putting AWS credentials in the credentials file
- Script for cli commands with MFA and multiple accounts
-
My Most Loved AWS Developer Tools & Resources
Haven’t tried Leapp, not sure how I’d feel about needing to swap to a UI every time. I’m a huge fan of Awsume
-
AWS identity and access management
💡 When working with different accounts and/or roles and enabled MFA, it's recommendable to get some tooling support. I love working with AWSume in this case. It's easy to set up and really intuitive to work with.
-
My favourite CDK parameter for large deployments is...
Together with awsume and cdkstat I can have a terminal dashboard if a want to monitor the deployment on multiple accounts:
- How do you store and manage multiple access keys for your personal accounts?
git-crypt
-
Why Can't My Mom Email Me?
https://github.com/AGWA/git-crypt
And occasionally to encrypt files, or receive encrypted files.
These are practical things which are non-theoretical.
> Using multiple keys don't offer added security or secrecy.
Depends on how careful you are or want to be, with your private key. My house key isn't the same as my car key isn't the same as my bike key.
> This is nothing like data harvesting
Alright fair, bad example. What I was grumbling about was more the lack of any clear communication that you've been auto-opted-in to a feature on protonmail, with no user interface signal indicating so, leading to confusion for a couple months like in TFA. I definitely wasn't casting shade on the opengpg keyserver, nor protonmail. It's the "hey! I didn't check a box for this, and it's not mentioned anywhere in the protonmail docs" hidden functionality which could do with some clarification.
I'm a forgetful creature. If I intentionally put my key on a keyserver, because I'm playing around and learning about PGP, will I make the connection between it and protonmail a few months down the line if I move my email account to them? Unlikely.
It's a nice automated feature. Protonmail-to-protonmail e2e encryption makes a lot of sense. I just think protonmail-to-non-protonmail e2e needs a tooltip in the UI, and the option to opt out, potentially with the ability to opt out for specific email addresses. I wouldn't at all assume it would be on by default even IF I've been actively using PGP in my email clients, because it's something you usually have to manually set up yourself, very explicitly. That, and 99.9% of emails are plaintext.
Anyhoo, one thing I forgot which kind of negates the "what if I have multiple encryption keys tied to my email" is the fact that the opengpg keyserver does tie 1 email address to 1 key so you can't publish multiple encryption keys, fair enough. Git-crypt and file encryption, I set my associated email address to use +tags eg [email protected], so as far as protonmail etc are concerned there's only one key per logical email address.
-
Is it safe to commit a Terraform file to GitHub?
Apart from a few exceptions (like ansible for example, which supports native encryption), we moved away from encrypted secrets in git repos and use external things, depending on the platform (like parameter store / secrets manager for AWS or keyvault for Azure - both of these do track changes, btw), so I haven't looked for quite a while. Back in ye olden days we used https://github.com/AGWA/git-crypt which worked quite nicely, but the key management is cumbersome and it's based on GPG, which in itself is a bit of a light redish flag these days.
-
GitHub Private Repos Considered Private-Ish
How about encryption?
https://github.com/AGWA/git-crypt has been solid for me
-
Codeship jet alternative
You might want to check out git-crypt. It allows you to encrypt and decrypt files in a git repo without needing an external account, and supports .env files. That said, trying your hand at making one as a personal project could be a fun and rewarding experience!
-
Ask HN: Privacy-Conscious GitHub?
I hesitate to append this but one option I have seen thrown around and also debated is git-crypt [1] There are many caveats to doing this as any integrations that would need to read the file contents would also need to be able to decrypt the files so this may not be entirely useful and may add many levels of complexity and fragility.
[1] - https://github.com/AGWA/git-crypt
-
Vaults vs. Cryptomator? Security, Cloud syncing, integration?
The most interesting approach I've seen for this is https://github.com/AGWA/git-crypt
-
How can I Make this binary statically-linked?
Here is the Makefile.
I use git-crypt to encrypt files in git repositories quite a lot and I find that it doesn't work on RHEL-based distros because of some missing or out-of-date library. I need to build a statically linked binary.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
Store the Secrets in a repo using gitcrypt or another encryption tool.
-
I moved all my input files to a private repo and used it as a submodule
Consider using git-crypt for transparent encryption instead.
What are some alternatives?
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
git-secrets - Commit files with sensitive information like environment secrets safely encrypted in GitHub
saml2aws - CLI tool which enables you to login and retrieve AWS temporary credentials using a SAML IDP
sops - Simple and flexible tool for managing secrets
aws-extend-switch-roles - Extend your AWS IAM switching roles by Chrome extension, Firefox add-on, or Edge add-on
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
aws-toolkit-vscode - Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
dendron - The personal knowledge management (PKM) tool that grows as you do!
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere