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).
- 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
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).