Gregory's ServerGithub: requires password/access token to clone public repos over HTTPS
Git: stores them unencrypted
Bash: makes it really hard to store them securely
Well played
 16 comments
@sitnik_ru yeah but the question is: is there really no way to clone public repo without auth?  @nikitonsky @sitnik_ru https? github doesn't ask for authentication for public repositories  @nikitonsky @sitnik_ru if you just want to clone public repository, use https, when you'd later decide to push, just replace remote origin with ssh  @nikitonsky What repo? I just cloned one of my public repos without authenticating. I even jumped to a new UID just to be sure it wasn't accessing any stored config.  @nikitonsky hmm, a basic `git clone` over HTTPS works for me without issues. I probably just don't understand exactly what do you mean by "without auth". Are you getting some form of password prompt or error when you try to clone?  @nikitonsky are you really really sure the repo is public? Works no problem here, cloned inside docker container isolated from any of my keys  @nikitonsky usually when this happens it's because I've typo-d the URL and GH is being secure and asking for a password in case I have access to a private repo of that name, rather than failing immediately My bad: I was using a non-existent URL and Github kept asking me for password. I googled the error and tried to set up auth instead of checking if I am even doing the right thing. Facepalm @nikitonsky It's happened to many of us/😅. The error message is rather misleading (although I can understand the rationale behind it) |
@nikitonsky if you switch from https to ssh you will have SSH key experience.
BTW, SSH key ≈ passkey. The same public/private key pair and even sort of password manager.