3 ms·
I'll just add some things I think are missing: * Here's GitHub's guide: https://docs.github.com/en/authentication/connecting-to-github-with-ssh https://docs.gi
by iamwpj 5y ago
I'll just add some things I think are missing:
* Here's GitHub's guide: https://docs.github.com/en/authentication/connecting-to-github-with-ssh https://docs.github.com/en/authentication/connecting-to-gith...
> Before I get killed here for using Excel files for credential storage please note that I have about thirty+ years of excellent experience going that way, have tons of managed credentials and think that millions of users have similar practices.
That's not true and even if it was, it's not a justification to do anything. You know it's wrong, but to be honest it's not my job to convince you that you should be using the right tool for the right job.
What steps did you take to research a good solution on your own? How do the responses here compare? Do you think that asking questions here will have an effect on how you see your current workflow?
- weezee 5y ago> You know it's wrong not quite wrong. Maybe not the most secure way. It worked and saved my life when password need to be changed, needed to get a more secure pattern, got lost and so on. > Do you think that asking questions here will have an effect on how you see your current workflow? Hmmm. Good feedback. My workflow gets disturbed by Github and Bitbucket, so I have to change it. I just try to learn from the community how to handle this requirements. Every developer has to find a way to handle secrets and it is not universally solved yet what is the best way. And additionally it changes from time to time.