On 27 May 2017, at 03:42, Ben Coman <btc@openInWorld.com> wrote:On Fri, May 26, 2017 at 5:31 AM, Esteban Lorenzano <estebanlm@gmail.com> 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 sshCredentialspublicKey: '/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 themselvesit works, then move on to using ssh-agent which has more modes of failure. Other apps like PuTTYdo this...
btw, I'm curious why the pub key is required? Isn't it only needed at the other (github) end?
cheers -bencheers,EstebanOn 25 May 2017, at 22:12, Stephane Ducasse <stepharo.self@gmail.com> wrote:I retriedrename all the keys I put in my git account.But> ssh-add -K ~/.ssh/github_rsaError connecting to agent: No such file or directory> ssh-add -K ~/.ssh/2016RSAError connecting to agent: No such file or directoryApparently I should runeval `ssh-agent -s`Now I will try to republish on github.anyway I'm not using git in pharo for now.StefOn Thu, May 25, 2017 at 8:20 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:> I do not get why I can use github all the time and not with pharo.
That is an excellent question
Alexandre