December 2018 - Pharo-users

Re: [Pharo-users] Teapot and SSL

by Sven Van Caekenberghe

> On 21 Dec 2018, at 21:42, horrido <horrido.hobbies(a)gmail.com> wrote: > > Okay, I will dispense with the self-signed certificate and purchase a > commercial one, say, from Comodo (PositiveSSL). But you cannot buy a certificate for localhost, only for a real domain name (that you host for real). > I presume once I get it, the code below will work correctly (?). If not, > I'll be back. Linux only, I would say. If you want to deploy for real, in some form of production, put nginx in front of pharo (as a proxy). That will work infinitely better and easier. > Sven Van Caekenberghe-2 wrote >>> On 20 Dec 2018, at 22:09, horrido < > >> horrido.hobbies@ > >> > wrote: >>> >>> I had this working some many months ago, but now I can't get it to work. >>> Really annoying. The entire process is so arcane... >>> >>> My HTTP server starts like this: >>> >>> Teapot stopAll. >>> Teapot on >>> Get: blah blah blah >>> >>> Then I visit http://localhost:1701/. >>> >>> I created a self-signed cert called newcert.pem. My HTTPS server starts >>> like >>> this: >>> >>> Teapot stopAll. >>> secureServer := (ZnSecureServer on: 1443) >>> certificate: '/home/richard/newcert.pem'; >>> logToTranscript; >>> start; >>> yourself. >>> teapot := Teapot configure: { #znServer -> secureServer }. >>> teapot >>> Get: blah blah blah >>> >>> When I visit https://localhost/, I get "Unable to connect". I tried >>> localhost:1701, localhost:1443, just about every damn port number I can >>> think of. No joy. >>> >>> So what the devil am I doing wrong??? >> >> First, this only works for Linux (as far as I know, have experienced, >> others have reported differently). >> >> Second, a self-signed certificate is considered insecure (more so >> nowadays), so you will have to force your browser to continue through lots >> of scary warnings. >> >> I just tried in Ubuntu 18.04.O1 LTS 64-bit, using Pharo 7 and FireFox, and >> it worked. >> >> As an aside, I would not do stuff like this, SSL is no joke, it is serious >> business: a certificate means something for real. This is not something >> you slam on for fun in a demo. In production systems, it is much better to >> put nginx or something like that in front of your app to add high quality >> ssl (with infinitely more documentation, options, users, experience, etc >> ...), but even there a quick and dirty self signed certificate won't get >> you very far. >> >> Sven > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 21, 2018

Re: [Pharo-users] Teapot and SSL

by horrido

Okay, I will dispense with the self-signed certificate and purchase a commercial one, say, from Comodo (PositiveSSL). I presume once I get it, the code below will work correctly (?). If not, I'll be back. Sven Van Caekenberghe-2 wrote >> On 20 Dec 2018, at 22:09, horrido < > horrido.hobbies@ > > wrote: >> >> I had this working some many months ago, but now I can't get it to work. >> Really annoying. The entire process is so arcane... >> >> My HTTP server starts like this: >> >> Teapot stopAll. >> Teapot on >> Get: blah blah blah >> >> Then I visit http://localhost:1701/. >> >> I created a self-signed cert called newcert.pem. My HTTPS server starts >> like >> this: >> >> Teapot stopAll. >> secureServer := (ZnSecureServer on: 1443) >> certificate: '/home/richard/newcert.pem'; >> logToTranscript; >> start; >> yourself. >> teapot := Teapot configure: { #znServer -> secureServer }. >> teapot >> Get: blah blah blah >> >> When I visit https://localhost/, I get "Unable to connect". I tried >> localhost:1701, localhost:1443, just about every damn port number I can >> think of. No joy. >> >> So what the devil am I doing wrong??? > > First, this only works for Linux (as far as I know, have experienced, > others have reported differently). > > Second, a self-signed certificate is considered insecure (more so > nowadays), so you will have to force your browser to continue through lots > of scary warnings. > > I just tried in Ubuntu 18.04.O1 LTS 64-bit, using Pharo 7 and FireFox, and > it worked. > > As an aside, I would not do stuff like this, SSL is no joke, it is serious > business: a certificate means something for real. This is not something > you slam on for fun in a demo. In production systems, it is much better to > put nginx or something like that in front of your app to add high quality > ssl (with infinitely more documentation, options, users, experience, etc > ...), but even there a quick and dirty self signed certificate won't get > you very far. > > Sven -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 21, 2018

Re: [Pharo-users] [Moose-dev] glamorous toolkit: v0.4.0

by Tudor Girba

Hi, Thanks for detailing your thoughts. Indeed, I know about your application. Whatever you can do with the current GT you will be able to do with the new one. Except that for the new one you will be able to do extra things. Here are a few: - You can build and share documents that embed those inspector views. This can be useful for reporting or sharing diagnostics with your users. - Because the underlying rendering engine is much more powerful, you can express modern and interfaces that integrate with the rest of the environment smoothly. - You likely have to deal with log files that might get large. First, the new editor allows you to smoothly work with such files. But, you can go well beyond this. Imagine that you build a tooling that produces the same editor only the text is interactive, and you might even embed visual artifacts right in the text to bridge the gap between what you would see in a typical console. For example, this tweet shows the new Transcript used to debug an animation. For every animation frame, we output the text corresponding with the frame and we insert the graphical preview corresponding to that step. You look at GT from the point of view of an end-user. You likely like the fact that you could mold the environment to your context and that you could do this incrementally. It happens that the same principles and tools can be applied to the whole programming, and once you do that, you actually can fundamentally change the act of programming. In fact, the same thing applies to the old GT: we built the new GT using that version and we believe that this allowed us to work much faster than if we would have used more traditional tools. The new GT pushes the envelope significantly further. So, that is why we are excited about that perspective, but even if you do not spend much time programming in Pharo, you can still take advantage for the user point of view as described above :). Is this answer better? Cheers, Doru > On Dec 21, 2018, at 4:59 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Thu, 20 Dec 2018 at 10:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: > The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. > [...] > Does this address the concern? > > I am not sure yet :). > > Programming is not our main use case for GT. We are using GT as an object inspector (etc) for examining diagnostic data. We have a Smalltalk application that's similar to GDB and we are using GT as the front-end. > > In our world we use the Inspector and the Spotter but all of the Smalltalk programming views are hidden. GT is "molded" to be a diagnostic tool *instead of* a programming environment. Specifically, our main use case is inspecting/debugging the operation of a JIT compiler written in C. We have Smalltalk code to load binary coredumps from the JIT, decode them using DWARF debug information, and represent the application-level compiler data structures as Smalltalk objects. This way we can use GT to browse generated code, cross-reference profiler data, examine runtime compilation errors, etc. > > The "old" GT is awesome for this. I feel like this application is also very much in the spirit of the "moldable tools" thesis. Lots of diagnostic workflows ultimately boil down to drill-down inspecting and/or searching. > > I don't know where we stand with respect to the "new" GT though. I am talking about diagnostics, you are talking about programming. I am talking about zeros and ones, you are talking about feelings. I am maintaining a stable application, you are talking about rewrites. I am having a hard time whether I should be switching to the new GT in the immediate future, or waiting another year or two for it to mature, or planning to stick with the old GT. > > Hints would be appreciated :) > > I reiterate that I think you guys are doing fantastic work - some of the most interesting work in the programming universe to my mind. I hope that this discussion is useful for at least understanding the thought process of some users / potential users. > > Cheers! > -Luke > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Being happy is a matter of choice."

Dec. 21, 2018

PetitParser release: v2.1.0

by Julien

Hello, This email to announce that a new minor release of PetitParser (1) has been published on GitHub (v2.1.0). Here is the change log: Summary ----------- - Each package has its tests separated in a separated package. - Cleaned baseline, made it more modular. - Created more groups to let people load the part of the project they want. - Some cleaning in `PetitParser` package. - Integrated PetitPreprocessor and PetitParserExtensions in the project as separated groups Changelog ----------- #31 Extract PPTextHighlighter into a separated package. #21 Add contribution guidelines #13 Update README with new groups #9 Fix CI configuration #19 A TODO comment in PPMemoizedParser>>#parseOn: might need to be fixed cleaning #11 Inconsistent method classification #15 Split tests in their own packages cleaning #22 PetitPreprocessor is missing some extensions #3 Use `>>>` notation for examples inside method #8 PPStream>>#column: has commented code that should be removed #7 PPCharSetPredicate and PPContextMemento need to be commented #1 Replace 'Oops' error message with a meaningful message #4 PPContext>>#on:stream: should be removed #2 Integrate PetitParserExtensions package from Smalltalkhub #5 Integrate PetitPreprocessor package from Smalltalkhub Thanks to Cyril Ferlicot for his help. Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

Dec. 21, 2018

Re: [Pharo-users] Teapot and SSL

by Sven Van Caekenberghe

> On 21 Dec 2018, at 12:00, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I just tried in Ubuntu 18.04.O1 LTS 64-bit, using Pharo 7 and FireFox, and it worked. BTW, I made my certificate like this (on macOS): prometheus:tmp sven$ mkdir ssl prometheus:tmp sven$ cd ssl prometheus:ssl sven$ openssl genrsa -out privkey.pem 1024 Generating RSA private key, 1024 bit long modulus ......................................++++++ ......++++++ e is 65537 (0x10001) prometheus:ssl sven$ openssl req -new -key privkey.pem -out certreq.csr You are about to be asked to enter information that will be incorporated into your certificate request. What you are about to enter is what is called a Distinguished Name or a DN. There are quite a few fields but you can leave some blank For some fields there will be a default value, If you enter '.', the field will be left blank. ----- Country Name (2 letter code) []:BE State or Province Name (full name) []: Locality Name (eg, city) []:Hasselt Organization Name (eg, company) []:Beta Nine Organizational Unit Name (eg, section) []: Common Name (eg, fully qualified host name) []:Sven Van Caekenberghe Email Address []: Please enter the following 'extra' attributes to be sent with your certificate request A challenge password []: prometheus:ssl sven$ openssl x509 -req -days 3650 -in certreq.csr -signkey privkey.pem -out newcert.pem Signature ok subject=/C=BE/L=Hasselt/O=Beta Nine/CN=Sven Van Caekenberghe Getting Private key prometheus:ssl sven$ ( openssl x509 -in newcert.pem; cat privkey.pem ) > server.pem prometheus:ssl sven$ ls certreq.csr newcert.pem privkey.pem server.pem prometheus:ssl sven$ ls -la server.pem -rw-r--r-- 1 sven staff 1681 Dec 21 11:28 server.pem prometheus:ssl sven$ pwd /Users/sven/tmp/ssl prometheus:ssl sven$ Display all 2771 possibilities? (y or n) prometheus:ssl sven$ ls certreq.csr newcert.pem privkey.pem server.pem

Dec. 21, 2018

Re: [Pharo-users] Teapot and SSL

by Sven Van Caekenberghe

> On 20 Dec 2018, at 22:09, horrido <horrido.hobbies(a)gmail.com> wrote: > > I had this working some many months ago, but now I can't get it to work. > Really annoying. The entire process is so arcane... > > My HTTP server starts like this: > > Teapot stopAll. > Teapot on > Get: blah blah blah > > Then I visit http://localhost:1701/. > > I created a self-signed cert called newcert.pem. My HTTPS server starts like > this: > > Teapot stopAll. > secureServer := (ZnSecureServer on: 1443) > certificate: '/home/richard/newcert.pem'; > logToTranscript; > start; > yourself. > teapot := Teapot configure: { #znServer -> secureServer }. > teapot > Get: blah blah blah > > When I visit https://localhost/, I get "Unable to connect". I tried > localhost:1701, localhost:1443, just about every damn port number I can > think of. No joy. > > So what the devil am I doing wrong??? First, this only works for Linux (as far as I know, have experienced, others have reported differently). Second, a self-signed certificate is considered insecure (more so nowadays), so you will have to force your browser to continue through lots of scary warnings. I just tried in Ubuntu 18.04.O1 LTS 64-bit, using Pharo 7 and FireFox, and it worked. As an aside, I would not do stuff like this, SSL is no joke, it is serious business: a certificate means something for real. This is not something you slam on for fun in a demo. In production systems, it is much better to put nginx or something like that in front of your app to add high quality ssl (with infinitely more documentation, options, users, experience, etc ...), but even there a quick and dirty self signed certificate won't get you very far. Sven

Dec. 21, 2018

Re: [Pharo-users] MongoCursor>>execute raising 'Unexpected responseTo in response'

by Holger Freyther

> On 17. Dec 2018, at 01:04, Sebastian Sastre <sebastianconcept(a)gmail.com> wrote: > > Hi All, Holger... The Mongo protocol allows multiple requests to be in transient and is using a client assigned id to indicate which request was responded to. MongoTalk is only fit to send/handle one request at a time per socket. Without more context it is difficult to say which failure mode you have but I can see these possible ones: 1.) Due to concurrency you are using the same connection but make more than one request. 2.) Our request id goes wrong (not sure how would this happen) 3.) Mongod sent a unsolicited response 4.) Many other things I can't think of right now. Is 1st) possible in your code? Do you have a packet trace to see which _responds_ you received and which request was answered? holger > Iâve seen this today: > http://forum.world.st/MongoCursor-gt-gt-execute-and-MongoTalk-changes-td488… > > > After talking with some people in the Pharo chat group at Discord about this erratic error Iâm having with MongoTalkâs MongoCursor . > > <app_image.png> > > Once it happens, the stream stays open and Mongo says isValid true but no other operations can be executed. > > Iâve loaded MongoTalk with: > > Metacello new > githubUser: 'pharo-nosql' project: 'voyage' commitish:'1.?' path: 'mc'; > baseline: 'Voyage'; > load: 'mongoâ. > > in a Pharo 6.1 image. > > Did this Unexpected responseTo happened again to you? > > nextRequestID has the code you mention in the issue: > > nextRequestID > ^requestID := requestID + 1 bitAnd: 16r3FFFFFFF > > Do you have any further hint on why the issue? Thanks! > > > Sebastian

Dec. 21, 2018

Teapot and SSL

by horrido

I had this working some many months ago, but now I can't get it to work. Really annoying. The entire process is so arcane... My HTTP server starts like this: Teapot stopAll. Teapot on Get: blah blah blah Then I visit http://localhost:1701/. I created a self-signed cert called newcert.pem. My HTTPS server starts like this: Teapot stopAll. secureServer := (ZnSecureServer on: 1443) certificate: '/home/richard/newcert.pem'; logToTranscript; start; yourself. teapot := Teapot configure: { #znServer -> secureServer }. teapot Get: blah blah blah When I visit https://localhost/, I get "Unable to connect". I tried localhost:1701, localhost:1443, just about every damn port number I can think of. No joy. So what the devil am I doing wrong??? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 20, 2018

Re: [Pharo-users] How to log Teapot activity

by Sven Van Caekenberghe

Ask a Teapot's server (which will be a Zinc HTTP Components server) to log. Teapot on server logLevel: 1; logToTranscript. Or even better, inspect the log objects emitted by Zinc HTTP Components. ZnLogEvent announcer inspect. And select the Announcements tab. > On 20 Dec 2018, at 17:02, horrido <horrido.hobbies(a)gmail.com> wrote: > > Is there a way to log server activity (to Transcript?) with Teapot? Without > ZnSecureServer. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 20, 2018

How to log Teapot activity

by horrido

Is there a way to log server activity (to Transcript?) with Teapot? Without ZnSecureServer. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 20, 2018