- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

I wanted to share my good news, though I have not yet gotten Pharo, Squeak and Java talking. What I was able to accomplish, after finishing the port of Cryptography's ASN1Types, Module and Streams is to get Java's rendezvous and key exchange working. After I got that connecting, I looked at the ciphers, ivSequences and MAC and got that working. In Java, I am now able to encrypt and decrypt "hello world". *Celebrates* - HH > -------- Original Message -------- > Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations > Local Time: October 25, 2017 12:00 PM > UTC Time: October 25, 2017 4:00 PM > From: henry(a)callistohouse.club > To: Ben Coman <btc(a)openinworld.com>, Squeak-dev <squeak-dev(a)lists.squeakfoundation.org>, Pharo-users list <pharo-users(a)lists.pharo.org> > Pharo Development List <pharo-dev(a)lists.pharo.org> > > I disabled vatId authorization in version 3, located in SessionOperations>>processIWant | SessionOperations>>processIAm:. > > I was asked to disseminate my news to Pharo Users, hello there. I was asked to describe ParrotTalk well, provide use cases and adopters of its use. Alright, I will give an attempt. > > ParrotTalk is an encrypted connection framework. Currently allowing anonymous 2048-bit key negotiation to establish user-provided encryption cipher and user-provided encoding and decoding, both through a provided SessionAgentMap to a starting SessionAgent server. Please look in the test case ThunkHelloWorldTest for building these maps and running a connection iwth data passing after encryption is established. There is a 4-way negotiation, from ProtocolOffered/Accepted to Go/GoToo. In using RSA 2048 signature validation and DH 2048 primes to establish the key used within the selected Cipher. The Cipher and Encoder are selected by name through the negotiation protocol. Currently three Ciphers are selectable, AESede, DESede, and DES. There are two encoders tested, asn1der, and Bytes. This protocol is described here, in this document. > > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > For as to use cases, this encrypted connection has no third party, man-in-the-middle situation by not using Certificates. As such, this is a tight implementation of NSA-proof encryption without explicit authorization beyond knowledge of a host:port. The use cases involve any communication desired to be encrypted with such high encryption. The support will last my lifetime, so we have a settled solution, here in the third version, provided here. It requires version 111 of Cryptography, as a prerequisite. Both run on Squeak and Pharo. > > http://www.squeaksource.com/Cryptography/Cryptography-zzz.111.mcz > http://www.squeaksource.com/Cryptography/ParrotTalk-HenryHouse.3.mcz > > The current use is with my hubbub system, a promise-based distributed object implementation. I am working to bring ParrotTalk to Java and allow hubbub to operate interdependently between Squeak, Pharo, Java and any other languages which can support ParrotTalk and STON. My latest efforts with hubbub are to bring STON as the Layer 6 encoding. Hubbub depends on eLinda. > > http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz > http://www.squeaksource.com/Oceanside/hubbub-HenryHouse.38.mcz > > Hubbub currently fails to load correctly in Pharo. In Squeak the two ParrotRemoteTestCases: LookupTestCase and OperationalTestCase really screw everything up, do not save an image after running. I never run these tests until I get a better handle of serialization. Currently, do to a shift in progress to STON, the serialization tests fail, just the way we like it. Fix the tests then the system starts to work right. > > The shift away from vatId authorization should not adversely affect hubbub, we hope! When STON starts to work, and I think I need to turn off jsonMode, then traffic between vats can start to be analyzed and figure out how resolving is working with redirectors invoked remotely. > > - HH > >> -------- Original Message -------- >> Subject: Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations >> Local Time: October 25, 2017 12:43 AM >> UTC Time: October 25, 2017 4:43 AM >> From: btc(a)openinworld.com >> To: henry <henry(a)callistohouse.club>, Pharo Development List <pharo-dev(a)lists.pharo.org> >> Stephane Ducasse <stepharo.self(a)gmail.com> >> >> If I google... parrottalk protocol >> nothing seems related. So what is ParrotTalk? >> >> P.S... since this is not "part of" pharo, [pharo-users] would be a better place for discussion than [pharo-dev]. >> Could you re-announce there, with some description of use cases and who/where the protocol is used? >> >> cheers -ben >> >> On Wed, Oct 25, 2017 at 1:42 AM, henry <henry(a)callistohouse.club> wrote: >> >>> Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. >>> >>> - HH >>> >>> On Tue, Oct 24, 2017 at 13:40, henry <henry(a)callistohouse.club> wrote: >>> >>>> In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of >>>> >>>> - ProtocolOffered { offered, preferred } >>>> - ProtocolAccepted { accepted } >>>> - IWant|GiveInfo|ReplyInfo { vatId, domain, publicKey, cryptoProtocols, dataEncoders } >>>> - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } >>>> - Go { cryptoProtocol, dataEncoder, dhParam, signature } >>>> - GoToo { signature } >>>> >>>> Using eLinda : >>>> >>>> http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz >>>> >>>> Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. >>>> >>>> With a non-specific vatId required, anonymous connections would be supported. >>>> >>>> - HH >>>> >>>> On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> >>>>> Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH

Oct. 31, 2017

[Pharo 7.0-dev] Build #248: 20599 make kernel independent of deprecated file stream

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #248 was: SUCCESS. The Pull Request #415 was integrated: "20599 make kernel independent of deprecated file stream" Pull request url: https://github.com/pharo-project/pharo/pull/415 Issue Url: https://pharo.fogbugz.com/f/cases/20599 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

Re: [Pharo-dev] Github API on github

by Ronie Salgado

Hi, This looks interesting. Maybe I should migrate Thermite into using some of this bindings. In Thermite I am using my custom wrapper for the GitHub API, Best regards, Ronie 2017-10-30 13:50 GMT-03:00 Torsten Bergmann <astares(a)gmx.de>: > Hi Guille, > > nice. Instead of just two we can merge all three into a single solution. > As I proposed > it should be made available for instance on a general URL like: > > https://github.com/pharo-vcs/github-api > > so we could work and improve on it all together. > > Thanks > Torsten > > > Gesendet: Montag, 30. Oktober 2017 um 17:24 Uhr > Von: "Guillermo Polito" <guillermopolito(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Github API on github > > Hi all, > > So I talked with Skip (Balletie) and he's not planning on supporting the > github api he hosted because he's not doing pharo any time soon. So he has > for the moment transferred the ownership of his project to me: > > https://github.com/guillep/Github > > I'll work soon in merging both > > https://github.com/guillep/Github[https://github.com/guillep/Github] > > and > > https://github.com/guillep/github-api[https://github.com/ > guillep/github-api] > > to have a single solution. > > To answer Esteban and Norbert, I try to keep it small and modular :) But > those are really high-level goals. What do you want to "not load" or what > is bothering? > > Because I'll not cut the library so you can load services in a 'per-class' > basis. That will be impossible to maintain in the long term... We need to > find an equilibrium between modularity and reuse. Right now the github API > embedded in Iceberg is not completely reusable either. > > >

Oct. 31, 2017

[Pharo 7.0-dev] Build #247: 20609-defaultBackgroundColor-should-be-removed-from-Object

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #247 was: SUCCESS. The Pull Request #414 was integrated: "20609-defaultBackgroundColor-should-be-removed-from-Object" Pull request url: https://github.com/pharo-project/pharo/pull/414 Issue Url: https://pharo.fogbugz.com/f/cases/20609 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

[Pharo 7.0-dev] Build #246: 20155-Browse-implementers-of-in-Nautilus-doesnt-parse-source-code-properly-for-methods-in-a-block

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #246 was: FAILURE. The Pull Request #410 was integrated: "20155-Browse-implementers-of-in-Nautilus-doesnt-parse-source-code-properly-for-methods-in-a-block" Pull request url: https://github.com/pharo-project/pharo/pull/410 Issue Url: https://pharo.fogbugz.com/f/cases/20155 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

potentially useful diagrams

by Stephane Ducasse

Hi during the last sprint we were brainstorming how we can help people to understand the git hub setup. I produced these two diagrams with christophe. Are they useful for you? Stef

Oct. 31, 2017

[Pharo 7.0-dev] Build #245: 18391-Debugger must guard against actions on process termination

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #245 was: SUCCESS. The Pull Request #409 was integrated: "18391-Debugger must guard against actions on process termination" Pull request url: https://github.com/pharo-project/pharo/pull/409 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

[Iceberg] Couple of bugs/problems on Iceberg

by Mariano Martinez Peck

Hi guys, 1) I am reviewing an awesome PR from Guille and I think the labels "Left: working copy" and "Right: incoming updates" are switched. Look at the attached screenshot. In this example, the method `waitForExitWithTimeout:` is new and comes from the update (PR), its NOT not on my working copy. 2) Subtree revert not possible? Let's say I have a class with 2 methods I changed and I want to revert both. I thought that reverting the class would do the trick and revert all the inner tree. But no, I am getting a `nil dnu #inverse`. Look at the attached screenshot. I mean to revert OSUnixSubprocess (hence, both methods below). 3) The scrolling of versions in the PR review feels slow... and my project is tiny... is that using "FastTable" ? Btw...I would also love if upper and down keys could be used in that table. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

Oct. 31, 2017

[Pharo 7.0-dev] Build #244: 20581-Manually-resolved-dependencies-in-manifests-need-update

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #244 was: SUCCESS. The Pull Request #391 was integrated: "20581-Manually-resolved-dependencies-in-manifests-need-update" Pull request url: https://github.com/pharo-project/pharo/pull/391 Issue Url: https://pharo.fogbugz.com/f/cases/20581 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

Re: [Pharo-dev] [IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

by Tudor Girba

+100! Doru > On Oct 31, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Tx guys! > > > On Tue, Oct 31, 2017 at 11:09 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> Subject says pretty much all: we are going to handle the migration to Tonel >> today. >> It will be more or less like this: >> >> - we will merge all mergable pull requests. >> - we will close not-mergable ones and we will ask to re-submit with new >> format later. >> - we will do a PR with the conversion (issue is >> https://pharo.fogbugz.com/f/cases/20616) >> - we will make it work and pass tests :) >> - we will merge >> >> IMPORTANT: After conversion is done, you will need to download a new Pharo >> 7.0a. >> IMPORTANT2: We will publish a review of the contribution process soon too. >> >> Esteban > -- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Oct. 31, 2017