December 2020 - 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

Can anyone get recent Pharo9 builds to work on Linux?
by Martin McClure Jan. 3, 2021

Jan. 3, 2021

If anyone can get recent (within the last week or so) 64-bit Pharo9 images to work on Linux, please let me know how you did that! I've tried everything I can think of and no luck. For the purposes of this query, "working'' means that you can open a playground, type into the it, then backspace over what you've typed. If you can do that on Linux, this information would be much appreciated: * What build are you running? * What VM are you running and where did you get it? * How do you launch it? If from the command-line, what arguments? Thanks, -Martin

5 8

Problem debugging a test with #should:raise:
by Hernan Wilkinson Dec. 30, 2020

Dec. 30, 2020

Hi all, I'm sending this mail to the three lists because it is an error I found in the three Smalltalks (Squeak, Pharo and Cuis) and maybe we could share the effort to solve it and the solution. The problem can be reproduce with this test: test1 self should: [ self error: 'something' ] raise: Error withExceptionDo: [ :anError | self assert: 'something different' equals: anError messageText ] If you run that test, it will fail of course. So if you go with the debugger to the context that signals de error (self error: 'something') and press restart and then over you will find the error. In the case of Squeak and Cuis, a new debugger is opened and you can not do anything with the original one. In the case of Pharo, the debugger stops working (in another try it opened a new debugger also but I could not reproduce it). I think the problem is related to the execution simulation but it is not a simple problem... Any idea what it could be? Cheers! Hernan. -- *HernÃ¡n WilkinsonAgile Software Development, Teaching & Coaching* *Phone: +54-011*-4893-2057 *Twitter: @HernanWilkinson* *site: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 896, Floor 6, Buenos Aires, Argentina

1 0

Progress Report -> Refactoring Project - ( December 21 - 24 )
by EVELYN CUSI LOPEZ Dec. 28, 2020

Dec. 28, 2020

Hello everyone, I hope you have had a nice holiday. Last week I did these tasks: - Fix extract method and occurrences issues ( https://github.com/pharo-project/pharo/pull/8193) - Issue #8083 <https://github.com/pharo-project/pharo/issues/8083> - Issue #4429 <https://github.com/pharo-project/pharo/issues/4429> - Issue #4973 <https://github.com/pharo-project/pharo/issues/4973> - Issue #5269 <https://github.com/pharo-project/pharo/issues/5269> - Start to migrate extract method to refactoring2 and commander2 (as an experiment to review how effort we need to migrate all refactorings). - Create extract setUp and tearDown methods refactoring for TestCase classes (by the moment I have some issues in this new refactoring). Tasks for this week: - Finish to create extract setUp and tearDown methods. - Finish to migrate extract method to refactoring2 and commander2. - Fix undo refactoring issue. - Add option to limit classes where we replace senders of method to other method (https://github.com/pharo-project/pharo/issues/8087) - Fix push up issues (https://github.com/pharo-project/pharo/issues/2656 , https://github.com/pharo-project/pharo/issues/8132) Cheers, Evelyn

1 0

Browsing crashed image
by Danil Osipchuk Dec. 23, 2020

Dec. 23, 2020

Hi, Pharoes Is there a simple way to file out a package from an image which is crashing? The most close thing I found is Epicea/code changes tool - it seems that I have to apply all changes I did (and they are numerous, I didn't expect the image will die since I did nothing fancy, so was just saving the image for speed) regards, Danil

1 0

This week (52/2020) on the Issue Tracker
by Marcus Denker Dec. 23, 2020

Dec. 23, 2020

This week a bit early due to holidays. We nevertheless manged to merge around 30 Pull Requests. The next issue tracker log will be send in 2021. Debugger ======== - Debugger fuel out stack command #8141 https://github.com/pharo-project/pharo/pull/8141 - 8135-When-executing-a-doit-against-a-context-the-class-is-not-correct #8136 https://github.com/pharo-project/pharo/pull/8136 Fluid Class Definition ================= - 8143-Cleaning-Fluid-Builder #8144 https://github.com/pharo-project/pharo/pull/8144 - 8150-Trait-creation-should-use-the-traitBuilder #8151 https://github.com/pharo-project/pharo/pull/8151 Improvements/Feature ================== - Switch to pharo-icon-pack v1.0.1-idea11 #8089 https://github.com/pharo-project/pharo/pull/8089 - Add a lint rule for classes to have no "Uncategorized" classes in the package #8033 https://github.com/pharo-project/pharo/pull/8033 Refactoring =========== - [RB] - Fix issue 4902, remove duplicated method #8147 https://github.com/pharo-project/pharo/pull/8147 - Fix Abstract instance variables issue #8138 https://github.com/pharo-project/pharo/pull/8138 Bug Fixes ========= - Fix class variable entanglement issue #8045 https://github.com/pharo-project/pharo/pull/8045 - 7984 - Change Sorter broken #8154 https://github.com/pharo-project/pharo/pull/8154 - Fixes in the Parser #8148 https://github.com/pharo-project/pharo/pull/8148 - Fix Morphic Shortcut Error handling #8156 https://github.com/pharo-project/pharo/pull/8156 - Fixes #6993 against P9: Incorrect error message on failed parsing of a number with high radix #6995 https://github.com/pharo-project/pharo/pull/6995 - Do not add DoIts to the cache. fixes #7955 #7959 https://github.com/pharo-project/pharo/pull/7959 - Add `visitSelectorNode:` #8163 https://github.com/pharo-project/pharo/pull/8163 Dead Code remove =============== - 8158-ContextquickStep-is-unused-and-strange #8159 https://github.com/pharo-project/pharo/pull/8159 - DelayBasicScheduler had debug code left from review #7990 https://github.com/pharo-project/pharo/pull/7990 - remove unused ivar DelayBasicScheduler #8164 https://github.com/pharo-project/pharo/pull/8164 - [fix] remove itemFilterName for the spotter, as it seems to be unusedâ¦ #6700 https://github.com/pharo-project/pharo/pull/6700 Cleanups ======== - RBMethodNode #pragmas is the only instance variable for AST children that has an accessor checking for nil #7979 https://github.com/pharo-project/pharo/pull/7979 - Fix testCreationByUnnamed #8165 https://github.com/pharo-project/pharo/pull/8165 - Tag uncategorized classes in package Refactoring-Tests-Core #8019 https://github.com/pharo-project/pharo/pull/8019 - Move business logic from new tools to system-support #7659 https://github.com/pharo-project/pharo/pull/7659 - 8127-FFICalloutAPITestmethod2-sends-non-implemented-call #8139 https://github.com/pharo-project/pharo/pull/8139 Pharo8 backporting =============== - backportIfErrorDo #6154 https://github.com/pharo-project/pharo/pull/6154 - Fixes #6993 against P8: Incorrect error message on failed parsing of a number with high radix #6994 https://github.com/pharo-project/pharo/pull/6994

1 0

Abut writeOn: versus storeOn:
by StÃ©phane Ducasse Dec. 23, 2020

Dec. 23, 2020

Hi I saw that a couple of collections implement writeOn: in addition to storeOn: and I was wondering if someone knows the reason. My gut feeling is that this is somehow dead code. Because readOn: logic is the inverse of storeOn: and I was wondering what is the equivalent for writeOn: S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 2

[Pharo 8.0] Build #1145: backportIfErrorDo
by ci-pharo-ci-jenkins2＠inria.fr Dec. 22, 2020

Dec. 22, 2020

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

1 0

[Pharo 8.0] Build #1144: Fixes #6993 against P8: Incorrect error message on failed parsing of a number with high radix
by ci-pharo-ci-jenkins2＠inria.fr Dec. 22, 2020

Dec. 22, 2020

There is a new Pharo build available! The status of the build #1144 was: FAILURE. The Pull Request #6994 was integrated: "Fixes #6993 against P8: Incorrect error message on failed parsing of a number with high radix" Pull request url: https://github.com/pharo-project/pharo/pull/6994 Issue Url: https://github.com/pharo-project/pharo/issues/6993 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Progress Report -> Refactoring Project - ( December 14 - 18 )
by EVELYN CUSI LOPEZ Dec. 21, 2020

Dec. 21, 2020

Hi all, Last week I did these tasks: - Pair programming with Pablo, to understand how use commander2 with calypso. By the moment this only works in source code context, some similary methods can be created to use commander2 in class, variable and method context. - Fix duplicated method issue ( https://github.com/pharo-project/pharo/pull/8147 ) - Fix all abstract instance variables issue ( https://github.com/pharo-project/pharo/pull/8138) - Continue fixing Extract method and ocurrences issues, I separated middle interactions with user (in Find and replace refactoring), to remove coupling between view and logic, but now I have some errors when I want use a composite refactoring. Tasks for this week: - Finish to fix Extract method issues, only logic part (removing views) - Migrate extract method to refactoring2. - Migrate command of extract method and occurrences to commander2 - Create extract setUp and tearDown refactoring only for TestCases - Fix undo refactoring issue (I already tried to correct, however I continue having some problems - https://github.com/pharo-project/pharo/compare/Pharo9.0...Lin777:FixUndoRef… ) - Add option to limit classes where we replace senders of method to other method (https://github.com/pharo-project/pharo/issues/8087) Cheers, Evelyn

1 0