[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 19:47:34 CEST 2019


I see, I based my assumption that you access Github via HTTP protocol as per your remotes.

bash-3.2$ git remote -v
origin	https://github.com/jipingw/NuPoP (fetch)
origin	https://github.com/jipingw/NuPoP (push)
upstream	git using git.bioconductor.org:packages/NuPoP (fetch)
upstream	git using git.bioconductor.org:packages/NuPoP (push)

If you are able to get SSH access to GitHub via the same key pair, these are mirrored on to the Bioconductor git server as well. I'm back at square one as per helping you debug this issue. 

Can you try maybe a brand new key, and a different computer (even a VM will do if you have access to one).

Best,

Nitesh 



> On May 28, 2019, at 1:43 PM, Jiping Wang <jzwang using northwestern.edu> wrote:
> 
> Hi Nitesh, 
> 
>   Thanks for help. I am confused about " It seems you authenticate to GitHub using HTTP protocol, so most likely you enter a password."
> 
> When I do ssh to github, I received he authentication. Does it mean I am not using HTTP? I thought I am using SSH here. I didn't enter password either.
> 
> Jipings-MacBook-Pro-2:.ssh jon$ ssh -T git using github.com 
> Hi jipingw! You've successfully authenticated, but GitHub does not provide shell access.
> 
> 
> 
> On 5/28/19, 12:39 PM, "Turaga, Nitesh" <Nitesh.Turaga using RoswellPark.org> wrote:
> 
>    At this point, I'd suggest two things,
> 
>    1. Create a new key, and try to use that new key by adding it in your BiocCredentials account. 
> 
>    2. Use a different computer? It might be something else entirely which we are missing. 
> 
>    I've double checked everything on Bioconductor's end of things, and it is configured correctly. 
> 
>    I've also noticed that you don't actually use your keys to get access to your Github account as well. It seems you authenticate to GitHub using HTTP protocol, so most likely you enter a password. I would also try to first authenticate with Github via the SSH key you are using.
> 
>    Best,
> 
>    Nitesh 
> 
> 
>> On May 28, 2019, at 1:31 PM, Jiping Wang <jzwang using northwestern.edu> wrote:
>> 
>> Still not working (my current key file is id_rsa, the other is the old one):
>> 
>> ~~~~~~~~~~~~~~~~`
>> Jipings-MacBook-Pro-2:.ssh jon$ ls -lht
>> total 64
>> -rw-r--r--  1 jon  staff    98B May 24 20:02 config
>> -rw-r--r--  1 jon  staff   228B May 24 19:47 config.back
>> -rw-r--r--  1 jon  staff   5.3K May 24 14:32 known_hosts
>> -r--------  1 jon  staff   749B May 24 14:15 id_rsa.pub
>> -r--------  1 jon  staff   3.3K May 24 14:15 id_rsa
>> -r--------  1 jon  staff   749B May 24 08:21 JWangNUGitHub.pub
>> -r--------  1 jon  staff   3.4K May 24 08:21 JWangNUGitHub
>> 
>> ~~~~~~~~~~~~~~~~~~~~~~~
>> Here is my config file:
>> 
>> host git.bioconductor.org
>> HostName git.bioconductor.org
>> IdentityFile ~/.ssh/id_rsa
>> User git
>> 
>> On 5/28/19, 11:52 AM, "Turaga, Nitesh" <Nitesh.Turaga using RoswellPark.org> wrote:
>> 
>>   What are the permissions on your SSH private key?
>> 
>>   Can you see what the permissions look like?
>> 
>>   	cd .ssh
>> 
>>   	ls -lht 
>> 
>>   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.
>> 
>> 
> 
> 
> 
>    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.
> 



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