[Bioc-devel] FW: BioC packages NuPoP and nuCpos

[Jiping Wang]

Hi Turaga, 

  I noticed there are two packages under my name (see below). But I should only have access to NuPoP. The other package was from a different contributor who has same initial as me (J. Wang, for Jing Wang). I don't whether that's the issue. The second key you listed below is my key.


Bioconductor Git Credentials

Logout
View User Profile
Which packages do I have access to?
'jzwang using northwestern.edu' has access to the following packages:

NuPoP
multiOmicsViz

~~~~~~~~~~
I followed your instruction below and still cannot go through it.  Here is the output. Thanks for your help.

bash-3.2$ ssh -i ./id_rsa -Tvv git using git.bioconductor.org
OpenSSH_7.9p1, LibreSSL 2.7.3
debug1: Reading configuration data /Users/jon/.ssh/config
debug1: /Users/jon/.ssh/config line 1: Applying options for git.bioconductor.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: Connecting to git.bioconductor.org port 22.
debug1: Connection established.
debug1: identity file ./id_rsa type 0
debug1: identity file ./id_rsa-cert type -1
debug1: identity file /Users/jon/.ssh/id_rsa type 0
debug1: identity file /Users/jon/.ssh/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to git.bioconductor.org:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256 using libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01 using openssh.com,ecdsa-sha2-nistp384-cert-v01 using openssh.com,ecdsa-sha2-nistp521-cert-v01 using openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01 using openssh.com,rsa-sha2-512-cert-v01 using openssh.com,rsa-sha2-256-cert-v01 using openssh.com,ssh-rsa-cert-v01 using openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305 using openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm using openssh.com,aes256-gcm using openssh.com
debug2: ciphers stoc: chacha20-poly1305 using openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm using openssh.com,aes256-gcm using openssh.com
debug2: MACs ctos: umac-64-etm using openssh.com,umac-128-etm using openssh.com,hmac-sha2-256-etm using openssh.com,hmac-sha2-512-etm using openssh.com,hmac-sha1-etm using openssh.com,umac-64 using openssh.com,umac-128 using openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm using openssh.com,umac-128-etm using openssh.com,hmac-sha2-256-etm using openssh.com,hmac-sha2-512-etm using openssh.com,hmac-sha1-etm using openssh.com,umac-64 using openssh.com,umac-128 using openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib using openssh.com,zlib
debug2: compression stoc: none,zlib using openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256 using libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305 using openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm using openssh.com,aes256-gcm using openssh.com
debug2: ciphers stoc: chacha20-poly1305 using openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm using openssh.com,aes256-gcm using openssh.com
debug2: MACs ctos: umac-64-etm using openssh.com,umac-128-etm using openssh.com,hmac-sha2-256-etm using openssh.com,hmac-sha2-512-etm using openssh.com,hmac-sha1-etm using openssh.com,umac-64 using openssh.com,umac-128 using openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm using openssh.com,umac-128-etm using openssh.com,hmac-sha2-256-etm using openssh.com,hmac-sha2-512-etm using openssh.com,hmac-sha1-etm using openssh.com,umac-64 using openssh.com,umac-128 using openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib using openssh.com
debug2: compression stoc: none,zlib using openssh.com
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: curve25519-sha256 using libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305 using openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305 using openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:nXILc5fVCnDfOID8HgPi+mSufGtr2JMYgnRa1JAQj/Q
debug1: Host 'git.bioconductor.org' is known and matches the ECDSA host key.
debug1: Found key in /Users/jon/.ssh/known_hosts:12
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: Will attempt key: jzwang using northwestern.edu RSA SHA256:nc2fGtrZqacQSdyJcLKJx9r7wylfJZ/IOe1qqlTLizg agent
debug1: Will attempt key: ./id_rsa RSA SHA256:QMfMFVkforhZObNtnpFc0Asy53n3NaHyorKgV4yL2fM explicit
debug1: Will attempt key: /Users/jon/.ssh/id_rsa RSA SHA256:QMfMFVkforhZObNtnpFc0Asy53n3NaHyorKgV4yL2fM explicit
debug2: pubkey_prepare: done
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: jzwang using northwestern.edu RSA SHA256:nc2fGtrZqacQSdyJcLKJx9r7wylfJZ/IOe1qqlTLizg agent
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: ./id_rsa RSA SHA256:QMfMFVkforhZObNtnpFc0Asy53n3NaHyorKgV4yL2fM explicit
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: /Users/jon/.ssh/id_rsa RSA SHA256:QMfMFVkforhZObNtnpFc0Asy53n3NaHyorKgV4yL2fM explicit
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
git using git.bioconductor.org: Permission denied (publickey).
bash-3.2$




On 5/28/19, 9:35 AM, "Turaga, Nitesh" <Nitesh.Turaga using RoswellPark.org> wrote:

    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.