[Bioc-devel] Several ssh keys ?

[Martin Morgan]

On 10/02/2017 10:50 AM, Bernat Gel wrote:
> Don't want to be alarmist, but is there anything in place to prevent a 
> "malicious agent" inserting a new ssh key to the form and gaining access 
> to our git repo? Maybe it would be sufficient to send an email to the 
> maintainer whenever a new key is added so we have a clue something has 
> gone wrong?

yes, there are opportunities for gaining 'unintended' access. We're 
working on tightening these up.

Note that there is a mapping between the public key and the packages 
that the public key provides access to, and the mapping is not itself 
public.

Martin

> 
> Bernat
> 
> *Bernat Gel Moreno*
> Bioinformatician
> 
> Hereditary Cancer Program
> Program of Predictive and Personalized Medicine of Cancer (PMPPC)
> Germans Trias i Pujol Research Institute (IGTP)
> 
> Campus Can Ruti
> Carretera de Can Ruti, Camí de les Escoles s/n
> 08916 Badalona, Barcelona, Spain
> 
> Tel: (+34) 93 554 3068
> Fax: (+34) 93 497 8654
> 08916 Badalona, Barcelona, Spain
> bgel at igtp.cat <mailto:bgel at igtp.cat>
> www.germanstrias.org <http://www.germanstrias.org/>
> 
> <http://www.germanstrias.org/>
> 
> 
> 
> 
> 
> 
> 
> El 09/29/2017 a las 02:32 PM, Turaga, Nitesh escribió:
>> Hi,
>>
>> Good morning. You can do that.
>>
>> You have to add your new key to the google form. You can do that in 
>> two ways.
>>
>> 1. If you have submitted an SSH public key. (This is your case)
>>
>>      — Submit a new ssh public key to the google form, but with the 
>> same SVN ID and email address. The google form when it is processed 
>> will pick it up.
>>
>> 2. If you have submitted a Github ID(/ username) as a surrogate for us 
>> to fetch your SSH public keys for Github (located at 
>> www.github.com/<username>.keys),
>>
>>     — Add your new keys to the GitHub SSH key form 
>> (https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/). 
>>
>>
>>     — DO NOT add anything in the google form.
>>
>>     — When the form is processed again, it will add your new SSH keys 
>> to bioconductor.  You may add as many keys to GitHub as you want for 
>> access from different computers, and we’ll keep them all on file.
>>
>> Best,
>>
>> Nitesh
>>
>>
>>
>>> On Sep 29, 2017, at 4:38 AM, Samuel Wieczorek 
>>> <samuel.wieczorek at cea.fr> wrote:
>>>
>>> Hi
>>>
>>> I would like to work on two different machines with Git and
>>> Bioconductor. Is it possible to have two ssh keys ?
>>>
>>>
>>> Best regards
>>>
>>>
>>> Sam
>>>
>>> -- 
>>> *Samuel Wieczorek
>>>
>>> Etude de la Dynamique des Protéomes (EDyP)*
>>> *Laboratoire Biologie à Grande Echelle (BGE)*
>>> *U1038 INSERM / CEA / UGA*
>>> *Biosciences and Biotechnology Institute of Grenoble (BIG)*
>>> *CEA / Grenoble*
>>> *17 avenue des Martyrs*
>>> *F-38054 Grenoble Cedex 9*
>>> */Tél. : 04.38.78.44.14/*
>>> */Fax : 04.38.78.50.51/*
>>>
>>> http://www.edyp.fr/
>>>
>>>     [[alternative HTML version deleted]]
>>>
>>> _______________________________________________
>>> 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 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 at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
> 
> _______________________________________________
> 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}}