January 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Denis Kudriashov

2017-01-30 14:21 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > btw, what is the "m" for in PharmIDE ? First it is like farm. Seconds it is *Pha*ro *R*e*m*ote IDE

Jan. 30, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Ben Coman

But I agree with Stef. My very first impression when I read the ANN subject line was of a pharmaceutical/medical app. Maybe a slight contraction to "PharIDE", which in common usage would probably become "pharide". Only 6k googs is not too bad. btw, what is the "m" for in PharmIDE ? cheers -ben On Mon, Jan 30, 2017 at 9:15 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Like it too FWIW. > > Phil > > On Mon, Jan 30, 2017 at 12:55 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: >> >> >> 2017-01-30 12:04 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: >>> >>> Hi, >>> >>> I really enjoy how motivated people get when it is about finding a name >>> :) >>> >>> I don't agree PharmIDE is a bad name. >> >> >> I also like my original name :) > >

Jan. 30, 2017

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

by phil＠highoctane.be

How can we start PharmIDE server so that it binds to localhost only on the server? Phil On Mon, Jan 30, 2017 at 1:14 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 30.01.2017 um 11:49 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 30 Jan 2017, at 11:43, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 30.01.2017 um 11:36 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: > > Hi Sean. > > 2017-01-28 19:06 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Have you considered security at all yet? Leaving a port open which allows > arbitrary code to be executed reomotely seems very dangerous... > > Norbert already answer you. I just put little summary. > Currently there is two important issues which must be handled manually: > - security. You can manage it by VPN or SSH > - distributed garbage collection. You need perform "remotePharo > disconnect" (or "PrmRemotePharo disconnectAll") at the end of your working > session. It cleans server and client from distributed objects. > > Last issue is at high priority in my todo. When I implement it unused > distributed objects will be collected automatically like local ones. > Security option can be added too. Seamless design allows to it. Probably > It can be simple switch to SecureSocketStream instead of SocketStream. > > > My advize for security is two-fold. The first reason not to apply security > features to seamless is that it complicates the code base with a feature > that is done better elsewhere. The second reason is that one big reason why > this can be unusable is latency. A high latency makes it very hard to use > the toolkit. So removing everything adding latency should be avoided. > Security is from the image perspective one of those things. > > > Explicit/manual SSH port forwarding is easy & safe. Doing it deliberately > makes you more aware of what you are doing, which is very necessary in this > case because of the huge danger involved (giving away full image control). > But it will add its own latency (just like TLS would). > > Right. To make it a bit more concrete. If we use the example of Denis on > port 40423 then a simple > > $ ssh -L 40423:localhost:40423 pharmide-server.anydomain.com > > will open a forwarding tunnel so you can connect with the PharmIDE client > using > > PrmRemoteIDE connectTo: (TCPAddress ip: #[127 0 0 1] port: 40423) > > and you'll end up connecting to your remote image. > > Unfortunately I couldn't test it because I installed the PharmIDE on my > linux machine and it does not work. When starting the image a listening > port is opened but 5 seconds later the port closes automatically. Has > anyone tested it on a linux machine? > > Norbert > > thanks again for doing that. > > Norbert > > > Important thing here that I am really satisfied with Seamless design which > I made. It was driven by tests which means that it only addresses existing > features but allow stable evolution to new functionality. And I thing it is > most important property of any system: provide stable way how to evolve. > System can be broken and very buggy at some point but if design and tests > are stable then system will move. By stable I mean "do not require big > changes for any new bug or feature", "always iterative process". > Just want to share these thoughts with you :). > > >

Jan. 30, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by phil＠highoctane.be

Like it too FWIW. Phil On Mon, Jan 30, 2017 at 12:55 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-01-30 12:04 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > >> Hi, >> >> I really enjoy how motivated people get when it is about finding a name :) >> >> I don't agree PharmIDE is a bad name. >> > > I also like my original name :) >

Jan. 30, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Ben Coman

On Sun, Jan 29, 2017 at 10:14 PM, stepharong <stepharong(a)free.fr> wrote: > Hi guys > > Since we will push the remote tools (videos/web...) I would like to get some > ideas for a cool name. > Any ideas? > > Because Pharmide (looks like medicine or chemical product). > Since I vaguely remember some german Pharmide made me think about > Fern(sehen) but this is not a good name. * distann - derive from distantool, or distant tool. 2700 googs not too bad. * ansyble - derived from https://en.wikipedia.org/wiki/Ansible 90 googs rather than 3,130,000 googs for ansible and differentiates from competing project http://ansible.com cheers -ben

Jan. 30, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Guillermo Polito

Avatools only gives ~2k results :) On Mon, Jan 30, 2017 at 1:55 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Sun, Jan 29, 2017 at 10:14 PM, stepharong <stepharong(a)free.fr> wrote: > > > > Hi guys > > > > Since we will push the remote tools (videos/web...) I would like to get > some ideas for a cool name. > > Any ideas? > > > > Because Pharmide (looks like medicine or chemical product). > > Since I vaguely remember some german Pharmide made me think about > Fern(sehen) but this is not a good name. > > > Following a theme of "superpower remote viewing" > > * Clairvoi - derived from https://en.wikipedia.org/wiki/Clairvoyance > 915 googs is not too bad > > * Psych - https://en.wikipedia.org/wiki/Psychic projection > 43,500,000 googs, not so good > > * ESP - Extra Sensory Pharo > 265,000,000 googs, bleh! > > * sckrii - derived from https://en.wikipedia.org/wiki/Scrying > 987 googs instead of 788,000 for Scry not too bad > > * astrrall - derived from https://en.wikipedia.org/wiki/Astral_projection > 87 googs instead of 55,100,000 for astral not to bad, but perhaps > trying a bit too hard > > > And btw, at home I refer to my own personal superpowers as "telepathetic" > > cheers -ben > >

Jan. 30, 2017

Why are issue priority automatically changed from 3 to 5 ?

by Nicolai Hess

For example: 19457 <https://pharo.fogbugz.com/f/cases/19457/Scrolling-Versionner-configuration-…> Scrolling Versionner configuration list is very slow 18778 <https://pharo.fogbugz.com/f/cases/18778/FileList-View-as-does-not-work> FileList "View as" does not work 19221 <https://pharo.fogbugz.com/f/cases/19221/Rub-Find-And-Replace-can-not-search…> Rub Find And Replace can not search for "?" For me, these are issues that "must fix" and not "Fix If Time". Most issues are only fixed "if someone has the time to do it" regardless how serious they are. Fixed if time looks like , we can live without this as we did since the last release, but actually we are just used to accept some bugs and regressions because we know we are to small or to few develoeper to actually fix this issues. I don't see any value in downgrading the priority - else we could just discard any priority. nicolai

Jan. 30, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Ben Coman

On Sun, Jan 29, 2017 at 10:14 PM, stepharong <stepharong(a)free.fr> wrote: > > Hi guys > > Since we will push the remote tools (videos/web...) I would like to get some ideas for a cool name. > Any ideas? > > Because Pharmide (looks like medicine or chemical product). > Since I vaguely remember some german Pharmide made me think about Fern(sehen) but this is not a good name. Following a theme of "superpower remote viewing" * Clairvoi - derived from https://en.wikipedia.org/wiki/Clairvoyance 915 googs is not too bad * Psych - https://en.wikipedia.org/wiki/Psychic projection 43,500,000 googs, not so good * ESP - Extra Sensory Pharo 265,000,000 googs, bleh! * sckrii - derived from https://en.wikipedia.org/wiki/Scrying 987 googs instead of 788,000 for Scry not too bad * astrrall - derived from https://en.wikipedia.org/wiki/Astral_projection 87 googs instead of 55,100,000 for astral not to bad, but perhaps trying a bit too hard And btw, at home I refer to my own personal superpowers as "telepathetic" cheers -ben

Jan. 30, 2017

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

by Denis Kudriashov

2017-01-30 13:14 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > Unfortunately I couldn't test it because I installed the PharmIDE on my > linux machine and it does not work. When starting the image a listening > port is opened but 5 seconds later the port closes automatically. Has > anyone tested it on a linux machine? I am working on it. It happens when server starts from command line. Probably I do something wrong in my TCPServer implementation. Zinc server works fine. So I have example where there is no problems.

Jan. 30, 2017

Re: [Pharo-dev] [Ann] PharmIDE: Pharo remote IDE to develop farm of Pharo images remotely

by Norbert Hartl

> Am 30.01.2017 um 11:49 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> >> On 30 Jan 2017, at 11:43, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 30.01.2017 um 11:36 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: >>> >>> Hi Sean. >>> >>> 2017-01-28 19:06 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: >>> Have you considered security at all yet? Leaving a port open which allows >>> arbitrary code to be executed reomotely seems very dangerous... >>> >>> Norbert already answer you. I just put little summary. >>> Currently there is two important issues which must be handled manually: >>> - security. You can manage it by VPN or SSH >>> - distributed garbage collection. You need perform "remotePharo disconnect" (or "PrmRemotePharo disconnectAll") at the end of your working session. It cleans server and client from distributed objects. >>> >>> Last issue is at high priority in my todo. When I implement it unused distributed objects will be collected automatically like local ones. >>> Security option can be added too. Seamless design allows to it. Probably It can be simple switch to SecureSocketStream instead of SocketStream. >> >> My advize for security is two-fold. The first reason not to apply security features to seamless is that it complicates the code base with a feature that is done better elsewhere. The second reason is that one big reason why this can be unusable is latency. A high latency makes it very hard to use the toolkit. So removing everything adding latency should be avoided. Security is from the image perspective one of those things. > > Explicit/manual SSH port forwarding is easy & safe. Doing it deliberately makes you more aware of what you are doing, which is very necessary in this case because of the huge danger involved (giving away full image control). But it will add its own latency (just like TLS would). > Right. To make it a bit more concrete. If we use the example of Denis on port 40423 then a simple $ ssh -L 40423:localhost:40423 pharmide-server.anydomain.com <http://pharmide-server.anydomain.com/> will open a forwarding tunnel so you can connect with the PharmIDE client using PrmRemoteIDE connectTo: (TCPAddress ip: #[127 0 0 1] port: 40423) and you'll end up connecting to your remote image. Unfortunately I couldn't test it because I installed the PharmIDE on my linux machine and it does not work. When starting the image a listening port is opened but 5 seconds later the port closes automatically. Has anyone tested it on a linux machine? Norbert >> thanks again for doing that. >> >> Norbert >> >>> >>> Important thing here that I am really satisfied with Seamless design which I made. It was driven by tests which means that it only addresses existing features but allow stable evolution to new functionality. And I thing it is most important property of any system: provide stable way how to evolve. System can be broken and very buggy at some point but if design and tests are stable then system will move. By stable I mean "do not require big changes for any new bug or feature", "always iterative process". >>> Just want to share these thoughts with you :).

Jan. 30, 2017