April 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

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC
by Eliot Miranda June 3, 2019

June 3, 2019

Hi Damien, On Fri, Mar 23, 2018 at 12:38 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > Here are the files (image and various outputs). Running with --leakcheck > does mention a few object leaks (see output.txt); > Indeed the image is corrupt at start-up. See below. > I'm not sure where to get or how to build an assert VM. > When you build a phar. VM under build.macos64x64/pharo.cog.spur using the mvm script (mvm -A) you produce an assert VM in PharoAssert.app. > I also realized the VM I had was from this summer (the one that comes with > a 70 image with zeroconf). The output files I include were produced by the > VM at get.pharo.org/64/vmLatest70 > > https://www.dropbox.com/s/y8yqjuzd9nsvy1u/clap-broken.tar.gz?dl=0 > > On 20 March 2018 at 18:17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> >> Hi Damien, >> >> On Tue, Mar 20, 2018 at 3:12 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >>> >>> Hi, I have a Pharo image that crashes the VM on startup. The crash >>> report below seems to incriminate GC. Should I make it available somewhere >>> online? What's most convenient? >>> >> >> Don't care. Anywhere it can be downloaded from. Also, try running with >> -leakcheck 15, preferably in an assert VM and see if that gets you >> additional information. >> >> >>> >>> Process: Pharo [64892] >>> Path: /Users/USER/*/Pharo.app/Contents/MacOS/Pharo >>> Identifier: org.pharo.Pharo >>> Version: 5.0.201708271955 (5.0.201708271955) >>> >> Right. This VM is prior to the bug fixes in VMMaker.oscog-eem.2320: Spur: Fix a bad bug in SpurPlnningCompactor. unmarkObjectsFromFirstFreeObject, used when the compactor requires more than one pass due to insufficient savedFirstFieldsSpace, expects the corpse of a moved object to be unmarked, but copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. Unmarking the corpse before the copy unmarks both. This fixes a crash with ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: creates lots of files, enough to push the system into the multi-pass regime. Pharo urgently needs to upgrade the VM to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. > Code Type: X86-64 (Native) >>> Parent Process: ??? [64888] >>> Responsible: Pharo [64892] >>> User ID: 501 >>> >>> Date/Time: 2018-03-19 20:27:03.906 +0100 >>> OS Version: Mac OS X 10.13.3 (17D102) >>> Report Version: 12 >>> Anonymous UUID: 6D022236-78DD-6676-117F-EADA56D5D1BE >>> >>> Sleep/Wake UUID: AC9E4E55-3CDB-4B4F-A6B4-51ACB1177154 >>> >>> Time Awake Since Boot: 28000 seconds >>> Time Since Wake: 6500 seconds >>> >>> System Integrity Protection: enabled >>> >>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>> >>> Exception Type: EXC_BAD_ACCESS (SIGABRT) >>> Exception Codes: KERN_INVALID_ADDRESS at 0x000000012b67c0b0 >>> Exception Note: EXC_CORPSE_NOTIFY >>> >>> VM Regions Near 0x12b67c0b0: >>> VM_ALLOCATE 000000011adfc000-00000001259fc000 [172.0M] >>> rw-/rwx SM=PRV >>> --> >>> STACK GUARD 0000700005613000-0000700005614000 [ 4K] >>> ---/rwx SM=NUL stack guard for thread 1 >>> >>> Application Specific Information: >>> abort() called >>> >>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >>> 0 libsystem_kernel.dylib 0x00007fff53fbde3e __pthread_kill + 10 >>> 1 libsystem_pthread.dylib 0x00007fff540fc150 pthread_kill + 333 >>> 2 libsystem_c.dylib 0x00007fff53f1a312 abort + 127 >>> 3 org.pharo.Pharo 0x0000000104ed8997 sigsegv + 190 >>> 4 libsystem_platform.dylib 0x00007fff540eff5a _sigtramp + 26 >>> 5 ??? 000000000000000000 0 + 0 >>> 6 org.pharo.Pharo 0x0000000104e73558 markObjects + 464 >>> 7 org.pharo.Pharo 0x0000000104e72d40 fullGC + 72 >>> 8 org.pharo.Pharo 0x0000000104e92dea primitiveFullGC + >>> 45 >>> 9 org.pharo.Pharo 0x0000000104e52425 interpret + 26715 >>> 10 org.pharo.Pharo 0x0000000104e5c7f6 >>> enterSmalltalkExecutiveImplementation + 152 >>> 11 org.pharo.Pharo 0x0000000104e4be6c interpret + 674 >>> 12 org.pharo.Pharo 0x0000000104ed9cc1 >>> -[sqSqueakMainApplication runSqueak] + 394 >>> 13 com.apple.Foundation 0x00007fff2e6d696c >>> __NSFirePerformWithOrder + 360 >>> 14 com.apple.CoreFoundation 0x00007fff2c579127 >>> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 >>> 15 com.apple.CoreFoundation 0x00007fff2c57904f >>> __CFRunLoopDoObservers + 527 >>> 16 com.apple.CoreFoundation 0x00007fff2c55b6a8 __CFRunLoopRun + >>> 1240 >>> 17 com.apple.CoreFoundation 0x00007fff2c55af43 >>> CFRunLoopRunSpecific + 483 >>> 18 com.apple.HIToolbox 0x00007fff2b872e26 >>> RunCurrentEventLoopInMode + 286 >>> 19 com.apple.HIToolbox 0x00007fff2b872a9f >>> ReceiveNextEventCommon + 366 >>> 20 com.apple.HIToolbox 0x00007fff2b872914 >>> _BlockUntilNextEventMatchingListInModeWithFilter + 64 >>> 21 com.apple.AppKit 0x00007fff29b3df5f _DPSNextEvent + >>> 2085 >>> 22 com.apple.AppKit 0x00007fff2a2d3b4c >>> -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] >>> + 3044 >>> 23 com.apple.AppKit 0x00007fff29b32d6d -[NSApplication >>> run] + 764 >>> 24 com.apple.AppKit 0x00007fff29b01f1a NSApplicationMain >>> + 804 >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- _,,,^..^,,,_ best, Eliot

9 26

FloatArray
by Jimmie Houchin May 21, 2019

May 21, 2019

I just recently discovered FloatArray by accident. I was close to having to use Python/Numpy due to considerable performance differences. Performance is very important. In one of my test using a 212000 item array of floats and doing a sum on each iteration through the array Pharo was taking 17 minutes verses Python/Numpy taking 20 seconds. Using FloatArray closes the gap to 40 seconds. That is acceptable. However when looking at the FloatArray comment it says it uses 32bit floats. I need 64bit. I don't even know where to look to create 64bit FloatArrays. I am surprised that they didn't get converted when moving to 64bit Pharo. Would I need to change VM source? Compile a new VM and create image side classes? I have not messed with VM in years. I do not know where the FloatArray plugin would be. Any pointers would be a great help. If this needs to be on the vm-dev list I can move it there. Thanks. Jimmie

5 21

[Pharo 8.0] Build #248: 3272-Slot-Demo-HistorySlot
by ci-pharo-ci-jenkins2＠inria.fr April 30, 2019

April 30, 2019

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

1 0

how implement isAbstract?
by Denis Kudriashov April 30, 2019

April 30, 2019

Hello. We did recently several cleanups by marking abstract classes as abstract using #isAbstract method (https://github.com/pharo-project/pharo/pull/3087, https://github.com/pharo-ide/Calypso/pull/462) . I would like to discuss here and decide what the right way to implement this method. The logic behind is to only return true when receiver is defining class of this method. And it should be false for any subclasses (if they do not implement own #isAbstract method). There is old pattern for implementation to compare name of class: MyAbstractClass class>>isAbstract ^self name == #MyAbstractClass It is used in many places (mostly tests). And it was used in recent Pharo PR (3087). We have another pattern in other places which simply compare self with class: MyAbstractClass class>>isAbstract ^self == MyAbstractClass And in Calypso I used "more simplified" version using equality: MyAbstractClass class>>isAbstract ^self = MyAbstractClass I think we would all agree that simplest version is last one. It does not raise any question about why we compare name or why we use identity comparison. So this is my choice in this discussion. Please write arguments about your preferred implementation. And let's choose single way at the end. There is an idea to add a command into browser to make classes abstract. And this decision will be used as a template. Best regards, Denis

11 19

Re: [Pharo-dev] color protocols and marking creation methods (msg 1 of Pharo-dev Digest, Vol 72, Issue 23)
by Jim Sawyer April 29, 2019

April 29, 2019

> 1. Re: How to convey that a message create a new instance > (Esteban Maringolo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 28 Apr 2019 13:11:06 -0300 > From: Esteban Maringolo <emaringolo(a)gmail.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] How to convey that a message create a new > instance > Message-ID: > <CAJMgPCK1YB98CFn3KxhcDxLmoY7mYoXDboT5ZC2o7ZbL6pTYjA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Esteban A. Maringolo > > > On Sun, Apr 28, 2019 at 6:02 AM ducasse <stepharo(a)netcourrier.com> wrote: >>> On 28 Apr 2019, at 10:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> On 28 Apr 2019, at 01:05, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >>>> >>>> I tend to use the following idioms: >>>> - 'beSomething' idiom for cases modifying the receiver. >>>> - 'newWithSomething' or 'copyWithXx' for cases when I want to make it clear that you would get a new instance As a class, I think of Color as a factory, answering an immutable (though not literal) propertyValue. I might tell an object with a color property to change to a different propertyValue. I would expect it to do so by changing the property (replacing the current value with anotherPropertyValue), and would not expect the propertyValue itself to mutate (thus affecting all references to said value). Red cannot be darker.Â Red is Red.Â This sortOfRed can be darker than thatSortOfRed, so if you have theColorRed you can ask it for something darker, but you cannot ask it to become darker. Therefore, Color should not have any 'be' methods or 'as' methods. It might well have some fancy 'instance side' modifiers for describing a desired result, but they should always be answering an immutable instance of the class Color. self setColor: (Color red " (#FF0000) " butDarker) self color: (self color butDarker) self lightBulbColor: (Color red opacity: 0.2) As for #be vs. #as vs #newSomething, I would agree. I've beenÂ using the following conventions... Â Â Â #beX Â Â Â #beNotX (iff mode X is binary) Â Â Â #be: X Â Â Â to mean change your own state to that of mode X Â Â Â #isX Â Â Â #is: X Â Â to answer whether state is currently mode X and Â Â Â #notXÂ Â Â (iff mode X is binary) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â rather than #isNotX Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â so that the 'mode' category lists modes as Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â isX Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â isY Â Â Â Â Â Â Â Â Â Â Â Â Â Â isZ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â notX Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â notY Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â notZ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â which is easier to read when there are lots of modes. and Â Â Â #asClassX Â Â Â #as: ClassXÂ Â Â to mean answer yourself as an instance of ClassX Â Â Â #asNewClassX Â Â Â #asNew: ClassXÂ Â Â to mean answer yourself as a new instance of ClassX and Â Â Â #newSomething Â Â Â #newWith: intialValue to mean create and answer a new instance and Â Â Â #variableOrPropertyNameÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â public accessingÂ Â Â Â Â Â Â Â Â (possibly lazily initialed) Â Â Â #setVariableName: nilOrValue Â Â Â Â Â Â Â Â Â Â Â Â private mutating Â Â Â Â Â Â Â Â (can be reset to nil, but not otherwise changed) Â Â Â #releaseVariableOrPropertyNameÂ Â Â Â Â Â Â Â Â private initial/release Â Â Â (if a resource) and set to nil, answer nil. Â Â Â #resetVariableOrPropertyNameÂ Â Â Â Â Â Â Â Â Â Â Â private initial/release Â Â Â reset to nil, answer self variableOrProprtyName Â Â Â #resetVariableOrPropertyName: valueÂ Â Â private initial/releaseÂ Â Â Â release (if a resource) and set to value Â Â Â #somePropertyName: valueÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â public mutatingÂ Â Â Â Â Â Â Â Â Â Â (answer self -- private mutators answer parameter) but these are all conventions for mutable objects. -Jim Jim Sawyer: jas(a)cruzio.com === --- This email has been checked for viruses by AVG. https://www.avg.com

1 0

Rename method Refactoring leads to infinite warning in latest image.
by ducasse April 29, 2019

April 29, 2019

I could not find what was the problem. /Users/ducasse/Documents/Pharo/images/P8Evaluator/P8Evaluator.image Pharo8.0.0 Build information: Pharo-8.0.0+build.247.sha.57e3eb84cac4564882b47b87e2a977199fbe2470 (64 Bit) Unnamed May be Spec2 side effect. Good news - reproducible - can stop with cmd . https://github.com/pharo-project/pharo/issues/3275 Stef

1 0