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

Re: [Pharo-dev] Epicea applying multiple changes

by Stephane Ducasse

Hi andrei this is strange because I recovered multiple time recently due to some hidden bugs and I did not face the one you report. Stef On Tue, Jul 18, 2017 at 10:48 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > Is there some known bug in Epicea when applying multiple changes at once in > Pharo 6? > > I had a few crashes lately and each time when recovering the changes by > selecting multiple changes at once some changes are skipped. If I apply > manually each change it works. > > Cheers, > Andrei

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Esteban A. Maringolo

2017-07-18 17:33 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2017-07-18 17:26 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> imply moving to github? The Cryptography package has Squeak contributors >> too and moving to github implies a fork. > Last commit to Squeaksource repo is 4 years old. I overlooked this, last commit is recent. My bad.

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Esteban A. Maringolo

2017-07-18 17:26 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Norbert, > > On Tue, Jul 18, 2017 at 11:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Really great! I think we should move the Cryptography package from >> smalltalkhub to github, refactor it and add goodies like this. We need a >> strong crypto foundation. > > > I agree that refactoring and adding goodies is great. But why does that > imply moving to github? The Cryptography package has Squeak contributors > too and moving to github implies a fork. The fork, soft or hard, already happened since Pharo incorporated in "core" packages methods that belonged to the Cryptography package, so loading this one overrides core methods. Last commit to Squeaksource repo is 4 years old. As per my last year announcement in http://forum.world.st/Cryptography-packages-tp4915041p4915764.html "I just adapted the latest version of the Cryptography package in SqueakSource (Cryptography-rww.49) and removed everything that was already in the Pharo 5.0 image and modified what was necessary to have all the tests passing. There is still a pending organization of the Cryptography classes and packages per se, but this should be the reference implementation in Pharo. http://smalltalkhub.com/#!/~Cryptography/Cryptography/" Regards, Esteban A. Maringolo

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Eliot Miranda

Norbert, On Tue, Jul 18, 2017 at 11:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Really great! I think we should move the Cryptography package from > smalltalkhub to github, refactor it and add goodies like this. We need a > strong crypto foundation. > I agree that refactoring and adding goodies is great. But why does that imply moving to github? The Cryptography package has Squeak contributors too and moving to github implies a fork. > > Norbert > > > Am 18.07.2017 um 19:10 schrieb Esteban A. Maringolo < > emaringolo(a)gmail.com>: > > > > Great! > > > > I see you continue doing Ethereum related stuff ;-) > > > > Regards! > > Esteban A. Maringolo > > > > > > 2017-07-18 13:32 GMT-03:00 Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > >> Hi there! > >> > >> I am just releasing the first version of the Keccak-256 hashing > algorithm. > >> https://en.wikipedia.org/wiki/SHA-3 > >> > >> You can find it at: https://github.com/sbragagnolo/Keccak > >> > >> This version is based on a javascript implementation: > >> https://github.com/emn178/js-sha3 > >> > >> This implementation supports as message: bytearray and ascii and utf-8 > >> strings. > >> > >> > >> Soon i will be adding support to the rest of the Keccak family of > hashing > >> functions, since the implementations is quite configurable, is just > need to > >> add some constructors with specific configurations and tests for this > other > >> cases of usage. > >> > >> > >> Here a onliner for building an image with the version v0.1: > >> > >> wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/ > build.sh > >> | bash > >> > >> Hope you find it useful :) > >> > >> > >> Santiago > >> > >> > > -- _,,,^..^,,,_ best, Eliot

July 18, 2017

Re: [Pharo-dev] [Pharo-users] [Ann] Keccak hashing algorithm

by Santiago Bragagnolo

Hahahaha, Thanks for the feedback. Sven, I am quite new in this domain. I'll study your questions and come with solutions tomorrow :). Thanks, i really need this interaction. On Tue, 18 Jul 2017 at 20:28 Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great work. I love libraries like these. > > I am a bit confused though, in your #updateString: you seem to be > implementing UTF-8 encoding, something we already have. Normally, hashing > algorithms are defined on bytes and result in bytes (yours returns a plain > Array, which is also strange). > > It seems > > (Keccak hashMessage: 'foo bar') = (Keccak hashMessage: 'foo bar' > asByteArray). > > is true, but > > (Keccak hashMessage: 'Les Ã©lÃ¨ves FranÃ§aises') = (Keccak hashMessage: 'Les > Ã©lÃ¨ves FranÃ§aises' utf8Encoded). > > is false. How come ? > > Is this UTF-8 encoding really part of the algorithm ? > > Do your tests cover it ? > > Another question, how would you compute the invariants given here ? > > https://en.wikipedia.org/wiki/SHA-3#Examples_of_SHA-3_variants > > SHAKE128("The quick brown fox jumps over the lazy dog", 256) > > f4202e3c5852f9182a0430fd8144f0a74b95e7417ecae17db0f8cfeed0e3e66e > > SHAKE128("The quick brown fox jumps over the lazy dof", 256) > > 853f4538be0db9621a6cea659a06c1107b1f83f02b13d18297bd39d7411cf10c > > > On 18 Jul 2017, at 18:32, Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com> wrote: > > > > Hi there! > > > > I am just releasing the first version of the Keccak-256 hashing > algorithm. https://en.wikipedia.org/wiki/SHA-3 > > > > You can find it at: https://github.com/sbragagnolo/Keccak > > > > This version is based on a javascript implementation: > https://github.com/emn178/js-sha3 > > > > This implementation supports as message: bytearray and ascii and utf-8 > strings. > > > > > > Soon i will be adding support to the rest of the Keccak family of > hashing functions, since the implementations is quite configurable, is just > need to add some constructors with specific configurations and tests for > this other cases of usage. > > > > > > Here a onliner for building an image with the version v0.1: > > > > wget -O- > https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh | bash > > > > Hope you find it useful :) > > > > > > Santiago > > > > > > >

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Sven Van Caekenberghe

Great work. I love libraries like these. I am a bit confused though, in your #updateString: you seem to be implementing UTF-8 encoding, something we already have. Normally, hashing algorithms are defined on bytes and result in bytes (yours returns a plain Array, which is also strange). It seems (Keccak hashMessage: 'foo bar') = (Keccak hashMessage: 'foo bar' asByteArray). is true, but (Keccak hashMessage: 'Les Ã©lÃ¨ves FranÃ§aises') = (Keccak hashMessage: 'Les Ã©lÃ¨ves FranÃ§aises' utf8Encoded). is false. How come ? Is this UTF-8 encoding really part of the algorithm ? Do your tests cover it ? Another question, how would you compute the invariants given here ? https://en.wikipedia.org/wiki/SHA-3#Examples_of_SHA-3_variants SHAKE128("The quick brown fox jumps over the lazy dog", 256) f4202e3c5852f9182a0430fd8144f0a74b95e7417ecae17db0f8cfeed0e3e66e SHAKE128("The quick brown fox jumps over the lazy dof", 256) 853f4538be0db9621a6cea659a06c1107b1f83f02b13d18297bd39d7411cf10c > On 18 Jul 2017, at 18:32, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > Hi there! > > I am just releasing the first version of the Keccak-256 hashing algorithm. https://en.wikipedia.org/wiki/SHA-3 > > You can find it at: https://github.com/sbragagnolo/Keccak > > This version is based on a javascript implementation: https://github.com/emn178/js-sha3 > > This implementation supports as message: bytearray and ascii and utf-8 strings. > > > Soon i will be adding support to the rest of the Keccak family of hashing functions, since the implementations is quite configurable, is just need to add some constructors with specific configurations and tests for this other cases of usage. > > > Here a onliner for building an image with the version v0.1: > > wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh | bash > > Hope you find it useful :) > > > Santiago > >

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Norbert Hartl

Really great! I think we should move the Cryptography package from smalltalkhub to github, refactor it and add goodies like this. We need a strong crypto foundation. Norbert > Am 18.07.2017 um 19:10 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > > Great! > > I see you continue doing Ethereum related stuff ;-) > > Regards! > Esteban A. Maringolo > > > 2017-07-18 13:32 GMT-03:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: >> Hi there! >> >> I am just releasing the first version of the Keccak-256 hashing algorithm. >> https://en.wikipedia.org/wiki/SHA-3 >> >> You can find it at: https://github.com/sbragagnolo/Keccak >> >> This version is based on a javascript implementation: >> https://github.com/emn178/js-sha3 >> >> This implementation supports as message: bytearray and ascii and utf-8 >> strings. >> >> >> Soon i will be adding support to the rest of the Keccak family of hashing >> functions, since the implementations is quite configurable, is just need to >> add some constructors with specific configurations and tests for this other >> cases of usage. >> >> >> Here a onliner for building an image with the version v0.1: >> >> wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh >> | bash >> >> Hope you find it useful :) >> >> >> Santiago >> >>

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Esteban A. Maringolo

Great! I see you continue doing Ethereum related stuff ;-) Regards! Esteban A. Maringolo 2017-07-18 13:32 GMT-03:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > Hi there! > > I am just releasing the first version of the Keccak-256 hashing algorithm. > https://en.wikipedia.org/wiki/SHA-3 > > You can find it at: https://github.com/sbragagnolo/Keccak > > This version is based on a javascript implementation: > https://github.com/emn178/js-sha3 > > This implementation supports as message: bytearray and ascii and utf-8 > strings. > > > Soon i will be adding support to the rest of the Keccak family of hashing > functions, since the implementations is quite configurable, is just need to > add some constructors with specific configurations and tests for this other > cases of usage. > > > Here a onliner for building an image with the version v0.1: > > wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh > | bash > > Hope you find it useful :) > > > Santiago > >

July 18, 2017

[Ann] Keccak hashing algorithm

by Santiago Bragagnolo

Hi there! I am just releasing the first version of the Keccak-256 hashing algorithm. https://en.wikipedia.org/wiki/SHA-3 You can find it at: https://github.com/sbragagnolo/Keccak This version is based on a javascript implementation: https://github.com/emn178/js-sha3 This implementation supports as message: bytearray and ascii and utf-8 strings. Soon i will be adding support to the rest of the Keccak family of hashing functions, since the implementations is quite configurable, is just need to add some constructors with specific configurations and tests for this other cases of usage. Here a onliner for building an image with the version v0.1: wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh | bash Hope you find it useful :) Santiago

July 18, 2017

Re: [Pharo-dev] [Seaside] [OFFTOPIC] Update: Debris Publishing / Quuve Research & Portfolio Management Platform

by Mariano Martinez Peck

On Mon, Jul 17, 2017 at 11:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 12 Jul 2017, at 21:53, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > Hi all, > > > > A while back our team presented Quuve [1], a customizable investment > management ecosystem for professional investors. We also discussed the > technologies employed to build it [2] (it is developed on Pharo and > deployed on GemStone). We are reaching out again because we recently > revamped our website [3] and created a number of promotional videos that > demonstrate Quuve's power [4]. > > I finally watched the first video and I must say this is really > impressive. So cool to see Smalltalk code in scripting boxes ! > > Thanks Sven, Yes, the rule engine is with Smalltalk code. The user can write their own rules (for fundamentals, algorithms, quants, screening filters, etc). The code of these rules can be simple keys or Smalltalk blocks. When blocks, these are something like this: [ :aProcessorProxy | aProcessorProxy revenues / aProcessorProxy price ] and things like that. Basically, in general we pass by a "proxy" to a processor which then dynamically understands keys and ends up evaluating rules. Sure, we have problems with mathematical operators and their precedence etc. But we try to document this and provide many many examples. There is also a kind of debugger with some call stack about the called keys etc. See [1] (all violet are links that open popups to see more info) And if you liked to see Smalltalk, did you see the rules browser? hahah. See [2]. > How large is the technical team that built / is building this ? It looks > like a really deep/wide application. > The product started like a single-man project in 1996. It started with Python, then moved to Smalltalk. It has no UI back then. I joined them about 5 years ago and have been working for them since then. In these last years we started a new UI using Seaside and Bootstrap, start using Ajax everywhere, we started using GemStone for deploy, etc etc. The team was/is really small..... I cannot even believe myself how much we were able to do with the team size we had. And...I cannot stop thinking what we COULD do with a bigger team... I can give you more details privately if you wish. > > Anyway, great work. I hope you can make a living out of this. > > Thanks Sven for your nice words. [1] http://imgur.com/a/u57x7 [2] http://imgur.com/a/rkVoL -- Mariano http://marianopeck.wordpress.com

July 18, 2017