Good day, I have submitted my public key a couple of months ago and am now trying to do some maintenance. The code I used is: git clone https://github.com/DarioS/ClassifyR.git cd ClassifyR git remote add upstream git at git.bioconductor.org:packages/ClassifyR.git git config core.sshCommand "ssh -i ~/SSHkeys/digiOcean" git checkout master git fetch upstream but I get an error. Permission denied (publickey). fatal: Could not read from remote repository. The key has the appropriate permissions. $ ls -l ~/SSHkeys/digiOcean -rw------- 1 dario dario 1675 Aug 5 2015 /home/dario/SSHkeys/digiOcean Copying the private key to ~/.ssh/ does not help. How can I do it? -------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia
[Bioc-devel] Fetuching Upstream Permission Denied
5 messages · Dario Strbenac, Martin Morgan
On 10/11/2017 08:00 PM, Dario Strbenac wrote:
Good day, I have submitted my public key a couple of months ago and am now trying to do some maintenance. The code I used is: git clone https://github.com/DarioS/ClassifyR.git cd ClassifyR git remote add upstream git at git.bioconductor.org:packages/ClassifyR.git git config core.sshCommand "ssh -i ~/SSHkeys/digiOcean" git checkout master git fetch upstream but I get an error. Permission denied (publickey). fatal: Could not read from remote repository. The key has the appropriate permissions. $ ls -l ~/SSHkeys/digiOcean -rw------- 1 dario dario 1675 Aug 5 2015 /home/dario/SSHkeys/digiOcean Copying the private key to ~/.ssh/ does not help. How can I do it?
The public key we have, and that allows write access to ClassifyR, ends with /met6XjCrGVZg1+sU6Tr2Y7aasdaGFeShqQkkJYi+aZ2x does that agree with digiOcean? If not, submit an updated public key with svn id d.strbenac Martin
-------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
This email message may contain legally privileged and/or...{{dropped:2}}
Good day, Yes, that's the end of the key digiOcean.pub. I also copied the private key to /tmp and re-generated the public key. The newly made public key is exactly the same as the one in ~/SSHkeys/ so the key pair matches. -------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia
On 10/11/2017 08:30 PM, Dario Strbenac wrote:
Good day, Yes, that's the end of the key digiOcean.pub. I also copied the private key to /tmp and re-generated the public key. The newly made public key is exactly the same as the one in ~/SSHkeys/ so the key pair matches.
if you say ssh -v git at git.bioconductor.org you might see something that suggests what is wrong, particularly finding the wrong ssh key; see FAQ #15 for how to configure ssh to use a particular key for a particular address http://bioconductor.org/developers/how-to/git/faq/
-------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
This email message may contain legally privileged and/or...{{dropped:2}}
Good day, Thanks for your help. In the end, export GIT_SSH_COMMAND='ssh -i ~/SSHkeys/digiOcean' did the trick. The write access is showing. R W packages/ClassifyR -------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia