4 ms·
Why would you want to disable it? They're not 'scare-quote' public, they're just public - analogous (kind of craply but workably) to 'distributing' your face, b
by OJFord 5y ago
Why would you want to disable it? They're not 'scare-quote' public, they're just public - analogous (kind of craply but workably) to 'distributing' your face, but not your passport/driving licence/etc.
The private key part is secret of course, never shared (that's where the analogy above breaks) but the public part is fine and desirable for everyone to have access to - that's how they verify that you signed something with your private key, how they encrypt a secret message to you.
- Djrhfbfnsks 5y agoBecause they may be used to learn the identity of an otherwise pseudoanonymous github account if one uses the same keys with another account that is tied to his real identity.
- pmontra 5y agoOne key per service. I've got a directory full of them and a long .ssh/config
- OJFord 5y agoIf the account is intended to be anonymous, it should have its own keypair not shared with the real identity (or other independently anonymous account). I say this regardless of whether public keys are being.. publicised. User database could be leaked, say, or public keys visible to employees/logged. OpenSSH literally refers to them as 'identities' - if you're trying to be anonymous/anon w.r.t. another it goes without saying that you need to not use the same identity!
- b3morales 5y agoI don't much want my face automatically associated with my GitHub (or other) account, either.