News for hackers. Stuff that matters.

A comment on SSH Keys on GitHub. Parent comment

Re:SSH Keys on GitHub by grhmc on Tuesday August 18, 2015 @11:59AM (#10079892)
No. There are valid cases to upload SSH keys and other certificates or secrets. Preventing it would be annoying, and near impossible to be very effective.

Just my $0.02.

[ Parent | on HN ]
Re:SSH Keys on GitHub by jethro_tell on Tuesday August 18, 2015 @12:02PM (#10079912)
I agree with you, but I can't imagine a use case for a secret that's not secret.
[ Parent | on HN ]
Re:SSH Keys on GitHub by mikegirouard on Tuesday August 18, 2015 @12:49PM (#10080313)
I believe Vagrant uses (or previously used) an insecure, public keypair[0] to keep things simple.

Aside from things like that, I can't see it being a _common_ use case.

[0]: https://github.com/mitchellh/vagrant/tree/master/keys

[ Parent | on HN ]
Re:SSH Keys on GitHub by swozey on Tuesday August 18, 2015 @12:06PM (#10079937)
They could be pointing to an environment variable or a number of things. I'm not sure if there's a good way for Github to deal with things like that without affecting at least some users.

edit:..I guess they could just validate that it's a key.

[ Parent | on HN ]
Re:SSH Keys on GitHub by benjarrell on Tuesday August 18, 2015 @12:20PM (#10080059)
There probably aren't many, howto and examples come to mind.
[ Parent | on HN ]
Re:SSH Keys on GitHub by jvoorhis on Tuesday August 18, 2015 @12:05PM (#10079933)
Certificates are not secrets.
[ Parent | on HN ]