… and I just enhanced the FAQ with this explanation: 
https://github.com/pharo-vcs/iceberg/blob/master/README.md#faq 
<https://github.com/pharo-vcs/iceberg/blob/master/README.md#faq>

Esteban, killing the 3G roaming :P

> On 25 May 2017, at 23:31, Esteban Lorenzano <[email protected]> wrote:
> 
> again, ssh-agent is one way to authenticate. 
> it can be not the best but it is the only one we could implement with the 
> time we get (also, ssh-agent is “common” while others are platform specific 
> and then they will work just in the intended platform). With time, we want to 
> implement all, but for now is what we have.
> 
> One way to solve this *without* using ssh-agent (for example, something we 
> recommend now for windows, since ssh-agent has problems for people not used 
> to it) is to use “custom keys”, which now in iceberg is done in settings (as 
> explained on the FAQ), or running this: 
> 
> IceCredentialsProvider useCustomSsh: true.
> IceCredentialsProvider sshCredentials
>       publicKey: '/Users/esteban/.ssh/id_rsa.pub’;
>       privateKey: '/Users/esteban/.ssh/id_rsa’
> 
> of course, you need to modify paths to your user :)
> of course (2), you may add that to a startup action, so you do not need to 
> execute that each time. 
> 
> cheers, 
> Esteban
> 
>> On 25 May 2017, at 22:12, Stephane Ducasse <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> I retried
>> rename all the keys I put in my git account. 
>> 
>> But 
>> > ssh-add -K ~/.ssh/github_rsa
>> Error connecting to agent: No such file or directory
>> > ssh-add -K ~/.ssh/2016RSA
>> Error connecting to agent: No such file or directory
>> 
>> Apparently I should run
>> eval `ssh-agent -s`
>> Now I will try to republish on github. 
>> anyway I'm not using git in pharo for now. 
>> 
>> Stef
>> 
>> On Thu, May 25, 2017 at 8:20 PM, Alexandre Bergel <[email protected] 
>> <mailto:[email protected]>> wrote:
>> > I do not get why I can use github all the time and not with pharo.
>> 
>> That is an excellent question
>> 
>> Alexandre
>> 
>> 
> 

Reply via email to