- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Recursively downloading Pharo packages / Building images with Nix

by Luke Gorrie

On 23 June 2017 at 18:58, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Workable? Yes. Fatal flaws? None. > There did seem to be a fatal flaw. Metacello doesn't seem to want to run without network access. Pre-populating the package cache with .mcz files doesn't seem to be sufficient. I'm sure it's possible to achieve but it was beyond my skills and patience. I have found a reasonably comfortable compromise now though. I build my image in two steps now. First a "base" image is built in the Jenkins universe using Metacello and the stable versions de jour of all the dependencies. Second the base image is imported into the Nix universe and extended using very low-brow Smalltalk scripts to force a reload of my own packages and setup the settings that I want. This seems fine. The base image can be updated by Jenkins every month or more: Just when I need to add a dependency or pull fixes to an existing one. The derived image can then be built many times per day within the same workflow as the rest of my application. Just in case anybody is curious here is the Nix code that I'm using to import the base image, add my extensions, and create a startup script that runs the image under vncserver+ratpoison for easy remote access to the GUI: https://github.com/studio/studio/blob/master/nixpkgs/studio/frontend/defaul…

July 18, 2017

Epicea applying multiple changes

by Andrei Chis

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] Automatic Refactoring Disranging Seaside Rest Methods

by Max Leske

As Gabriel notes, it looks like your missing the .sources file. I don't know what pharocloud supports, but you could try packaging your image and your .sources file into the same ZIP archive. Cheers, Max On 18 July 2017 at 02:21:54, lionelakue (lionelakue(a)gmail.com) wrote: Now I can remember reading about this somewhere(wrongly remembered it as automatic refactoring)... I have this problem when I have to copy my image to pharocloud by example. You need to zip your .image file and load it to the cloud. what I am doing now is to replace my in-uri string parameters with the excepted arg1, arg2 etc. So is this the only solution? since the behavior is not voluntary. gcotelli wrote > I saw this happening only when the image cannot find the sources file, so > it has to decompile the methods. > > On Mon, Jul 17, 2017 at 7:34 PM, lionelakue < > lionelakue@ > > wrote: > >> Hello everyone, >> >> When you copy an image or sometimes when you make a Metacello commit, >> your >> methods are automatically refactored. >> >> This uncleanse the code (replacing context meaningfull variable names >> with >> gereric identifiers) and prevents seaside request parameters . Which are >> mapped to method parameters by uri strings: >> >> ToDoHandler>>searchFor: aString >> > <get> >> > <path: '/search?query={aString}'> >> >> ^ String streamContents: [ :stream | >> ToDoList default items do: [ :each | >> (each title includesSubString: aString) >> ifTrue: [ stream nextPutAll: each title; crlf ] ] ] >> >> >> will become: >> >> >> ToDoHandler>>searchFor: arg1 >> > <get> >> > <path: '/search?query={aString}'> >> ^ String streamContents: [ :arg2| >> ToDoList default items do: [ :arg3| >> (each title includesSubString: aString) >> ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] >> >> >> So will end having a Parameter not found exception because arg1 and >> aString >> mismatche. >> >> >> Is there a way to disable automatic refactoring? >> >> Lionel >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Automatic-Refactoring- >> Disranging-Seaside-Rest-Methods-tp4955422.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/Automatic-Refactoring-Disranging-Seaside-Rest-Methods… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 18, 2017

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

by lionelakue

Now I can remember reading about this somewhere(wrongly remembered it as automatic refactoring)... I have this problem when I have to copy my image to pharocloud by example. You need to zip your .image file and load it to the cloud. what I am doing now is to replace my in-uri string parameters with the excepted arg1, arg2 etc. So is this the only solution? since the behavior is not voluntary. gcotelli wrote > I saw this happening only when the image cannot find the sources file, so > it has to decompile the methods. > > On Mon, Jul 17, 2017 at 7:34 PM, lionelakue < > lionelakue@ > > wrote: > >> Hello everyone, >> >> When you copy an image or sometimes when you make a Metacello commit, >> your >> methods are automatically refactored. >> >> This uncleanse the code (replacing context meaningfull variable names >> with >> gereric identifiers) and prevents seaside request parameters . Which are >> mapped to method parameters by uri strings: >> >> ToDoHandler>>searchFor: aString >> > <get> >> > <path: '/search?query={aString}'> >> >> ^ String streamContents: [ :stream | >> ToDoList default items do: [ :each | >> (each title includesSubString: aString) >> ifTrue: [ stream nextPutAll: each title; crlf ] ] ] >> >> >> will become: >> >> >> ToDoHandler>>searchFor: arg1 >> > <get> >> > <path: '/search?query={aString}'> >> ^ String streamContents: [ :arg2| >> ToDoList default items do: [ :arg3| >> (each title includesSubString: aString) >> ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] >> >> >> So will end having a Parameter not found exception because arg1 and >> aString >> mismatche. >> >> >> Is there a way to disable automatic refactoring? >> >> Lionel >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Automatic-Refactoring- >> Disranging-Seaside-Rest-Methods-tp4955422.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/Automatic-Refactoring-Disranging-Seaside-Rest-Methods… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 18, 2017

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

by Gabriel Cotelli

I saw this happening only when the image cannot find the sources file, so it has to decompile the methods. On Mon, Jul 17, 2017 at 7:34 PM, lionelakue <lionelakue(a)gmail.com> wrote: > Hello everyone, > > When you copy an image or sometimes when you make a Metacello commit, your > methods are automatically refactored. > > This uncleanse the code (replacing context meaningfull variable names with > gereric identifiers) and prevents seaside request parameters . Which are > mapped to method parameters by uri strings: > > ToDoHandler>>searchFor: aString > <get> > <path: '/search?query={aString}'> > > ^ String streamContents: [ :stream | > ToDoList default items do: [ :each | > (each title includesSubString: aString) > ifTrue: [ stream nextPutAll: each title; crlf ] ] ] > > > will become: > > > ToDoHandler>>searchFor: arg1 > <get> > <path: '/search?query={aString}'> > ^ String streamContents: [ :arg2| > ToDoList default items do: [ :arg3| > (each title includesSubString: aString) > ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] > > > So will end having a Parameter not found exception because arg1 and aString > mismatche. > > > Is there a way to disable automatic refactoring? > > Lionel > > > > -- > View this message in context: http://forum.world.st/Automatic-Refactoring- > Disranging-Seaside-Rest-Methods-tp4955422.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 17, 2017