October 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to encrypt a password?

by mail list

Someone may have already replied as I am writing this on a plane but 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) You just compare encrypted passwords to see if they are equal. eg password:= SecureHashAlgorithm new hashMessage: aClearTextPass. then later on you check password = SecureHashAlgorithm new hashMessage: aPasswordAttempt. On Oct 24, 2011, at 11:44 PM, Mariano Martinez Peck wrote: > Hi guys. I need to be able to store a password as part of a method. Say I need to be able to do > > 'thisIsMyPassword' encrypted -> 'dasdafjewrhjk34wh5435345345345ewfsfs' > > Then I can write the method: > > MyClass >> myPassword > ^ 'dasdafjewrhjk34wh5435345345345ewfsfs' decrypted > > > It should have a kind of public key somehow so that someone cannot easily decrypt it. > > How can I do that in Pharo? I am totally newbie with all this stuff. > > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com >

Oct. 25, 2011

Re: [Pharo-project] How to encrypt a password?

by Mariano Martinez Peck

Thanks Paul. It looks interesting. On Mon, Oct 24, 2011 at 6:38 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi Mariano, > > I've made a FFI library on Squeaksource that works on Linux. > > http://www.squeaksource.com/**Cryptography/**PasswordHashingFFI-** > PaulDeBruicker.8.mcz<http://www.squeaksource.com/Cryptography/PasswordHashingFFI-PaulDeBruicker.…> > > You need to install the 32 bit versions of libcrypt and libxcrypt if you're > using a 64 bit linux os. > > Using crypt can hash passwords using MD5, DES, SHA256, SHA512. > > Using libxcrypt can hash passwords using bcrypt. > > If its for a new installation use bcrypt or SHA512 to hash the passwords. > bcrypt is better because its slower, and allegedly future proof. > > > to get a hashed password use > > BCryptLinuxFFI bcrypt:'mypassword' > > to check it against a stored hash use: > > BCryptLinuxFFI check:'mypassword' against: storedHash > > > > -- Mariano http://marianopeck.wordpress.com

Oct. 24, 2011

Re: [Pharo-project] How to encrypt a password?

by Paul DeBruicker

Hi Mariano, I've made a FFI library on Squeaksource that works on Linux. http://www.squeaksource.com/Cryptography/PasswordHashingFFI-PaulDeBruicker.… You need to install the 32 bit versions of libcrypt and libxcrypt if you're using a 64 bit linux os. Using crypt can hash passwords using MD5, DES, SHA256, SHA512. Using libxcrypt can hash passwords using bcrypt. If its for a new installation use bcrypt or SHA512 to hash the passwords. bcrypt is better because its slower, and allegedly future proof. to get a hashed password use BCryptLinuxFFI bcrypt:'mypassword' to check it against a stored hash use: BCryptLinuxFFI check:'mypassword' against: storedHash

Oct. 24, 2011

[Pharo-project] Correct usage of exception handlers with ensure and ifCurtailed

by John Toohey

Hi, I have an issue with WAListenerAdapter throwing ConnectionTimeOut and ConnectionClosed exceptions in a headless image, which causes the VM to abort. These "exceptions" are just socket timeouts, and can be ignored. The methods that I believe is the correct place to handle these is coded as follows :- waitForConnection: aSocket | socket stream | socket := aSocket waitForAcceptFor: 10. socket isNil ifTrue: [ ^ self ]. stream := SocketStream on: socket. [ [ [ self process: stream ] ensure: [ stream close ] ] ifCurtailed: [ socket destroy ] ] forkAt: Processor userBackgroundPriority I've changed the code so it looks like this :- waitForConnection: aSocket | socket stream | socket := aSocket waitForAcceptFor: 10. socket isNil ifTrue: [ ^ self ]. stream := SocketStream on: socket. [ [ [ [self process: stream ] on: NetworkError do:[:ex| ^self]] ensure: [ stream close ] ] ifCurtailed: [ socket destroy ] ] forkAt: Processor userBackgroundPriority As the errors are intermittent and only occur on my production server, I wonder is someone can look at the code, and tell me if I've added the #on:do: block correctly. Thanks. -- ~JT

Oct. 24, 2011

Re: [Pharo-project] Jenkis small delay possible?

by Camillo Bruni

Can't you make it dependent on the configuration? Like that you would only fire a build after the configuration was pushed, which, hopefully, refers to packages that actually exist :) cami On 2011-10-24, at 13:15, Igor Stasenko wrote: > On 24 October 2011 11:23, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> Marcus, the problem is that jenkis is working VERY well ;) Now, really, >> the thing is that I have a lot of packages, and when I change in several of >> them, when I commit the first package, Jenkis automatically fires up a >> build. That happens even before I can commit the rest of the packages. >> Hence...the build become unstabe, and just in the next build it becomes >> stable again... >> So...I was wondering, maybe we can put kind of delay ? so that Jenkis does >> not trigger a build immediatly, but say, after 5 minutes? (that gives me >> time to commit all packages) >> > > The solution is simple, as to me: > Do not commit the first, before you commit the rest :) > > Apparently, if jenkins watching for changes in PackageA, which depends > on PackageB, > first you should commit B, and only then A. > >> Thanks >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > > -- > Best regards, > Igor Stasenko. >

Oct. 24, 2011

[Pharo-project] How to encrypt a password?

by Mariano Martinez Peck

Hi guys. I need to be able to store a password as part of a method. Say I need to be able to do 'thisIsMyPassword' encrypted -> 'dasdafjewrhjk34wh5435345345345ewfsfs' Then I can write the method: MyClass >> myPassword ^ 'dasdafjewrhjk34wh5435345345345ewfsfs' decrypted It should have a kind of public key somehow so that someone cannot easily decrypt it. How can I do that in Pharo? I am totally newbie with all this stuff. Thanks, -- Mariano http://marianopeck.wordpress.com

Oct. 24, 2011

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #update

by Ben Coman

Thanks for your comment Bill. I need to learn more about good exception handling for my own applications. What I was surprised about was that nil appeared to receive a #do: but not raise an error, and that next step in execution was OrderedCollection>>do: . Anyway, saving the sketch, closing the image, and the next day opening the sketch has cleared the error. Ben Schwab,Wilhelm K wrote: > Ben, > > I can't comment on the workings of Dr. Geo, but since you ask about #do:, nil, least surprise etc., I can tell you that errors are your friends. Note that there is a difference between sending #do: to nil (would you really expect "nothing" to know how to iterate its contents?) and sending #do: to a collection that contains elements, some of which happen to be nil? In the latter case, would it really be non-surprising to have nil elements treated differently from their peers? Would you have them treated differently only if nil encounters a problem doing what is asked of it? In that case, #do: would have to trap and suppress errors, at least for nil entries. > > All of that sounds pretty surprising to me. Eventually, it will to you too. Happy Smalltalking! > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Ben Coman [btc(a)openInWorld.com] > Sent: Saturday, October 22, 2011 2:36 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #update > > I was using DrGeo for the first time from the bundled release 11.08 on > Windows 7. About 30 minutes in I drew three equally intersecting > circles, added a reflection line with each circle reflected. I added a > free point with a middle (I think to a circle) and was trying to add a > locus. > > When moving any of the points defining the circles I am getting a dozen > or more cascading MNUs down the screen. Moving the reflection line > still works okay. > > The error occurs in following method... > DrGeo>>updateDirtyCostumes > self presenter tool costumes do: [ :each | each update ]. > self area changed > > In the debugger inspecting "self presenter tool costumes" returns nil. > While I can't judge whether returning nil is valid here, as a Smalltalk > newbie what I am really interested in is: > > 1. The semantics of sending a "do:" message to nil. By the principle of > least surprise I would expect that it would do ...nothing, whereas here > it tries later sending the "update" method to it. > > 2. Why in lines 0027 and 0641 is the "do:" method received by > OrderedCollection and not UndefinedObject? Actually I can't see "do:" in > the hierarchy of UndefinedObject, so why does UndefinedObject not raise > a MNU for "do:" ? > > The image with the error is available at... > http://blog.openinworld.com/miscfiles/DrGeo-updateDirtyCostumes-MNU-2011-10… > > The stack trace generated by the <Mail out bug report> menu item is > below. I wasn't sure how much of it to cut or leave, so I've left it all. > ------------------8<------------------------- > 00000001 22 October 2011 10:27:03 pm > 00000002 > 00000003 VM: Win32 - IX86 - NT - Squeak3.10.2 of 11 February 2010 > [latest update: #9314] > > > > > >

Oct. 24, 2011

Re: [Pharo-project] Jenkis small delay possible?

by Igor Stasenko

On 24 October 2011 11:23, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Marcus, the problem is that jenkis is working VERY well ;)Â Â Now, really, > the thing is that I have a lot of packages, and when I change in several of > them, when I commit the first package, Jenkis automatically fires up a > build. That happens even before I can commit the rest of the packages. > Hence...the build become unstabe, and just in the next build it becomes > stable again... > So...I was wondering, maybe we can put kind of delay ? so that Jenkis does > not trigger a build immediatly, but say, after 5 minutes?Â (that gives me > time to commit all packages) > The solution is simple, as to me: Do not commit the first, before you commit the rest :) Apparently, if jenkins watching for changes in PackageA, which depends on PackageB, first you should commit B, and only then A. > Thanks > > -- > Mariano > http://marianopeck.wordpress.com > > -- Best regards, Igor Stasenko.

Oct. 24, 2011

Re: [Pharo-project] Having a shared package-cache Re: MCDirectoryRepository defaultDirectoryName ignored?

by Mariano Martinez Peck

On Sun, Oct 23, 2011 at 11:13 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > I am not sure if it is the best solution, but it works, an that's all I > need :) > What I did is to implement two extension methods: > > MCCachedRepository >> marianoDefaultWithDirectory: aDirectory > self checkCacheDirectory. > ^ default ifNil: [default := self new directory: aDirectory] > > MCCachedRepository >> marianoReset > default := nil. > > Maybe this is helpful for other guys as well? In such case, I can commit: MCCachedRepository >> changeDefaultWithDirectory: aDirectory default := nil. ^ default ifNil: [default := self new directory: aDirectory] What do you think? Cheers > And then in my build script I execute: > > MCCacheRepository marianoReset. > MCCacheRepository marianoDefaultWithDirectory: self > sharedPackageCacheDirectory. > > >> sharedPackageCacheDirectory > (FileDirectory on: self sharedPackageCacheName) > assureExistence; > yourself > > >> sharedPackageCacheName > ^ '/Users/mariano/Pharo/localRepo/' > > > Cheers > > > On Sun, Oct 23, 2011 at 10:51 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> how? >> >> Stef >> >> On Oct 21, 2011, at 11:26 PM, Mariano Martinez Peck wrote: >> >> > Thanks guys. I was able to successfully change the directory of the >> package-cache. >> > >> > On Fri, Oct 21, 2011 at 12:15 PM, Lukas Renggli <renggli(a)gmail.com> >> wrote: >> > You could add startup code that resets it to an absolute fixed location. >> > >> > I would go with the links. >> > >> > Lukas >> > >> > On 21 October 2011 11:59, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> > > >> > > On 21 Oct 2011, at 11:47, Mariano Martinez Peck wrote: >> > > >> > >> Hi guys. I would really LOVE to have a shared package-cache among >> images. I have (really) 1 gb of .mcz in different package-cache. >> > >> I am using new images all the time (hence package cache is empty). I >> would love to be able to reuse the same package-cache directory for all my >> images. >> > >> So...how can I change the place where the package-cache is created so >> that it uses another directory? >> > > >> > > Mine is 0.75 GB, but shared: I put all my images in the same >> directory. >> > > Working with links is also an option, I think that is what Lukas' >> build scripts do. >> > > >> > > Sven >> > > >> > > >> > > >> > >> > >> > >> > -- >> > Lukas Renggli >> > www.lukas-renggli.ch >> > >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

Oct. 24, 2011

Re: [Pharo-project] Jenkis small delay possible?

by Mariano Martinez Peck

Thanks Marcus!!! On Mon, Oct 24, 2011 at 11:37 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Oct 24, 2011, at 11:23 AM, Mariano Martinez Peck wrote: > > > Marcus, the problem is that jenkis is working VERY well ;) Now, really, > the thing is that I have a lot of packages, and when I change in several of > them, when I commit the first package, Jenkis automatically fires up a > build. That happens even before I can commit the rest of the packages. > Hence...the build become unstabe, and just in the next build it becomes > stable again... > > So...I was wondering, maybe we can put kind of delay ? so that Jenkis > does not trigger a build immediatly, but say, after 5 minutes? (that gives > me time to commit all packages) > > > > Ok, I changed the "quite period" to be 5 minutes (was 2) > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Mariano http://marianopeck.wordpress.com

Oct. 24, 2011