Hi Michael,

I have seen that you have been resubmitting your keys again for some reason. 
First, I must say, without changing your keys, please do not resubmit as this 
does nothing. 

Bioconductor already has a key on file for you, (note, you SVN ID is 
m.zimmermann, spelled exactly like that) 

m.zimmermann                                                                    
                        

ssh-rsa 
AAAAB3NzaC1yc2EAAAADAQABAAABAQDXfq8/6yiczdTnZgDRqC4iQPDEyAUe/Kse0RKxXcamSgUb/QDmXGW+8PjKCxJJGl4BDX02ZDx5Iohj7d/808bguUyP6XWexFdeYR3mZrcfZAIZ9yfThURwyYr1oFxaW4XQ4pY6KbwOmn71kPZ1EOROZ/MxwU0byyYnabyEioWvsvBXBLJRYCWTgru1YQhY8u2xMzZEPEH2AsNGhGC2WZuJZMbxR1Q4FQQu2Repeqj8/iUJprQnkJXWcmtyJxDDdTaY+opFNw0H6CbgoUeA5qhGGwjTZIwtMwi0839DJDx6OwXY8tDxps60BAilqXcD/X9E3WLk+4L/hM7Nwx+o6By3


You have been submitting bad entries and these do not get carried over to the 
bios-git authentication system. 

1. Email: Email ID
2. SVN ID: m.zimmermann 
3. SSH key or Github ID: (ssh-rsa key) OR (MTZimmer)

Check the following items to make sure you are trying to fetch correctly,

1. If you use the private key associated to that public key, your verification 
should go through. This will show you your package and access rights,

        ssh -T g...@git.bioconductor.org 

2. Please make sure you are using the correct key with the SSH protocol.
        
        git remote -v


Best,

Nitesh


> On Sep 22, 2017, at 12:25 AM, Zimmermann, Michael T., Ph.D. 
> <zimmermann.mich...@mayo.edu> wrote:
> 
> Dear Nitesh,
> 
> Thank you for your help. My apologies for the confusion. 
> 
> After receiving your email, I tried fetching again, but was met with "host 
> key verification failed" message. So, I submitted correct svn and git IDs to 
> the Google form. Since then, I have tried to fetch upstream and continue to 
> get "host key verification failed."
> 
> Again, my apologies for my confusion - any help you can provide would be much 
> appreciated.
> 
> Sincerely,
> 
> 
> 
> -----Original Message-----
> From: Turaga, Nitesh [mailto:nitesh.tur...@roswellpark.org] 
> Sent: Wednesday, September 13, 2017 12:51 PM
> To: Zimmermann, Michael T., Ph.D.
> Subject: Re: Bad keys
> 
> Dear Michael,
> 
> We have this key on file for you,
> 
> ssh-rsa 
> AAAAB3NzaC1yc2EAAAADAQABAAABAQDXfq8/6yiczdTnZgDRqC4iQPDEyAUe/Kse0RKxXcamSgUb/QDmXGW+8PjKCxJJGl4BDX02ZDx5Iohj7d/808bguUyP6XWexFdeYR3mZrcfZAIZ9yfThURwyYr1oFxaW4XQ4pY6KbwOmn71kPZ1EOROZ/MxwU0byyYnabyEioWvsvBXBLJRYCWTgru1YQhY8u2xMzZEPEH2AsNGhGC2WZuJZMbxR1Q4FQQu2Repeqj8/iUJprQnkJXWcmtyJxDDdTaY+opFNw0H6CbgoUeA5qhGGwjTZIwtMwi0839DJDx6OwXY8tDxps60BAilqXcD/X9E3WLk+4L/hM7Nwx+o6By3
> 
> Under the SVN id “m.zimmerman”. Is this correct?  
> 
> There were multiple submissions with your GitHub ID(MTZimmer ) in the place 
> of SVN ID. This is breaking your submission because it is a fail safe to 
> prevent people from submitting keys, with the same name and getting access to 
> the package. 
> 
> Please refrain from doing this. 
> 
> Best,
> 
> Nitesh
> 
> 
>> On Sep 12, 2017, at 6:08 PM, Zimmermann, Michael T., Ph.D. 
>> <zimmermann.mich...@mayo.edu> wrote:
>> 
>> Dear Nitesh,
>> 
>> I am still having access trouble. As we previously communicated, I have 
>> resubmitted my ssh public key. Could you advise me on how I should proceed?
>> 
>> bash-4.1$ git remote -v
>> origin       https://github.com/MTZimmer/RITAN (fetch)
>> origin       https://github.com/MTZimmer/RITAN (push)
>> upstream     g...@git.bioconductor.org:packages/RITAN.git (fetch)
>> upstream     g...@git.bioconductor.org:packages/RITAN.git (push)
>> 
>> bash-4.1$ git fetch --all
>> Fetching origin
>> Fetching upstream
>> No RSA host key is known for git.bioconductor.org and you have requested 
>> strict checking.
>> Host key verification failed.
>> fatal: Could not read from remote repository.
>> 
>> Sincerely,
>> 
>> 
>> -----Original Message-----
>> From: Zimmermann, Michael T., Ph.D. 
>> Sent: Monday, September 11, 2017 8:06 AM
>> To: 'Turaga, Nitesh'
>> Subject: RE: Bad keys
>> 
>> Thank you, Nitesh, for this information and explanation. I just resubmitted 
>> my GitHub key with the tag. Please let me know if there is anything further 
>> I can provide.
>> 
>> Sincerely,
>> 
>> -----Original Message-----
>> From: Turaga, Nitesh [mailto:nitesh.tur...@roswellpark.org] 
>> Sent: Friday, September 08, 2017 11:32 AM
>> To: Samuel Wieczorek; Zimmermann, Michael T., Ph.D.; dcof...@fredhutch.org; 
>> nol...@nist.gov
>> Subject: Reg: Bad keys
>> 
>> Hi Maintainers,
>> 
>> You have submitted a key which is invalid, and part of the responsibility is 
>> on us. The google form was not accepting spaces in the ssh-key or GitHub id 
>> section, and this has been a mistake which has been fixed now.
>> 
>> The SSH public keys submitted are missing the “ssh-rsa” tag in the 
>> beginning, and this is required to identify the kind of ssh key being 
>> submitted i.e dds vs rsa. 
>> 
>> Please resubmit your keys completely, it should look like this, 
>> 
>> ssh-rsa 
>> AAAAB3NzaC1yc2EAAAADAQABAAACAQDbxkSoP0mAYI6KCrBm/OrIR5W9V6rJv0Ph2vicCGm0ymsQZx96WR026RhvzsX60g5VyZrD8hg6FcyZmwr2Ux8+SyyTRZzCQZKACQAAsk4hjrCl/aVlRQX62vpozIhIeR2qE+LW9pF5M5+O2LtAV593rm3uQ5jXuxmxSvzHzuvcdsmc7w8Ou4Bogy/gqdYQmlymkx27fjGz7HxwZRsXps+JN1zibllsw/VyXtyRPjAJE7XXXYG5aOYFbYN0kDdj+oTPpHcdkleVaMsl1LnINyjysJAyfMSwqQgiA/otiel8hSopOoLlpZxeXG1aEzqqJaXYRqZUWjIPThjaoMS2ktFf0N2S7thjz1D0tpK4xW5/wDyu1V4D+YBbzrASD38AxY4BDBlEtp5dqgfHkcSvSGEAyIMMD/a41VYGWpLC9UmqRu3wdLPW+A0WdmnTlwJnGBADk3JOBrliOISDHByFRAETl/u2ANOicXOfyosK+VbjPZ6iMfiJvU6LfqHPoASDOZCIhnUJT4vgDXXSiUnCmrq1+JNjQHt5Y7rfIPsWa21gOWVhusTqAMOzHpjxQ1wlKo2vHHpLD9DgNnl9xcxdps/zuneHHYnuvG26SufAW18CisKDuHTv58yp8cEBrLuhAJlxrpsigQJqOM+HS0uQTve6c2NT4yDJi6JA2Wr7BM7YL8w==
>>  nit...@blah.com
>> 
>> 
>> There is a space between the ssh-rsa(dds) identifier and the rest of the key.
>> 
>> 
>> 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.
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

Reply via email to