- Pharo-dev - lists.pharo.org

WhatsUp from: 2013-07-15 until: 2013-07-31

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2013-07-31 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

July 15, 2013

Re: [Pharo-dev] Recommendation for password encryption?

by Paul DeBruicker

Hi Mariano, You shouldn't use it. Its broken. I didn't realize until just now. But I also haven't been using it. To encrypt the db password do enc:=Blowfish encryptString:'myDbPassword' with: 'mySecretKey' and to decrypt it later do Blowfish decryptToString: enc with: 'mySecretKey' But if you decrypt it with the key '1234' you get 'Ã«"~Ã½Ã£Ã®fword' which shows its only encrypting the first 8 bytes. And if your db password is 30 chars long like this one: '123456789012345678901234567890' then the leaked info is the last 22 numbers. The tests aren't covering this error yet. I'll mess with it sometime soon and get it sorted but for now its broken and shouldn't be used. Unless your DB password is 8 bytes or less. -- View this message in context: http://forum.world.st/Pharo-dev-Recommendation-for-password-encryption-tp46… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 15, 2013

Re: [Pharo-dev] Recommendation for password encryption?

by Paul DeBruicker

I added it here: MCHttpRepository location: 'http://smalltalkhub.com/mc/Cryptography/Blowfish/main' user: '' password: '' And added you and Mariano as contributors. StÃ©phane Ducasse wrote > Hi paul > > could you migrate the code to SmalltalkHub because this would be good to > have > a good set of packages available? > Is there tests? > Because I could port it on Pharo 2.0 and 3.0. > > > Stef > > > On Jul 13, 2013, at 4:54 PM, Paul DeBruicker < > pdebruic@ > > wrote: > >> I made a Smalltalk implementation of the Blowfish cipher >> (https://en.wikipedia.org/wiki/Blowfish_%28cipher%29) here: >> http://www.squeaksource.com/Cryptography/Blowfish-PaulDeBruicker.8.mcz >> >> >> It would benefit from being NativeBoost-ified but it works and would do >> what >> you want. >> >> >> Also I haven't tried it in Pharo 2 or 3 but it works in Squeak, Pharo >> 1.4, & >> Cuis. >> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Pharo-dev-Recommendation-for-password-encryption-tp46… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> -- View this message in context: http://forum.world.st/Pharo-dev-Recommendation-for-password-encryption-tp46… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 15, 2013

Re: [Pharo-dev] Protocol buffers - anyone working on it?

by GÃ¶ran Krampe

On 07/14/2013 07:58 PM, Sven Van Caekenberghe wrote: > > On 14 Jul 2013, at 18:49, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > >> Hey! >> >> Just wanted to check, is someone working on implementing protobufs in Pharo? >> >> regards, GÃ¶ran > > http://forum.world.st/Protocol-Buffers-anyone-td3067246.html Yeah, I know. But then I opted for the HTTP API instead. Now more time has passed so I thought I should ask, it is for a different db :) regards, GÃ¶ran

July 14, 2013

Re: [Pharo-dev] Can't open image file without write access

by Igor Stasenko

On 14 July 2013 12:55, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > if I try to launch a Pharo image and the current user only has read > access, I see a black window that never disappears. How can I launch > an image without having write access to it? This is a problem for all > pharo-based applications that companies will produce because they will > probably be placed in read-only directories such as /usr/bin or > /Applications or c:\program files > are you sure this is image file, not .changes? because i see that VM uses fopen(file, "rb") for openiing it. btw, have you tried to trace system calls while launching VM? i just tried: ls -la ~/Downloads/NativeBoost/NativeBoost.image -r--r--r--@ 1 sig staff 25081972 Jul 12 19:48 /Users/sig/Downloads/NativeBoost/NativeBoost.image opening it without problem. > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > -- Best regards, Igor Stasenko.

July 14, 2013

opal bug with the old debugger

by Andrei Vasile Chis

Hi, Executing '1 haba' in a workspace and then choosing create method from the pre debug window leads to this exception: UndefinedObject(Object)>>doesNotUnderstand: #methodOrBlockNode If instead I choose to debug, select the top context of the stack and the press the 'Creare method' button a different exception is thrown: UndefinedObject(Object)>>doesNotUnderstand: #debugHighlightRange In both cases the method is created. So known or unknown issue? Also it doesn't seem to happen with the new debugger. Not sure why :) Andrei

July 14, 2013

Re: [Pharo-dev] Protocol buffers - anyone working on it?

by Sven Van Caekenberghe

On 14 Jul 2013, at 18:49, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hey! > > Just wanted to check, is someone working on implementing protobufs in Pharo? > > regards, GÃ¶ran http://forum.world.st/Protocol-Buffers-anyone-td3067246.html ;-) Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

July 14, 2013

Protocol buffers - anyone working on it?

by GÃ¶ran Krampe

Hey! Just wanted to check, is someone working on implementing protobufs in Pharo? regards, GÃ¶ran

July 14, 2013

Re: [Pharo-dev] Recommendation for password encryption?

by Mariano Martinez Peck

Thanks Paul! THere are test and they all pass (7 tests) in Pharo 2.0! Excellent. It would be nice to have a ConfigurationOf also? I guess my use-case if the one of #testEncryptDecrypt, right? If we put it to SmalltalkHub we can also write a quick tutorial :) Btw..for my scenario I don't care at all about speed ;) On Sun, Jul 14, 2013 at 8:16 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi paul > > could you migrate the code to SmalltalkHub because this would be good to > have > a good set of packages available? > Is there tests? > Because I could port it on Pharo 2.0 and 3.0. > > > Stef > > > On Jul 13, 2013, at 4:54 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > > I made a Smalltalk implementation of the Blowfish cipher > > (https://en.wikipedia.org/wiki/Blowfish_%28cipher%29) here: > > http://www.squeaksource.com/Cryptography/Blowfish-PaulDeBruicker.8.mcz > > > > > > It would benefit from being NativeBoost-ified but it works and would do > what > > you want. > > > > > > Also I haven't tried it in Pharo 2 or 3 but it works in Squeak, Pharo > 1.4, & > > Cuis. > > > > > > > > > > > > > > > > > > -- > > View this message in context: > http://forum.world.st/Pharo-dev-Recommendation-for-password-encryption-tp46… > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > -- Mariano http://marianopeck.wordpress.com

July 14, 2013

Re: [Pharo-dev] Can't open image file without write access

by Camillo Bruni

Both startup and shutdown write to the changes file which in this case does not make sense. On 2013-07-14, at 12:55, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > if I try to launch a Pharo image and the current user only has read > access, I see a black window that never disappears. How can I launch > an image without having write access to it? This is a problem for all > pharo-based applications that companies will produce because they will > probably be placed in read-only directories such as /usr/bin or > /Applications or c:\program files > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

July 14, 2013