On Thu, Aug 31, 2017 at 11:23 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
you are all confused :)
Sean talks about storing the passphrase for SSH, not the HTTPS user/pass. Nevertheless both, passphrase and user/pass needs to be stored on Pharo and then they are not safe.
Now, how can we reliable store passwords in Pharo? This is a good thing we need to solve before blame Iceberg :P
So far, we can do just two things to avoid this problem:
- do not store the passwords on Pharo, which means we need to introduce them each time we use it (not very confortable⦠and btw this can be not working on ssh mode, I didnât test).
can we store them in the starting preferences?
- use ssh keys without password protection. I have to be honest: since I never used password protection of ssh keys in my life, I never seen this problem until Norbert pointed it to me :P
I will be glad to have a general solution for password storing in Pharo. But that would be like creating a keychain, isnât? Also, the openness of our system makes the problem even harder⦠:S
cheers, Esteban
On 31 Aug 2017, at 10:29, Denis Kudriashov <dionisiydk@gmail.com> wrote:
But ssh agent not working for you?
I work with Iceberg without extra configuration in image. No problems for me. But I am on Mac. So image now only keeps github password for pull requests.
(Only problem with latest Mac update is that I am now manually add ssh keys after any reboot: ssh-add -A).
2017-08-31 3:32 GMT+02:00 Sean P. DeNigris <sean@clipperadams.com>:
https://github.com/pharo-vcs/iceberg/blob/master/README.md suggests to configure Iceberg with the "Use Custom SSH Keys" setting, part of which seems to include pasting one's SSH Key Passphrase into Pharo's settings. Is that a good idea (i.e. is that safe)?
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html