[Bioc-devel] FW: BioC packages NuPoP and nuCpos
Turaga, Nitesh
N|te@h@Tur@g@ @end|ng |rom Ro@we||P@rk@org
Tue May 28 16:35:48 CEST 2019
Ok, now that we know that there remotes have been set up right, I'd like to also make sure that the private keys you are using correspond to the public keys we have on file.
cat */j.wang*
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDEqshGh957iQCZMOE3Ftuuh2raPyKGipFHnCqV7xzuW5vIhhB8P9B2VQGLs0bNvFmEhWCoxob5LJnOnP1dd51Ug0xceKvWiGIWZttNIqfATzgqqH2pkX4L21qudDb+6FYXxUzDvFjfw1Mxvn+qEXFrDr/mbe6Fv0YoCMmLd2edlxWS89YCtO6gYQasFs5wVJdKRZPxjT2PRPXB843KnHpj+9LB+tNHEHJj1fSHyNoSJiZigxjaBkVVt4Tr3KBHfE98cgwjbcvu2PTsNjZuMPfmqL+vDGqcrRQfU0VEFKbO5R/VRdmZulFlEotK9eZVHeE3RG8h9IqgWNXvyBEcvXz2qLvZiHm5hqeZ30Ha7b/AYGKX9Cp0RkdLK7EQzsHsogCP63W2dlWKeKfyscKsYOjuCqCGEA9mAD4+CpXBggvNsKgf9dHdMdTm7/ztPx9yyy6wC5mmTvZ4ngUPM5TNFkUMBPiWM8/oKfR4DHTRlqGX1lTNBtd+pgdIbE2WYnpDkHH2fS2LiCr/0QKz+rlJhRjF+8+gannzmsnJtd1GEm6ibAhDdRb6rSHh8Tqc6A0UYflw65p84lWzDqLsTz/gfBQTU37LmXgO+7oL9gsuYIccJUeb2hAGIiiWivhFCk+e4wA6wCyFgHUSRKLZprGgfWJG4wYMoLIzvz0AWDAXf2k9XQ==
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDejG1Q1diYAVW42NceCobh63b+riksaDYo4cmy74zSZP5xvzXat1FnIQLeUxIWUEoIpyMiX3wn/8rbSaPXFaA+3Biqf+/KX4dYPPJBcwVRxLmmtpNR4/ouI4m37tRwQzNfjjhSYnGkrPZwOy7cPh5HBGkw8wJOx/0PCM3HdlJVn/ArnBI7IE2ebHjNNYvO7ePqZwci2Ay4kVD4wJZPVid4c7crhFAGc5jiXcB6z0STNUQpMAyefpknncWQSO0P3WLoJ5uw2XJqrBJ6NK56bqFR+odffX95oAfgBhAQhon0dChkuurJxn3dD+dn1aiWA7K4fXF5XLrwQUw4g6Rcp1FizoarRFKHl+ZITTYgXBbb9fxEIpVQQvu+NbmyzCviHdfmXeRarubUztCXLFTwMisYlx2UzMkOgKEUd9UXwLuxi+zyncv98PrAbpUSWVRpuMQUBZ5qfx5qbfxhFX1ktOiDn050+6zekDFXTbsRubpmK3TQPt0uxGEqK4WJqWKYx+gjMsfk1s8OqvtsksIKv/byIhgFFi3mHgDOhLPOtKFgatp3t+Yk59ObYxLien7ATmC94WF4CA6OxeQTHB8++FGPyNoPrDjRzp29cdEupdkxrQXNH2b4oBp8YmrdAia5avhdQW/HdU2+7dE6bLMh7qq4wNxk+oUxZQkxUFqy4jDIBQ==
One way to make sure that your public keys are matching is,
1. Identify the private key which corresponds on your local machine in the .ssh directory. This command will recreate the public key, and it should match one of the two I have attached.
ssh-keygen -y -f ~/.ssh/<private_key>
2. When you have identified the key, force ssh to use that key,
ssh -i </path/private_key> -Tv git using git.bioconductor.org
If this doesn't work, please check to see that that permissions on your key are set to `chmod 400` (only the "user" has read permissions.)
Send the output of
`ssh -i <path/private_key> -Tvv git using git.bioconductor.org`
(if authentication doesn't work)
Best,
Nitesh
This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
More information about the Bioc-devel
mailing list