![]() ![]() More details about key generations at: ~/.ssh/config # github ![]() # also GitHub does not allow new keys with DSA anymore! # this only as a last resort option, should work everywhere: In decreasing order of preference and security: # prefer this if possible: If you working with GitHub you want to generate keys with the latest and greatest recommended algorithms: ssh-keygen -t ed25519 -C you work on other platforms, please check first, which algorithms are supported there. So let's tackle this lower level first: SSH Keys While git does support the HTTPS transport, in most cases you will use the more preferred way of talking git+ssh instead. Since GitHub makes it easy to keep using a single account while also being a member of an Enterprise organization, I haven't bothered testing it with a true multi-account configuration, but since you will use individual SSH and GPG keys for either way your computer won't really know the difference. The reasons are plenty and some will justify the need for what is described here.īy the way, this approach should work for both single and multiple GitHub accounts. »Why would I continue using my personal GitHub account on my work machine anyway?« - You may or may not be an open source contributor, and you may or may not use such open source software at your current employer's projects for example. So, if you cannot get rid of the first point and do need also access to your personal persona on GitHub (or any other git based hosting platform for that matter), this article might help you to achieve it. On Latacora you can find a nice compilation of things you need to consider and implement if you want to go big and sell your startup, but a lot of it could and should be done without that goal in mind. You better improve your setup now when it's still easy to do so. And part of it will be around security and compliance. If you do work in an early stage startup you might think that it would be excessive, but I promise you: if that company becomes successfull and grows and turns into a bigger deal like an enterprise, things will change. But not only is this my personal preference, partially also my workplace has some strictler rules, especially when it comes to security. I know, I know, this looks like a huge list of requirements. I want all of it happening as automatically as possible.I want to use the individual SSH keys based on the project I work on.I want separate SSH keys for each context (work, personal but also for each computer).I want to sign my commits with the individual GPG keys for each of the addresses.I want separate GPG keys for each email address. ![]() I want to use my work email address for the workplace stuff.I want to use my personal (and main) email address for my personal GitHub projects.The slightly more complex version control system configuration is due to the following requirements and expectations: The following blog post is a refined version of it. Recently I helped a coworker during onboarding with his machine setup and he asked me about this very same topic. ![]() For work I need some special care for my git config, since I want/need access to personal repositories. I work across 2 computers and 3 OS, all with nearly same development setup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |