October 2021 - 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

one year contract
by stephane ducasse Dec. 14, 2021

Dec. 14, 2021

Hello this is a one year contract with remote working possibility in Pharo of course. We will produce an english version. Please contact Nicolas Becu. Nicolas Becu <nicolas.becu(a)cnrs.fr> _____________ Nicolas Becu Chercheur CNRS Littoral Environnement et SociÃ©tÃ©s (UMR LIENSs) TÃ©l : 05 16 49 67 94 S

2 1

Hardening Zinc's Core HTTP Server
by Sven Van Caekenberghe Dec. 2, 2021

Dec. 2, 2021

Hi, Zinc HTTP Components [https://github.com/svenvc/zinc] has been a part of Pharo since version 1.3 (2011). It is an open-source framework to deal with the HTTP networking protocol, modelling all aspects involved. It also offers both client and server functionality. The reliability of the code base has improved steadily over the years, thanks to virtually all Pharo developers using it, directly or indirectly. Over the summer a number of issues that popped up after Pharo 9 was released were resolved. The robustness of the core HTTP server is one important aspect. To put this quality further to the test, I deployed two servers with the same demo Seaside application, Reddit.st, open to the internet, without any further protections. - On Amazon AWS: http://34.245.183.130:1701 - On Microsoft Azure: http://51.137.72.94:8080 The application's source code can be found at [https://github.com/svenvc/Reddit] For the technically curious there are also deploy instructions at [https://github.com/svenvc/Reddit/blob/main/DEPLOY.md] The demo app itself is described in an older article [https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740] Note that, by definition, there is no HTTPS/TLS variant. If you manage to break this server with (a) malicious request(s) in such a way that you can explain what you did for others to confirm your approach, you not only help me/us improve the code, but earn eternal fame as well ;-) Sven PS: I hope I won't regret this, I am looking for constructive criticism. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

3 8

[ANN] Fuel release 4.0.0
by Max Leske Nov. 21, 2021

Nov. 21, 2021

Hi everyone. It's been quite a while since we've done any major work on Fuel, so we are very excited to announce version 4.0.0 of Fuel today! Short-list of the most interesting things: - builder API - support for talents and anonymous classes - support for FullBlockClosure - full serialization support by default (no more need to load FuelMetalevel to serialize classes and methods) - full serialization support for Squeak The complete release notes are over on GitHub: https://theseion.github.io/Fuel/releases/4.0.0/. We hope that you'll like what we've done and we're excited to see, what kind of magic you will do with it. If you are using Fuel in a project, please let us know and we'll add it to the list of projects on GitHub (good for us and you ;)). As always, please report any issues to https://github.com/theseion/Fuel/issues and we'll try to help you out. Cheers, Max (on behalf of the Fuel team)

5 4

This week (43/2021) on the Pharo Issue Tracker
by Marcus Denker Oct. 29, 2021

Oct. 29, 2021

We merged 8 PRs and closed 9 issues. There are 11 more PRs ready, just missing a review: https://github.com/pharo-project/pharo/pulls Features ======= - [Pharo 10] Reactivating debugger opening strategies by default. #10271 https://github.com/pharo-project/pharo/pull/10271 Fixes ===== - 10204-RBMoveMethodRefactoring-incorrectly-computes-types-when-using-a-class-name-for-the-variable-to-move-into #10266 https://github.com/pharo-project/pharo/pull/10266 Speed ===== - speedup-specialSelectorIndexOrNil #10277 https://github.com/pharo-project/pharo/pull/10277 Cleanups ======== - Cleanup Beacon #10281 https://github.com/pharo-project/pharo/pull/10281 - Cleanup-Merge-FullBlockClosure1 #10272 https://github.com/pharo-project/pharo/pull/10272 - 10274-Cleanup-cleanup-IRBytecodeGeneratorv3VMHeader #10275 https://github.com/pharo-project/pharo/pull/10275 - 10231-Cleanup-check-references-to-EncoderForSistaV1 #10243 https://github.com/pharo-project/pharo/pull/10243

1 0

This week (42/2021) on the Pharo Issue Tracker
by Marcus Denker Oct. 22, 2021

Oct. 22, 2021

We merged 34 PRs and closed 35 issues. Literal Sharing =============== Since Pharo9, literals are compiled as read-only objects. This used to be a source of ugly bugs (code accidentally changing a literal, but the source not showing it). As we now can not change literals, and identity changes anyway on recompile, we are free to unify literals over the whole image. This seems to save ~2MB with the current build. We do this once as part of the build, users with large code bases can re-run it (see ImageCleaner>>#shareLiterals) and save some space. - Enable-SharedLiterals #10186 https://github.com/pharo-project/pharo/pull/10186 - 10190-Literal-Sharing-unify-nested-arrays #10195 https://github.com/pharo-project/pharo/pull/10195 Speed ===== - Use-equivalentTo-ReEquivalentSuperclassMethodsRule #10183 https://github.com/pharo-project/pharo/pull/10183 Features ======== - 10200-add-isClassSide-to-CompiledMethod #10202 https://github.com/pharo-project/pharo/pull/10202 - 4211 easy support for equality and hash with nice default behavior #4803 https://github.com/pharo-project/pharo/pull/4803 - Migrating RBInlineMethodRefactoring into Refactoring2 #10163 https://github.com/pharo-project/pharo/pull/10163 - Parameter refactoring migrations #10162 https://github.com/pharo-project/pharo/pull/10162 Class Parser ============ Work continous on the class parser / fluid class definitions - Changing uses: and trait: to use traits: in the class definition. #10199 https://github.com/pharo-project/pharo/pull/10199 - Removing #<< from SequentialCollection class #10197 https://github.com/pharo-project/pharo/pull/10197 Fixes ===== - Autofixes on class side raise DNU #10235 https://github.com/pharo-project/pharo/pull/10235 - fix: #10211 addSearch: -> addRule: adding two little tests to start #10220 https://github.com/pharo-project/pharo/pull/10220 - 9973-Different-behavior-in-Playground-for-deprecated-method-transformed-vs-nontransformed-deprecations #10222 https://github.com/pharo-project/pharo/pull/10222 - [P10] 8170-Pharo-image-freeze-on-Windows-after-some-hours-Idle-P10 #10188 https://github.com/pharo-project/pharo/pull/10188 - 10193-testNoEquivalentSuperclassMethods-failing-on-ci #10194 https://github.com/pharo-project/pharo/pull/10194 Cleanup - Old Blocks / Bytecode =============================== Cleaning the core system and compiler - 9929-Reflectivity-compiler-still-uses-pushClosureCopyCopiedValuesargsjumpTo #10177 https://github.com/pharo-project/pharo/pull/10177 - Cleanup-FullBlocks: remove dead code #10221 https://github.com/pharo-project/pharo/pull/10221 - Cleanup-optionFullBlockClosure #10229 https://github.com/pharo-project/pharo/pull/10229 - Remove-EncoderForV3PlusClosures #10181 https://github.com/pharo-project/pharo/pull/10181 - Fix 10178: Cleanup OldBlocks Compiler/Decompiler #10180 https://github.com/pharo-project/pharo/pull/10180 Cleanup ======= - Cleanup-Deprecated9-More #10236 https://github.com/pharo-project/pharo/pull/10236 - Release test to ensure we have no protocol names with leading or trailing spaces #10233 https://github.com/pharo-project/pharo/pull/10233 - Mark a few abstract refactorings #10246 https://github.com/pharo-project/pharo/pull/10246 - Mark abstract classes in Ring #10250 https://github.com/pharo-project/pharo/pull/10250 - "Tools-Test" package should be "Tools-Tests" #10244 https://github.com/pharo-project/pharo/pull/10244 - Fix lint in Array>>#copyWithDependent: #10252 https://github.com/pharo-project/pharo/pull/10252 - Cleanup: no leading or trailing space in method category name #10230 https://github.com/pharo-project/pharo/pull/10230 - 10205-LiteralVariable-classcheckValidName-has-commented-out-code #10207 https://github.com/pharo-project/pharo/pull/10207 - Remove empty protocols in ZnStaticFileServerDelegate #10224 https://github.com/pharo-project/pharo/pull/10224 - Cleanup-hasLinks #10206 https://github.com/pharo-project/pharo/pull/10206 - 10191-MCClassDefinitionring2LayoutType-misses-Double-layouts #10192 https://github.com/pharo-project/pharo/pull/10192 - Fix a few lints regarding categorization of "converting" #10175 https://github.com/pharo-project/pharo/pull/10175 - Adopte testNoUncategorizedMethods #10169 https://github.com/pharo-project/pharo/pull/10169 Pharo9 ====== [P9] 8170-Pharo-image-freeze-on-Windows-after-some-hours-Idle #10179 https://github.com/pharo-project/pharo/pull/10179

1 0

Book the dates: Pharo Days 2021: 3/4 March 2022 @ Lille
by stephane ducasse Oct. 22, 2021

Oct. 22, 2021

Dear Pharoers We are super excited to announce the dates of the next Pharo Days. Pharo Days 2021 will be held at Lille 3/4 March 2022 We will set soon a program and a website. Stay tuned. S.

1 0

This week (41/2021) on the Pharo Issue Tracker
by Marcus Denker Oct. 15, 2021

Oct. 15, 2021

We merged 25 Pull Requests and closed 13 Issue tracker entries Pharo 9 ======== - [P9] backporting-new-iceberg #10176 https://github.com/pharo-project/pharo/pull/10176 - enabling-debug-window-in-windows-P9 #10129 https://github.com/pharo-project/pharo/pull/10129 - [P9] 10085-Pharo-does-not-work-on-network-drive-on-Windows #10137 https://github.com/pharo-project/pharo/pull/10137 - P9-Backport-PR10099: Added two missing methods #tfPointerAddress #10146 https://github.com/pharo-project/pharo/pull/10146 - 10147-Fix-invalid-non-Boolean-return-when-CPU-watcher-is-enabled-For-P9--P10 #10148 https://github.com/pharo-project/pharo/pull/10148 - 10152-Backport-Pharo9-10113-speedup-isReferenced-for-ClassVariables-from-a-Pool- #10157 https://github.com/pharo-project/pharo/pull/10157 Pharo 8 ======= - Fix invalid (non-Boolean) return when CPU watcher is enabled #10134 https://github.com/pharo-project/pharo/pull/10134 Fixes ===== - 10085-Pharo-does-not-work-on-network-drive-on-Windows-P10 #10138 https://github.com/pharo-project/pharo/pull/10138 - 10144-SystemNavigationobsoleteClasses-should-use-isObsolete #10145 https://github.com/pharo-project/pharo/pull/10145 - Fix InstructionStream>>nextPc: #10044 https://github.com/pharo-project/pharo/pull/10044 - [P10] 10147-Fix-invalid-non-Boolean-return-when-CPU-watcher-is-enabled-For-P9--P10 #10149 https://github.com/pharo-project/pharo/pull/10149 Features ======= - Provide autofix rule to have no unreferenced ivars left #10126 https://github.com/pharo-project/pharo/pull/10126 - enabling-debug-window-in-windows-P10 #10130 https://github.com/pharo-project/pharo/pull/10130 - Provide Autofix for ReProperMethodProtocolNameRule #10140 https://github.com/pharo-project/pharo/pull/10140 Speed ====== - 10113-speedup-isReferenced-for-ClassVariables-from-a-Pool #10151 https://github.com/pharo-project/pharo/pull/10151 Cleanup ======= - Cleanup-theNonMetaParentName #10118 https://github.com/pharo-project/pharo/pull/10118 - Cleanup package Refactoring-Changes #10142 https://github.com/pharo-project/pharo/pull/10142 - Improve naming in ProtocolConventionTest #10132 https://github.com/pharo-project/pharo/pull/10132 - Cleanup-defaultTimeLimit #10153 https://github.com/pharo-project/pharo/pull/10153 - clean-dirty-packages-from-repo #10154 https://github.com/pharo-project/pharo/pull/10154 - Debugger infrastructure improvement and cleaning #10133 https://github.com/pharo-project/pharo/pull/10133 - Protocol for all class side methods #reset changed to initialization #9999 https://github.com/pharo-project/pharo/pull/9999 - Refactoring2-Cleanup-parentSuchAs #10158 https://github.com/pharo-project/pharo/pull/10158 - Ring-Cleanup-theNonMetaClass #10161 https://github.com/pharo-project/pharo/pull/10161 - 10065-Cleanup-ClassBuilder-remove-uses #10160 https://github.com/pharo-project/pharo/pull/10160

1 0

Something weird in VirtualMachine>>#maxExternalSemaphores:
by Sven Van Caekenberghe Oct. 13, 2021

Oct. 13, 2021

Hi, The ExternalSemaphoreTable is an important resource since it holds 3 Semaphores per Socket (network connection). The size of ExternalSemaphoreTable determines how many such resources can be used concurrently. VM parameter 49 holds this limit, it is accessed by VirtualMachine>>#maxExternalSemaphores. The default for Pharo 9 seems to be 256 currently. There is a method VirtualMachine>>#maxExternalSemaphoresSilently: that can be used to set this limit higher. This seems to work. Now, there are some limitations here: the number must be a power of 2, higher that the one set before and lower than 64K. BTW the number of file descriptors for files and sockets is also limited by the OS for its processes. Also, while growing the table, the Semaphores become unavailable to the VM for a very short period of time, so they could miss signals, leading to IO issues. For this reason, it seems that the design goal was to not allow this to grow during normal use, only during startup or upfront configuration. Now comes the weird thing: the implementation/code of VirtualMachine>>#maxExternalSemaphores: This is the method called when the current table is too small and when it wants to grow larger than the current VirtualMachine>>#maxExternalSemaphores. The implementation calls #maxExternalSemaphoresSilently: in a forked thread, after signalling a SystemNotification with a full explanation. But why should this be forked in the first place ? Then in the main thread, it signals an error ! Presumably because the design goals mentioned before. These two actions are in conflict. All this is probably the result of well meant evolution and refactoring, but it is quite confusing. My first idea would be: let the caller raise the error and don't try raising the limit, remove the current implementation and replace it by what is now #maxExternalSemaphoresSilently: What do you think ? Sven

2 5

Bloc and Spec2
by o lu Oct. 12, 2021

Oct. 12, 2021

What is the difference between Bloc and Spec2? Sent with [ProtonMail](https://protonmail.com/) Secure Email.

2 1