November 2017 - 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

Pharo 7 and Traits ?
by Sven Van Caekenberghe June 14, 2018

June 14, 2018

Hi, So what is the story with Pharo 7 and Traits ? I may be wrong, but were they not removed but flattened ? How are external libraries that want to support multiple Pharo versions supposed to cope when they need to add extension methods to (meta) class ? I have a problem with STON. Sven

2 3

Athens based game worked on windows and pharo 60 :)
by stepharong May 2, 2018

May 2, 2018

Hi esteban Today during the labs at the university, we verified with the latest VM on windows that the athens based game that the students were improving is working with Pharo 60 (while some weeks ago when they tried it did not). Stef --

3 2

AnnouncementSubscription and Ephemerons
by Torsten Bergmann April 2, 2018

April 2, 2018

Hi, by accident I stumbled upon the following code in AnnouncementSubscription: makeWeak action isBlock ifTrue: [ self error: 'Not currently available due to missing ephemerons support']. ... My understanding is that we have Ephemeron support in Pharo now working. Right? Anyone with more insights who knows how to fix/complete this? Should we at least open an issue? Thx T.

5 8

Some segfault crashes and freezes when trying to re-run saved pharo 7 images
by Thomas Dupriez March 28, 2018

March 28, 2018

Hello, I've had a few issues with Pharo 7 lately. After downloading pharo 7 images, doing some work in them and saving them, the images either instantly crashe or freeze when I try to re-run them. If that helps, I was working with and on the calypso browser. Attached are the crash dump files from some of these faulty images. vm version: 201708271955 image version: 6521 OS: Ubuntu 16.04 LTS Cheers, Thomas

6 14

new pharo cheatsheet
by stepharo March 8, 2018

March 8, 2018

new cheatsheet for Pharo syntax. Any feedback is welcome Stef

18 33

FFI Struct Argument Pass By Value Fails on Mac 64 bit
by Todd Blanchard March 6, 2018

March 6, 2018

I've been trying to track this down for a couple weeks now. I have concluded that structs passed by value to functions on the 64 bit VM are not properly populated. The struct's memory is all zero'd. I found this while trying to work with LibClang and found that functions that fetched code locations from code ranges always returned invalid zero'd locations. After spending some time with lldb I have traced the problem into the native code and found that the argument is not correct. I've carved out the wee bit of clang to reproduce this in a tiny library. The gist of it is below and the entire file is included. Basically the struct passed to the function clang_getRangeStart is zero'd memory regardless of the data I send from the image side. The build command I used on sierra is clang -shared -undefined dynamic_lookup -o microclang.dylib microclang.c I'm stuck. The FFI64 plugin is way beyond my comprehension. // microclang.c typedef struct { const void *ptr_data[2]; unsigned int_data; } CXSourceLocation; /** * \brief Identifies a half-open character range in the source code. * * Use clang_getRangeStart() and clang_getRangeEnd() to retrieve the * starting and end locations from a source range, respectively. */ typedef struct { const void *ptr_data[2]; unsigned begin_int_data; unsigned end_int_data; } CXSourceRange; const char* first = "first_pointer"; const char* second = "second_pointer"; // return a fake range with non zero data CXSourceRange clang_getArbitraryRange() { CXSourceRange range = {0}; range.ptr_data[0] = (void*)first; range.ptr_data[1] = (void*)second; range.begin_int_data = 17; range.end_int_data = 24; return range; } // Actual clang function - range is always zero'd here despite having values in the image CXSourceLocation clang_getRangeStart(CXSourceRange range) { // Special decoding for CXSourceLocations for CXLoadedDiagnostics. if ((uintptr_t)range.ptr_data[0] & 0x1) { CXSourceLocation Result = { { range.ptr_data[0], nullptr }, 0 }; return Result; } CXSourceLocation Result = { { range.ptr_data[0], range.ptr_data[1] }, range.begin_int_data }; return Result; }

4 13

Iceberg workflow
by Ben Coman March 3, 2018

March 3, 2018

I'm still struggling with Iceberg workflow for a personal repo. World menu > Iceberg Clicked <Clone Repository> Remote URL <-- git@github.com:bencoman/libclang-pharo-bindings.git Clicked <Create Repository> So now I have a new row... Name = libclang-pharo-bindings Current Branch = master Loaded version = No package loaded Status = Not loaded but nothing loaded into Image, which seems expected from Iceberg Operations Overview... * http://forum.world.st/Iceberg-operations-overview-td5036218.html (even though "Clone" is not shown there, I guess its the same as "Checkout") but I can't work out how to load it. In the filesystem I see the repo has been checked out, under... /home/ben/Pharo/images/latest-64-02/pharo-local/iceberg/bencoman/libclang-pharo-bindings Now from Iceberg Operations Overview, I guess I need to either load, merge, reload or pull. These all are apparently exposed in the UI. Right-clicking on the repo, the only one I see is "Pull incoming commits" and... Pharo quietly exits, with no debug log. Restarting to gather more info, after selecting the repo, the [Packages] tab is empty (maybe that is normal). Then I try Right-click>Refresh Repository with no effect. Right-click > Synchronize Repository takes me to three tabs with empty list views. The [Update] tab has a <Pull> button which also causes Pharo to exit. Versions... Ubuntu 16.04-64bit Pharo-7.0+alpha.build.300.sha.f81891fbde76d6a92e2827229293cb377d3b2c1c (64 Bit) Unix built on Aug 27 2017 20:00:40 Compiler: 4.6.3 VMMaker versionString VM: 201708271955 cheers -ben

6 16

OpalCompiler evaluate speed
by Nicolas Cellier Feb. 15, 2018

Feb. 15, 2018

I have an ArbitraryPrecisionFloatTests doing an exhaustive test for printing and reevaluating all positve half precision float. That's about 2^15 or approximately 32k loop which evaluate snippets like (ArbitraryPrecisionFloat readFrom: '1.123' readStream numBits: 10) The test was naively written with Compiler evaluate: and was using the legacy Compiler. If I rewrite self class compiler evaluate: the test times out. Let's see what increase is necessary: [ ArbitraryPrecisionFloatTest new testPrintAndEvaluate ] timeToRun. -> 3s with legacy Compiler -> 14s with OpalCompiler It's not unexpected that intermediate representation (IR) reification has a cost, but here the 4.5x is a bit too much... This test did account for 1/4 of total test duration already (3s out of 12s). With Opal, the total test duration doubles... (14s out of 23s) So let's analyze the hot spot with: MessageTally spyOn: [ ArbitraryPrecisionFloatTest new testPrintAndEvaluate ]. (I didn't use AndreasSystemProfiler becuase outputs seems a bit garbbled, no matter since the primitives do not account that much, a MessageTally will do the job) I first see a hot spot which does not seem that necessary: | |24.6% {3447ms} RBMethodNode(RBProgramNode)>>formattedCode >From the comments I understand that AST-based stuff requires a pattern (DoIt) and an explicit return (^), but this expensive formatting seems too much for just evaluating. i think that we should change that. Then comes: | |20.7% {2902ms} RBMethodNode>>generate: which is split in two halves, ATS->IR and IR->bytecode | | |9.3% {1299ms} RBMethodNode>>generateIR | | | |11.4% {1596ms} IRMethod>>generate: But then I see this cost a 2nd time which also leave room for progress: | |10.9% {1529ms} RBMethodNode>>generateIR | | |12.9% {1814ms} IRMethod>>generate: The first is in RBMethodNode>>generateWithSource, the second in OpalCompiler>>compile Last comes the parse time (sourceCode -> AST) | 13.2% {1858ms} OpalCompiler>>parse Along with semantic analysis | 6.0% {837ms} OpalCompiler>>doSemanticAnalysis ----------------------------------- For comparison, the legacy Compiler decomposes into: | |61.5% {2223ms} Parser>>parse:class:category:noPattern:context:notifying:ifFail: which more or less covers parse time + semantic analysis time. That means that Opal does a fair work for this stage. Then, the direct AST->byteCode phase is: | 16.9% {609ms} MethodNode>>generate IR costs almost a 5x on this phase, but we know it's the price to pay for the additional features that it potentially offers. If only we would do it once... And that's all for the legacy one... -------------------------------------- This little exercize shows that a 2x acceleration of OpalCompiler evaluate seems achievable: - simplify the uselessely expensive formatted code - generate bytecodes once, not twice Then it will be a bit more 2x slower than legacy, which is a better trade for yet to come superior features potentially brought by Opal. It would be interesting to carry same analysis on method compilation

6 12