On 19/08/15 09:05, Stefan Schmidt wrote:
> Hello.
>
> On 17/08/15 02:33, Bertrand Jacquin wrote:
>> Hi,
>>
>> On 17/08/2015 01:14, Stephen Houston wrote:
>>> Sorry can you provide a quick walk through of the steps to accomplish
>>> it?
>>> How to generate the new keys and commit and remove the old ones?
>>> Thanks. I
>>> could figure it out, but thought it might be helpful and get it done
>>> faster
>>> to give all the devs the steps to take.
>> Sure, here is it:
>>
>> $ ssh-keygen -t ed25519 -b <256|384|512>
>> Then enter a strong passphrase, pwqgen random=64 is a great tool.
>>
>> The public key will be present in ${HOME}/.ssh/id_ed25519.pub
>>
>> Clone the git repo containing all the devs keys:
>>
>> $ git clone git+ssh://g...@git.enlightenment.org/admin/devs.git
>> $ git rm devs/developers/${USER}/*
> ^ This is a really bad idea, no? It will remove your pictures, info.txt,
> etc as well.
>
> Did not happen to me but I have just seen it.Yes it is. You should just git rm *.pub and then add the new keys. Or better yet, just manually remove the offending keys (as you may have a few, and some may be good). -- Tom. ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
