> On 27 May 2017, at 03:42, Ben Coman <[email protected]> wrote:
> 
> 
> 
> On Fri, May 26, 2017 at 5:31 AM, Esteban Lorenzano <[email protected] 
> <mailto:[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. 
> 
> Maybe in some quick-start instructions this should be the default, so people 
> can prove to themselves
> it works, then move on to using ssh-agent which has more modes of failure.  
> Other apps like PuTTY
> do this...
> https://developers.openshift.com/images/overview-ssh-putty-configure-4.png 
> <https://developers.openshift.com/images/overview-ssh-putty-configure-4.png>  

but there is a settings there :)
(not as complete as that, but we should arrive)
what I’m thinking is to change the “default” to “ssh-agent or guess”: try to 
get the ssh-agent credentials, if that fails try to guess based on what is in 
default directory (.ssh) and if not then raise the exception. Is a hack, but I 
think it will work. 

Now, in fact ssh-agent works in 99% of the cases when you are out of windows 
(most people have it configured by default and with default options), the 
problem is that Stef does not do anything default (which is good, because then 
is a good border-case detector) :)

> 
> btw, I'm curious why the pub key is required?  Isn't it only needed at the 
> other (github) end?

no idea :)
I just know that libgit2 requires it 

cheers, 
Esteban

> 
> cheers -ben
> 
> 
> 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