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

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

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

2017-08-31 10:24 GMT+02:00 Denis Kudriashov : > Hi. > > We now have very generic message names: > - pin > - unpin > - setPinned: > - isPinned > > Problem that they collide with possible domain related names. > For example I implemented pinning of tabs in Calypso and I found

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

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

Re: [Pharo-dev] Writeup: how to contribute to Pharo

> On 31 Aug 2017, at 00:06, Nicolai Hess wrote: > > Hi, > > I am now able to use iceberg on windows, thanks for the help. > > But I am still a bit unsure about how the review and contribution workflow > should work. > > up to pharo 6 I just load a latest image, > -

[Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi. We now have very generic message names: - pin - unpin - setPinned: - isPinned Problem that they collide with possible domain related names. For example I implemented pinning of tabs in Calypso and I found that I overrides #pin and #isPinned messages. Then I fix it with different names.

[Pharo-dev] I disabled notifications from github

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

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

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

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

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

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

> Am 31.08.2017 um 12:52 schrieb 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 >

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

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:

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

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

Re: [Pharo-dev] Can not review pull request with iceberg

Thanks Nicolai. Esteban will really look at these issues. On Thu, Aug 31, 2017 at 1:55 AM, Nicolai Hess wrote: > > > 2017-08-31 1:47 GMT+02:00 Nicolai Hess : >> >> Hi, >> >> I set up my fork and iceberg as it is described in >> >>

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Hi nicolai here is what I do. I always download the latest image via a bash script because updating can fail since loading package without a baseline may break. After I use the set up described by guille blog post and I reuse my downloaded clone (to avoid to trash my SSD). Esteban told me that

[Pharo-dev] Pharo / Iceberg BOF at ESUG

Hi I'm wondering if we should not do a BOF around Pharo iceberg at ESUG. Stef

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Hi Niolai thanks for raising this issue. The description should be migrated to Pharo github. Stef On Thu, Aug 31, 2017 at 12:42 AM, Nicolai Hess wrote: > > > 2017-08-31 0:28 GMT+02:00 Cyril Ferlicot D. : >> >> Le 31/08/2017 à 00:06, Nicolai Hess

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

> Am 31.08.2017 um 09:30 schrieb Peter Uhnák : > > > On Thu, Aug 31, 2017 at 8:45 AM, Norbert Hartl > wrote: > > > > Am 31.08.2017 um 03:32 schrieb Sean P. DeNigris >

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

On Thu, Aug 31, 2017 at 8:45 AM, Norbert Hartl wrote: > > > > Am 31.08.2017 um 03:32 schrieb Sean P. DeNigris : > > > > https://github.com/pharo-vcs/iceberg/blob/master/README.md suggests to > > configure Iceberg with the "Use Custom SSH Keys" setting,

Re: [Pharo-dev] [pharo-project/pharo] 20355-Make-SUnit-Tests-green-on-bootstrapped-image (#230)

@pavel-krivanek pushed 1 commit. 3051d7f add SUnit-Tests to the Hermes packages archive -- You are receiving this because you are subscribed to this thread. View it on GitHub:

Re: [Pharo-dev] [pharo-project/pharo] 20355-Make-SUnit-Tests-green-on-bootstrapped-image (#230)

@pavel-krivanek pushed 1 commit. c65440c add SUnit-Tests.hermes to the loading sequence -- You are receiving this because you are subscribed to this thread. View it on GitHub:

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

> Am 31.08.2017 um 03:32 schrieb Sean P. DeNigris : > > 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

Re: [Pharo-dev] Writeup: how to contribute to Pharo

On Thu, Aug 31, 2017 at 12:42 AM, Nicolai Hess wrote: > > Thank you Cyril. > > Do we have a list of links to this and other usefull articles or how did you > know about this article? > > Most of those articles comes from the same wiki that Guille gave in the first message

[Pharo-dev] [pharo-project/pharo] 20357-New-warning-text-color-is-not-readable-on-white-theme (#231)

When I added the warningTextColor I did not test it enough. Now that I try to use it with Iceberg I see that it is not good. This will make it more readable. Case 20357 : https://pharo.fogbugz.com/f/cases/20357/New-warning-text-color-is-not-readable-on-white-theme You can view, comment on, or