[Bioc-devel] problem with git / svn transition: ssh keys

Luo Weijun luo_weijun at yahoo.com
Tue Sep 12 19:26:30 CEST 2017


Well, I modified the file acces by:
chmod 400 ~/.ssh/id_rsa

it goes further, but the passphrase I stored seems not work (as below). I couldn’t change passphrase either due to the same problem. Can I remove the old ssh key, regenerated/resubmit a new key? What’s the best way to proceed?

luo$ git clone git at git.bioconductor.org:packages/pathview
Cloning into 'pathview'...
Enter passphrase for key '/Users/luo/.ssh/id_rsa': 
Enter passphrase for key '/Users/luo/.ssh/id_rsa': 
Enter passphrase for key '/Users/luo/.ssh/id_rsa': 
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

--------------------------------------------
On Tue, 9/12/17, Turaga, Nitesh <Nitesh.Turaga at RoswellPark.org> wrote:

 Subject: Re: problem with git / svn transition: ssh keys

 Cc: "Morgan, Martin" <Martin.Morgan at RoswellPark.org>, "Bioc-devel" <bioc-devel at r-project.org>
 Date: Tuesday, September 12, 2017, 12:39 PM

 http://bioconductor.org/developers/how-to/git/faq/

 You need point#16 on the FAQ section. 

 Change your permissions. 

 > On Sep 12, 2017, at 12:35 PM, Luo

 wrote:
 > 
 > The original file name was
 id_rsa.pub.pub.
 > I changed it to id_rsa.pub or
 id_rsa now. It stops complaining about the invalid format,
 but still have permission problem.
 > 
 > ##id_rsa.pub
 > luo$ git clone git at git.bioconductor.org:packages/pathview
 > Cloning into 'pathview'...
 > Permission denied (publickey).
 > fatal: Could not read from remote
 repository.
 > 
 > Please make sure you have the
 correct access rights
 > and the repository exists.
 > 
 > ##id_rsa
 > git clone git at git.bioconductor.org:packages/pathview
 > Cloning into 'pathview'...
 >
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 > @        
 WARNING: UNPROTECTED PRIVATE KEY FILE!     
     @
 >
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 > Permissions 0644 for
 '~/.ssh/id_rsa' are too open.
 > It is required that your private
 key files are NOT accessible by others.
 > This private key will be ignored.
 > Load key "~/.ssh/id_rsa": bad
 permissions
 > Permission denied (publickey).
 > fatal: Could not read from remote
 repository.
 > 
 > Please make sure you have the
 correct access rights
 > and the repository exists.
 > 
 >
 --------------------------------------------
 > On Tue, 9/12/17, Turaga, Nitesh
 <Nitesh.Turaga at RoswellPark.org>
 wrote:
 > 
 > Subject: Re: problem with git /
 svn transition: ssh keys

 > Cc: "Morgan, Martin" <Martin.Morgan at RoswellPark.org>,
 "Bioc-devel" <bioc-devel at r-project.org>
 > Date: Tuesday, September 12, 2017,
 12:20 PM
 > 
 > What name did you store your key
 > under? “id_rsa” or something
 else?
 > 
 > Nitesh
 > 
 >> On
 > Sep 12, 2017, at 12:11 PM, Luo

 > wrote:
 >> 
 >> the
 > following the are commands I used
 and output:
 >> 
 >> luo$ git clone git at git.bioconductor.org:packages/pathview
 >> Cloning into 'pathview'...
 >> key_load_public: invalid
 format
 >> Permission denied
 (publickey).
 >> fatal: Could not read from
 remote
 > repository.
 >> 
 >> 
 > Please make sure you have the
 correct access rights
 >> and the repository exists.
 >> luo$  ssh -T git at git.bioconductor.org
 >> key_load_public: invalid
 format
 >> Permission denied
 (publickey).
 >> 
 >> Is it because the
 > ssh key is still not in the right
 format because the suffix

 > was removed as I mentioned in
 previous email?
 >> 
 >> BTW, my ssh key
 > should be associated with gage
 package too.
 >> 
 >> 
 >
 --------------------------------------------
 >> On Tue, 9/12/17, Turaga,
 Nitesh <Nitesh.Turaga at RoswellPark.org>
 > wrote:
 >> 
 >> Subject:
 > Re: problem with git / svn
 transition: ssh keys

 >> Cc: "Morgan, Martin" <Martin.Morgan at RoswellPark.org>,
 > "Bioc-devel" <bioc-devel at r-project.org>
 >> Date: Tuesday, September 12,
 2017, 11:47
 > AM
 >> 
 >> Your key is in
 > our system. It
 >> starts with,
 >> 
 >> ssh-rsa
 >> 
 >
 AAAAB3NzaC1yc2EAAAADAQABAAACAQD4+kbkP7J0rkIGy81r9fO+4tCgHzQXfkthRu/MFPE7AMvZy7SeNf9WuxPQtMeOjAl
 >> 
 >> It is associated
 > with the
 >> correct package
 “pathview”
 > and also “gageData”. 
 >> 
 >> Please give me more
 >> 
 > information to help you. Show me
 the exact commands you
 > are
 >> running. 
 >> 
 >> i.e 
 >> 
 >>      git clone
 git at git.bioconductor.org:packages/pathview
 >> 
 >> If that doesn’t
 > work,
 >> then,
 >> 
 >>      ssh -T git at git.bioconductor.org
 >> 
 >> 
 >> Check out put for
 >> 
 > “pathview” package. Please
 also send the email to
 >> Bioc-devel. 
 >> 
 >> Best,
 >> 
 >> Nitesh
 >> 
 >> 
 >>> On Sep 12, 2017,
 > at 11:39

 >> wrote:
 >>> 
 >>> Nitesh,
 >>> I
 > resubmit my ssh public key based
 on your
 >> suggestion last Friday. But I
 still cannot
 > git clone my
 >> package respository. The
 > same error remain as below. Can
 you
 >> 
 > check into this?
 >>> Weijun
 >>> 
 >>> Cloning
 > into
 >> 'pathview'...
 >>> key_load_public:
 >> 
 > invalid format
 >>> Permission denied
 >> (publickey).
 >>> 
 > fatal: Could not read from
 >> remote
 > repository.
 >>> 
 >>> Please make sure you have
 the
 > correct
 >> access rights
 >>> and the repository
 >> exists.
 >>> 
 >>> 
 >> 
 >
 --------------------------------------------
 >>> On Fri, 9/8/17, Luo Weijun

 >> wrote:
 >>> 
 >>> Subject:
 >> Re:
 > problem with git / svn transition:
 ssh keys
 >>> To: "NiteshTuraga" <Nitesh.Turaga at RoswellPark.org>
 >>> Cc: "MartinMorgan" <Martin.Morgan at RoswellPark.org>
 >>> Date: Friday, September 8,
 2017,
 > 12:23
 >> PM
 >>> 
 >>> Nitesh,
 >>> I
 > just submitted it. The problem is
 >>> 
 > gone indeed.
 >>> Could
 >> you process my request and
 assign
 >>> me
 >> the git
 > access? Thanks.
 >>> Weijun
 >>> 
 >>> 
 >> 
 >
 --------------------------------------------
 >>> On Fri, 9/8/17, Turaga,
 Nitesh <Nitesh.Turaga at RoswellPark.org>
 >>> wrote:
 >>> 
 >>>    Subject: Re:
 problem with git /
 > svn
 >>> transition: ssh keys
 >>>    To: "Luo

 >>>    Cc: "Morgan,
 Martin"
 > <Martin.Morgan at RoswellPark.org>
 >>>    Date: Friday,
 September 8, 2017,
 >> 10:31
 >>> AM
 >>> 
 >>>    Hi
 > Weijun,
 >>> 
 >>>  
 >  I understand this was a
 problem
 >>> 
 > earlier on our
 >>>    end,
 >> and it has been fixed. 
 >>> 
 >>>    Is it
 > still the case that it gives
 >>> the
 >>>    “Github ID
 >> 
 > cannot contain spaces”
 >>> error? If
 > so,
 >> can you
 >>>   
 > take a screen shot and send
 >> it to
 > me.
 >>> I’ve tried it a few
 >>>    times and it
 does not give me
 > that
 >>> error anymore.
 >>> 
 >>>    Nitesh
 > 
 >>> 
 >>> 
 >>>> On Sep 8, 2017,
 >> at 10:22
 >>>    AM,

 >>>    wrote:
 >>>> 
 > 
 >>>> Nitesh,
 >>>> As I
 >> 
 > mentioned previously, I
 >>> tried to
 >>>    submit with
 the prefix ssh-rsa,
 > but
 >> it
 >>> always
 > complained
 >>>    that
 “Github ID
 > cannot contain
 >>> spaces” since
 > there is a
 >>>    space
 following
 > ssh-rsa. I guess it
 >>> will allow me
 > submit if
 >>>    I remove the
 empty
 > space, but would
 >>> that be a
 > functional ssh
 >>>    key?
 >>>> BTW, the
 >> web
 > form error“Github
 >>>    ID cannot
 >> contain spaces” seem to
 >>> wrong as this
 >> is
 > ssh key
 >>>    submission.
 >>>> Weijun
 >>>> 
 >>> 
 >>>> 
 >>> 
 >>> 
 >> 
 >
 --------------------------------------------
 >>>> On Thu, 9/7/17,
 Turaga, Nitesh
 >>> <Nitesh.Turaga at RoswellPark.org>
 >>>    wrote:
 >>>> 
 > 
 >>>> Subject:
 >>>    Re:
 >> problem
 > with git / svn transition:
 >>> ssh
 >> keys
 >>>> To:
 > "Luo Weijun"

 >>>> Cc: "Morgan, Martin"
 > <Martin.Morgan at RoswellPark.org>
 >>>> Date: Thursday,
 September 7,
 >>> 2017, 5:20
 >>>   
 > PM
 >>>> 
 >>>> Hi Luo,
 >>>> 
 >>>> The
 > key we
 >> have on
 >>>    file is
 missing the
 >> starting
 >>>> 
 > `ssh-rsa`.
 >>>    Could you
 please
 > resubmit? 
 >>>> 
 >>>> Best,
 >>>> 
 > 
 >>>> Nitesh
 >>>> 
 >>>> 
 >>>>> 
 >>>> 
 > On Sep
 >> 7, 2017, at 5:04 PM, Luo
 >>> Weijun
 >>>   

 >>>> wrote:
 >>>>> 
 >> 
 >>>>> Just want
 >>>> to make
 >>>  
 >  sure
 >> that you see my email below.
 I
 >>> still
 >> have the
 >>>> same problem at this
 >> time.
 >>>>> 
 > Weijun
 >>>>> 
 >>>>> 
 >>>> 
 > 
 >>> 
 >>> 
 >> 
 >
 --------------------------------------------
 >>>>> On Wed, 9/6/17,
 Luo Weijun

 >>>> wrote:
 >>>>> 
 >> 
 >>>>> Subject:
 >>>> problem
 >>>  
 >  with
 >> git / svn transition: ssh
 keys
 >>>>> 
 >> 
 >>>    To:
 "NiteshTuraga" <Nitesh.Turaga at RoswellPark.org>
 >>>>> Cc: "Martin
 > Morgan"
 >> <martin.morgan at roswellpark.org>
 >>>>> Date: Wednesday,
 September
 > 6,
 >>> 2017,
 >>>  
 >  11:32
 >>>> AM
 >>>>> 
 >>>>> Dear
 >>>> 
 >> Nitesh,
 >>>>> I submitted my
 ssh
 >> keys
 >>>> 
 > online
 >>>>> yesterday.
 >>>   
 >> However, I
 > still
 >>>> cannot git clone
 >> my
 >>>    packages
 >>>>> from
 >>>> 
 >>>   
 > github. Could you help me?
 Thanks!
 >>>>> 
 >>>   
 > The
 >>>> error message below
 see
 > to
 >>>>> complained
 >>>> the
 >>>   
 > public key
 >> format. My ssh public key
 >>> looks
 >>>>> 
 > like: 
 >>>>> 
 >>>    ssh-rsa
 >>>> AAAAB3NzaC1y….FHQ==

 >>>>> but the google web
 form
 >>> always
 >>>>> 
 >> 
 > complained “Github ID
 >>> cannot
 >>>    contain
 >>>> 
 >> spaces”.
 > So I
 >>>>> removed the
 >> prefix and
 >>>> 
 > suffix parts:
 >> "ssh-rsa "
 > and

 >>>>> it got through
 after that. 
 >>>>> Weijun
 >>>>> 
 >>>>> 
 >>>>> $ git clone
 >>>   
 >> git at git.bioconductor.org:packages/pathview
 >>>>> Cloning into
 >> 'pathview'...
 >>>>> 
 >> 
 > key_load_public: invalid
 >>> format
 >>>>> Permission denied
 >>> (publickey).
 >>>>> 
 >> fatal:
 > Could not read from
 >>> remote
 >>>>> repository.
 >>>>> 
 >>> 
 >>>>> Please make sure
 you have
 >>> the
 >>>   
 > correct
 >>>>> access rights
 >>>>> and the
 >>>> 
 >> 
 >>>    repository
 exists.
 >>>> 
 >>>> 
 >>>> 
 >>>> 
 > 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.
 > 
 > 
 > 
 > 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