- Pharo-users - lists.pharo.org

Re: [Pharo-users] Validate password with PBKDF2

by Pierce Ng

On Fri, Jun 30, 2017 at 12:43:23AM -0700, Francis via Pharo-users wrote: > Saving the salt is not a big issue but I'd like something more simple. > In python I can store the salt with the password > see:https://pypi.python.org/pypi/bcrypt/3.1.0 Hi, you could try PasswordCrypt: https://github.com/PierceNg/PasswordCrypt Pierce

June 30, 2017

Re: [Pharo-users] Custom Glamour browser for Dr. Geo scripting

by Hilaire

I extended the browser definition with: browser transmit from: #scripts; from: #categories; to: #methods; when: [ :a :b | a isMeta not ]; andShow: [:a | self methodsIn: a ]. browser transmit from: #scripts; from: #categories; to: #methods; when: [ :a | a isMeta ]; andShow: [:a | self classMethodsIn: a ]. However it does not work as #when: message always receive a class, so the wrong methods a re list in the method pane. I enclosed a Fileout of the browser. It works independently of DrGeo. When one select class methods, still the instance methods are displayed in right most pane. Any tips? Thanks Hilaire Le 29/06/2017 Ã 14:59, Hilaire a Ã©crit : > but something is missing to get the listed method right depending on the > category is instance or class side. I don't how to do it. -- Dr. Geo http://drgeo.eu

June 30, 2017

Re: Validate password with PBKDF2

by Francis

Thank you Paul, Saving the salt is not a big issue but I'd like something more simple. In python I can store the salt with the password see:https://pypi.python.org/pypi/bcrypt/3.1.0 # Hash a password for the first time, with a randomly-generated salt hashed = bcrypt.hashpw(password, bcrypt.gensalt()) and retrieve it subsequently if bcrypt.checkpw(password, hashed): ... print("It Matches!") Are you (smalltalkers) aware of something similar? Thanks again Francis Paul DeBruicker wrote > Looks like you'll have to store the salt when making the original hash of > the password. > > With that you can do > > > | salt originalPassword userInputPassword originalHash newHash secretKey > | > salt:='salt'. > originalPassword:='password'. > userInputPassword:='12345678'. > originalHash:=PBKDF2 derivedKeySHA1Password: originalPassword salt: salt. > newHash:=PBKDF2 derivedKeySHA1Password: userInputPassword salt: salt. > > secretKey:= SecureRandom new nextBytes: 16. > > ((SHA256 new hmac key: secretKey) digestMessage: originalHash) = ((SHA256 > new hmac key: secretKey) digestMessage: newHash). > > > > We do the double SHA256 HMAC signing of the hashes because of > https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2011/februa… > > You can store the #secretKey and each user should get a new #salt every > time they change their password and you shouldn't reuse the salts for > other users or password. > > For PBKDF2 there is probably a max (or recommended) salt length but I > don't know it. > > I also don't know anything about the SecureRandom class but it says it on > the tin, so maybe it is. Maybe not though. I don't know how to find out. > But I don't know that it matters in this instance as its only used for the > SHA256 HMAC internally in the comparison function. > > > Hope this helps. > > > Francis wrote >> Hi folks >> >> I'm playing with the PBKDF2 package of Udo: >> http://www.smalltalkhub.com/#!/~UdoSchneider/PBKDF2 >> (thanks Udo), but I can't find how to validate a stored hash. >> Can you point me in the right direction? >> >> Thanks >> Francis -- View this message in context: http://forum.world.st/Validate-password-with-PBKDF2-tp4952973p4953004.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 30, 2017

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Tim Mackinnon

Hi Offray - I hadn't understood your project was in this area, I'll have a look. It does sound like some tweaks in playground might be useful. Like many of these things though - you have to live with them for a while to really understand. Tim Sent from my iPhone Sent from my iPhone > On 29 Jun 2017, at 23:54, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > Tim, I have made a project, called Grafoscopio, that, in its core, is > about saving playgrounds and embed them into bigger context/narratives. > You can see more details and examples here: > > [1] http://mutabit.com/grafoscopio/index.en.html > > Still needs work to do, for example improving English documentation and > discoverability, as Glenn suggested (Spanish page is better ranked in > search engines), but maybe you find it interesting for what you're > looking for. See the page at [1] and the examples, to see what is > possible at the moment. > > Cheers, > > Offray > > Ps: I share Esteban's concern on privacy and autosave feature, despite > of being useful, sometimes, for me and in the workshops. This behavior > should be disabled by default and turn on on user demand. (Maybe a tool > tip on first launch, like the one on anonymous metrics could help here > too). > >> On 29/06/17 15:55, Esteban A. Maringolo wrote: >> Please allow me a little rant here... >> >> I still find disturbing the"autosave" feature without having the >> option to explicitly save the contents in the filesystem as I did with >> Workspaces. Sometimes I don't want the contents of a file/tab updated >> by a criteria different than when to save the image, it is: my own >> when I consider appropriate. >> >> It's not I want to disable Playground by complete which I find useful >> when integrated with the inlined insector, but I want to keep the >> behavior of saving and restoring the contents under my control. >> >> Privacywise I don't like the "history" of previous contents in the >> Playground, the history it can be removed but it can't be disabled. I >> can condense the changes file, but the Playground history remains. >> >> Regards! >> >> >> Esteban A. Maringolo >> >> >> 2017-06-29 17:12 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >>> Cool - I was missing that insight. >>> >>> Tim >>> >>> Sent from my iPhone >>> >>>> On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. >>>> >>>>> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >>>>> >>>>> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >>>>> >>>>> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >>>>> >>>>> What are the semantics of page saving? >>>>> >>>>> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >>>>> >>>>> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >>>>> >>>>> Tim >>>>> >>>>> Sent from my iPhone >>>>> >>>>> >>>>> Sent from my iPhone > > >

June 30, 2017

Re: [Pharo-users] Validate password with PBKDF2

by Paul DeBruicker

Looks like you'll have to store the salt when making the original hash of the password. With that you can do | salt originalPassword userInputPassword originalHash newHash secretKey | salt:='salt'. originalPassword:='password'. userInputPassword:='12345678'. originalHash:=PBKDF2 derivedKeySHA1Password: originalPassword salt: salt. newHash:=PBKDF2 derivedKeySHA1Password: userInputPassword salt: salt. secretKey:= SecureRandom new nextBytes: 16. ((SHA256 new hmac key: secretKey) digestMessage: originalHash) = ((SHA256 new hmac key: secretKey) digestMessage: newHash). We do the double SHA256 HMAC signing of the hashes because of https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2011/februa… You can store the #secretKey and each user should get a new #salt every time they change their password and you shouldn't reuse the salts for other users or password. For PBKDF2 there is probably a max (or recommended) salt length but I don't know it. I also don't know anything about the SecureRandom class but it says it on the tin, so maybe it is. Maybe not though. I don't know how to find out. But I don't know that it matters in this instance as its only used for the SHA256 HMAC internally in the comparison function. Hope this helps. Francis wrote > Hi folks > > I'm playing with the PBKDF2 package of Udo: > http://www.smalltalkhub.com/#!/~UdoSchneider/PBKDF2 > (thanks Udo), but I can't find how to validate a stored hash. > Can you point me in the right direction? > > Thanks > Francis -- View this message in context: http://forum.world.st/Validate-password-with-PBKDF2-tp4952973p4952985.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 30, 2017

Validate password with PBKDF2

by Francis

Hi folks I'm playing with the PBKDF2 package of Udo: http://www.smalltalkhub.com/#!/~UdoSchneider/PBKDF2 (thanks Udo), but I can't find how to validate a stored hash. Can you point me in the right direction? Thanks Francis -- View this message in context: http://forum.world.st/Validate-password-with-PBKDF2-tp4952973.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 30, 2017

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Offray Vladimir Luna CÃ¡rdenas

Hi, Tim, I have made a project, called Grafoscopio, that, in its core, is about saving playgrounds and embed them into bigger context/narratives. You can see more details and examples here: [1] http://mutabit.com/grafoscopio/index.en.html Still needs work to do, for example improving English documentation and discoverability, as Glenn suggested (Spanish page is better ranked in search engines), but maybe you find it interesting for what you're looking for. See the page at [1] and the examples, to see what is possible at the moment. Cheers, Offray Ps: I share Esteban's concern on privacy and autosave feature, despite of being useful, sometimes, for me and in the workshops. This behavior should be disabled by default and turn on on user demand. (Maybe a tool tip on first launch, like the one on anonymous metrics could help here too). On 29/06/17 15:55, Esteban A. Maringolo wrote: > Please allow me a little rant here... > > I still find disturbing the"autosave" feature without having the > option to explicitly save the contents in the filesystem as I did with > Workspaces. Sometimes I don't want the contents of a file/tab updated > by a criteria different than when to save the image, it is: my own > when I consider appropriate. > > It's not I want to disable Playground by complete which I find useful > when integrated with the inlined insector, but I want to keep the > behavior of saving and restoring the contents under my control. > > Privacywise I don't like the "history" of previous contents in the > Playground, the history it can be removed but it can't be disabled. I > can condense the changes file, but the Playground history remains. > > Regards! > > > Esteban A. Maringolo > > > 2017-06-29 17:12 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >> Cool - I was missing that insight. >> >> Tim >> >> Sent from my iPhone >> >>> On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. >>> >>>> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >>>> >>>> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >>>> >>>> What are the semantics of page saving? >>>> >>>> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >>>> >>>> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >>>> >>>> Tim >>>> >>>> Sent from my iPhone >>>> >>>> >>>> Sent from my iPhone >>>> >>> >> >

June 29, 2017

Solved: ZdcPluginMissing: SSL/TLS plugin initailization failed (VM plugin missing ? OS libraries missing ?)

by Offray Vladimir Luna CÃ¡rdenas

Hi, Thanks Sven. This solves the problem. The issue was the 32 bit library. I don't know if this should be added as some kind of annotation or footnode to [1], because the chapter suposse a 32-bit Ubuntu Gnu/Linux deployment, but some of us are going to try similar stuff in similar environment, forgetting to install the 32 bits libraries. Anyway, if there is any room for this, I would be happy to make the edition with the respective pull request. [1] https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/WebA… Cheers, Offray Ps: Sorry to open a new thread. My mail was having some issues and didn't get updated threads.

June 29, 2017

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Esteban A. Maringolo

Please allow me a little rant here... I still find disturbing the"autosave" feature without having the option to explicitly save the contents in the filesystem as I did with Workspaces. Sometimes I don't want the contents of a file/tab updated by a criteria different than when to save the image, it is: my own when I consider appropriate. It's not I want to disable Playground by complete which I find useful when integrated with the inlined insector, but I want to keep the behavior of saving and restoring the contents under my control. Privacywise I don't like the "history" of previous contents in the Playground, the history it can be removed but it can't be disabled. I can condense the changes file, but the Playground history remains. Regards! Esteban A. Maringolo 2017-06-29 17:12 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > Cool - I was missing that insight. > > Tim > > Sent from my iPhone > >> On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. >> >>> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >>> >>> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >>> >>> What are the semantics of page saving? >>> >>> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >>> >>> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >>> >>> Tim >>> >>> Sent from my iPhone >>> >>> >>> Sent from my iPhone >>> >> >> > >

June 29, 2017

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Tim Mackinnon

Cool - I was missing that insight. Tim Sent from my iPhone > On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. > >> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >> >> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >> >> What are the semantics of page saving? >> >> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >> >> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >> >> Tim >> >> Sent from my iPhone >> >> >> Sent from my iPhone >> > >

June 29, 2017