June 2019 - Pharo-dev - lists.pharo.org

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] Contribute to pharo8.0 ?
by Ritesh Saini Feb. 24, 2020

Feb. 24, 2020

Having the same issue. Canât fix! Tried everything :( Regards, Ritesh adsense high paying keywords <https://www.digitalkube.com/highest-paying-adsense-niches/>

3 2

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by monty Sept. 10, 2019

Sept. 10, 2019

I will move it to github, if that makes things easier for everyone else. ___ montyos.wordpress.com > Sent: Wednesday, January 30, 2019 at 3:13 PM > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > > > > On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: > > > > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. > > Has there been any progress in this area ? > > It would be really great if this important project moved to GitHub. > > Sven > >

8 11

Information on Spec development
by Cyril Ferlicot Aug. 13, 2019

Aug. 13, 2019

Hello everyone! This is an important update about the development of Spec. As you might have heard, we are working on Spec to release a new version in Pharo 8. One goal is to unify all Pharo interfaces behind one GUI framework and a second goal is to allow multiple back-ends (Morphic but also GTK, Bloc, ...). To reach those goals we have been updating the current version of Spec. We see now, however, that updating Spec directly creates troubles with migration. For example, we currently have a lot of deprecation warnings in Iceberg, because we can't update it without breaking Pharo 7 compatibility. After some discussions between the engineers working on Spec, here is our plan to improve the situation: We will copy all classes of Spec and rename them with the "Sp" prefix. (We will also ensure that every class of Spec started with the same prefix for consistency). For extensions methods, we will rename them to have a version different from Spec 1 (The spec from Pharo 7). Once done we will integrate this new version in Pharo 8. From there we will wait some weeks to let users who started to use the updated Spec change their projects to use this new Spec2. Finally, we will revert all changes that happened on Spec 1 and deprecate the packages. We hope this will make things easier for everyone. Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

6 10

A small game: do one trivial improvement every day
by Marcus Denker July 9, 2019

July 9, 2019

Hi, I have started again to do one absolutely trivial improvement every week-day. The idea is that this is something that can be done in <15minutes, the right thing to do when stuck with other work or as the first or last thing of the day. I will do one per day and put another one on the issue tracker for others to do. Today: withAllSubclassesDo: and withAllSuperclasses can be implemented a little bit nicer: https://github.com/pharo-project/pharo/pull/3629 (review needed!) new issue (for someone else to submit a PR): small cleanup traits in Behaviour: isComposedBy: move to traits https://github.com/pharo-project/pharo/issues/3630 The âevery dayâ might be a bit too much, other frequencies could be âevery weekâ or âevery monthâ or âone for every releaseâ I think the âone for every releaseâ is something everyone on this list should have as a minimal goal. We have a list of simple things to do here: https://github.com/orgs/pharo-project/projects/8 Marcus

5 12

[Pharo 8.0] Build #412: Making the World to render in different backends
by ci-pharo-ci-jenkins2＠inria.fr June 30, 2019

June 30, 2019

There is a new Pharo build available! The status of the build #412 was: SUCCESS. The Pull Request #3627 was integrated: "Making the World to render in different backends" Pull request url: https://github.com/pharo-project/pharo/pull/3627 Issue Url: https://github.com/pharo-project/pharo/issues/improving Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

3 2

[Pharo 8.0] Build #414: 3706-INVALID-ISSUE
by ci-pharo-ci-jenkins2＠inria.fr June 30, 2019

June 30, 2019

There is a new Pharo build available! The status of the build #414 was: SUCCESS. The Pull Request #3707 was integrated: "3706-INVALID-ISSUE" Pull request url: https://github.com/pharo-project/pharo/pull/3707 Issue Url: https://github.com/pharo-project/pharo/issues/3706 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #413: 3630-small-cleanup-traits-in-Behaviour-isComposedBy-move-to-traits-
by ci-pharo-ci-jenkins2＠inria.fr June 30, 2019

June 30, 2019

There is a new Pharo build available! The status of the build #413 was: FAILURE. The Pull Request #3704 was integrated: "3630-small-cleanup-traits-in-Behaviour-isComposedBy-move-to-traits-" Pull request url: https://github.com/pharo-project/pharo/pull/3704 Issue Url: https://github.com/pharo-project/pharo/issues/3630 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #411: 3702-SystemDictionary-add-a-cache-for-allBehaviors
by ci-pharo-ci-jenkins2＠inria.fr June 30, 2019

June 30, 2019

There is a new Pharo build available! The status of the build #411 was: FAILURE. The Pull Request #3703 was integrated: "3702-SystemDictionary-add-a-cache-for-allBehaviors" Pull request url: https://github.com/pharo-project/pharo/pull/3703 Issue Url: https://github.com/pharo-project/pharo/issues/3702 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0