- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

by Stephane Ducasse

On Thu, Aug 31, 2017 at 11:23 AM, Esteban Lorenzano <estebanlm(a)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(a)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(a)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 >> > >

Aug. 31, 2017

Re: [Pharo-dev] slow Pharo downloading and Travis

by Marcus Denker

> On 31 Aug 2017, at 16:56, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Peter UhnÃ¡k wrote >> over the past week+ downloading the latest Pharo 6 version has been >> extremely slow -- 5+ minutes to download the zip. > > I don't know if this is related, but Launcher just took several minutes to > "Fetch source files for Pharo 6.0" when I tried to launch an imageâ¦ > > I know have opened a ticket to see if the admins know of any Inria related networking issues. Marcus

Aug. 31, 2017

Re: [Pharo-dev] slow Pharo downloading and Travis

by Sean P. DeNigris

Peter UhnÃ¡k wrote > over the past week+ downloading the latest Pharo 6 version has been > extremely slow -- 5+ minutes to download the zip. I don't know if this is related, but Launcher just took several minutes to "Fetch source files for Pharo 6.0" when I tried to launch an imageâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 31, 2017

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

by Sean P. DeNigris

Oops, misfire. Let me try that againâ¦ Peter UhnÃ¡k wrote > Just about as safe as storing credentials for SmalltalkHub. (and to be > fair, STHub is even worse in that the connection is not encrypted. Imagine > someone observing traffic on PharoDays/ESUG conf.) That is exactly why I originally moved all my projects to GitHub and have tried to fork as many of the outside projects I use there as well (of course the fork part is practically impossible to keep up). ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 31, 2017

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

by Sean P. DeNigris

Peter UhnÃ¡k wrote > Just about as safe as storing credentials for SmalltalkHub. (and to be > fair, STHub is even worse in that the connection is not encrypted. Imagine > someone observing traffic on PharoDays/ESUG conf.) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 31, 2017

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

by Norbert Hartl

> Am 31.08.2017 um 12:52 schrieb Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > So you do not put passphrases on your ssh keys? > > Not always. > > Because you don't give the private key away why protect it? So imagine you have development process that includes a jenkins that needs to build the source and therefor needs access to the repository. What do you do? > > I give it a password-less ssh key, encrypted in some manner. (I do not know what Jenkins offers, but both Travis and GitLab(Runner) support file/data encryption.) > Adding the build server a password on top of the key would make no difference. If you have access to one, you have the access to the other. > So deal with it outside of the image. It is the same situation as a sandbox and key chain access. Exactly what I was meaning. Norbert

Aug. 31, 2017

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

by Tim Mackinnon

To further her add to what Peter is saying - in GitLab you can add secret variables (which are encrypted) and can be referenced only during the build process. So you can call your image with the value of one of these variables. Which is fine if you don't persist the value. I'm wondering if we have a concept of "transient" variables that don't persist on image save? Then iceberg could use one of those, and expect you to pass that value through on the command line of Pharo? I was toying with the idea of having an encrypted vault in my image (to hold multiple values for convenience) and I would then pass an unlock value on the command line - but I would need some way to ensure that value isn't persisted? Is this where a plugin might help? Something to save a value transiently only during image execution? Tim Sent from my iPhone On 31 Aug 2017, at 12:52, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> So you do not put passphrases on your ssh keys? > > Not always. > >> Because you don't give the private key away why protect it? So imagine you have development process that includes a jenkins that needs to build the source and therefor needs access to the repository. What do you do? > > I give it a password-less ssh key, encrypted in some manner. (I do not know what Jenkins offers, but both Travis and GitLab(Runner) support file/data encryption.) > Adding the build server a password on top of the key would make no difference. If you have access to one, you have the access to the other. > > Peter >

Aug. 31, 2017

Re: [Pharo-dev] Bloc: Safe to Store SSH Passphrase in Pharo?

by Peter UhnÃ¡k

> > So you do not put passphrases on your ssh keys? > Not always. > Because you don't give the private key away why protect it? So imagine you > have development process that includes a jenkins that needs to build the > source and therefor needs access to the repository. What do you do? > I give it a password-less ssh key, encrypted in some manner. (I do not know what Jenkins offers, but both Travis and GitLab(Runner) support file/data encryption.) Adding the build server a password on top of the key would make no difference. If you have access to one, you have the access to the other. Peter

Aug. 31, 2017

Re: [Pharo-dev] I disabled notifications from github

by Dimitris Chloupis

There are websites that let you automate gmail. For example you could make a small task that when you received a email for the pharo repo with the words "pull" and "request" automatically you will forward the email to the mailing list. I have used IFFT https://ifttt.com/collections/google The link I provided has the applets but it also allow you to make your own applets with a set of wizards Alternatives to IFFT https://zapier.com/ https://automate.io/ https://github.com/huginn/huginn etc On Thu, Aug 31, 2017 at 12:26 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > they were far too much. > I will comeback when I find a solution for the only two cases I would like > to inform to this list: > > 1) there is a new Pull Request (so people can go and take a look) > 2) there is a new merge into development (so people know the change has > been integrated) > > Esteban >

Aug. 31, 2017

I disabled notifications from github

by Esteban Lorenzano

they were far too much. I will comeback when I find a solution for the only two cases I would like to inform to this list: 1) there is a new Pull Request (so people can go and take a look) 2) there is a new merge into development (so people know the change has been integrated) Esteban

Aug. 31, 2017