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

Re: [Pharo-dev] [squeak-dev] [Cryptography port to Pharo] RandomGenerator class>>unpredictableStringsDo:

by Ron Teitelbaum

Hi All, Unless someone filed the proper paperwork I would suggest NOT moving the cryptography code anywhere except for SqueakSource. When we started the project we spent time ensuring that we had a proper exemption from the U.S. regulations on exporting cryptographic code. If someone copied and forked the code that exemption may not still apply to that new repository. I'm not personally involved with the code on Pharo, not sure who is doing crypto there. All the best, Ron > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of > Chris Muller > Sent: Monday, October 19, 2015 2:47 PM > To: The general-purpose Squeak developers list > Cc: Pharo Development List > Subject: Re: [Pharo-dev] [squeak-dev] [Cryptography port to Pharo] > RandomGenerator class>>unpredictableStringsDo: > > Yes, if a common package for both Squeak and Pharo is possible, that'd be > great. Otherwise, the Squeak and Pharo versions should reside in separate > repositories. Squeak users are still using squeaksource.com, Pharo moved to > smalltalkhub and beyond.. > > On Mon, Oct 19, 2015 at 1:42 PM, Robert Withers > <robert.w.withers(a)gmail.com> wrote: > > hey Ron, > > > > It was actually the Pharo Cryptography team I was thinking of. Perhaps > > we can get the same package to work in both squeak and Pharo, with use > > of installable entropy sources or the like. In order to get SqueakElib > > running in Pharo I need crypto and we may as well do it right. > > > > Cheers, > > Robert > > > > > > On 10/19/2015 02:28 PM, Ron Teitelbaum wrote: > >> > >> Hi Robert, > >> > >> You are already on the Cryptograph repo on SqueakSource.com as an > admin. > >> Please feel free to reorg if you like. > >> > >> Let me know if you have trouble resurrecting your account. > >> > >> All the best, > >> > >> Ron > >> > >>> -----Original Message----- > >>> From: squeak-dev-bounces(a)lists.squeakfoundation.org > >>> [mailto:squeak-dev- bounces(a)lists.squeakfoundation.org] On Behalf Of > >>> Robert Withers > >>> Sent: Monday, October 19, 2015 1:53 PM > >>> To: squeak-dev(a)lists.squeakfoundation.org > >>> Subject: Re: [squeak-dev] [Pharo-dev] [Cryptography port to Pharo] > >>> RandomGenerator class>>unpredictableStringsDo: > >>> > >>> This is great guys. Is there a way to get this from the image? Good > >>> to get > >> > >> it > >>> > >>> with an FFI/OSProcess call or something. > >>> > >>> Thank you, > >>> Robert > >>> > >>> On 10/19/2015 08:58 AM, Louis LaBrunda wrote: > >>>> > >>>> Hi Guys, > >>>> > >>>> How about getting the CPU temperature. I think most CPUs support > >>>> "Digital Thermal Sensor" (I'm not sure about ARM). I think it is > >>>> seven bits. The real range should be less than that but it may be > >>>> enough to help add some entropy. > >>>> > >>>> Lou > >>>> > >>>> On Mon, 19 Oct 2015 07:39:19 -0400, Robert Withers > >>>> <robert.w.withers(a)gmail.com> wrote: > >>>> > >>>>> Hi Ron , nice to see you too! It has been a number of years, hasn't it? > >>>>> Crypto is timestamped back in 2010, so there is is. I hope these > >>>>> have been kind years to you, as they have for me. > >>>>> > >>>>> I love the idea of optional sources of entropy, depending on the > >>>>> deployed capabilities. So there are our mouse points and such, > >>>>> because they ought to be optional. > >>>>> > >>>>> What are some reliably present sources in the most minimal > situation? > >>>>> If we could define minimal as an image with no image level I/O > >>>>> beyond file I/O, I would think we'd have: Kernel, System, > >>>>> Collections, Compiler and FFI. Some intransitives in that scope > >>>>> for entropy would be > >>> > >>> grand. > >>>>> > >>>>> > >>>>> I was thinking to take 5 millisecondClockValues, separated by 4 > >>>>> non-secure random intervals: take the low order byte of the 4 > >>>>> intervals and reverse & concat them, as a entropic source. > >>>>> > >>>>> I can coordinate these changes. Ron, could you add me to the > >>>>> Cryptography team so I can upload the Pharo Cryptography > >>> > >>> #bleedingEdge? > >>>>> > >>>>> > >>>>> Thanks and I look forward to more, :) > >>>>> > >>>>> Robert > >>>>> > >>>>> On 10/18/2015 02:38 PM, Ron Teitelbaum wrote: > >>>>>> > >>>>>> Hi Robert, > >>>>>> > >>>>>> Nice to see you! > >>>>>> > >>>>>> Looks interesting I know that Chris did something gathering > >>>>>> sources of > >>> > >>> entropy. Seems like the more the better. Could you just make the > >>> entropy sources optional such that if they exist we use them? I > >>> would have to go back and see what Chris did but he was following > >>> suggestions from Schneider in his secureRandom. > >>>>>> > >>>>>> > >>>>>> All the best, > >>>>>> > >>>>>> Ron Teitelbaum > >>>>>> > >>>>>>> -----Original Message----- > >>>>>>> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On > >>>>>>> Behalf Of Robert Withers > >>>>>>> Sent: Sunday, October 18, 2015 5:00 AM > >>>>>>> To: The general-purpose Squeak developers list; Pharo > >>>>>>> Development List > >>>>>>> Subject: Re: [Pharo-dev] [Cryptography port to Pharo] > >>>>>>> RandomGenerator > >>>>>>> class>>unpredictableStringsDo: > >>>>>>> > >>>>>>> I'm sorry, I forgot the code. I list the existing method, > >>>>>>> followed by my modified Pharo method below. I welcome any > feedback. > >>>>>>> > >>>>>>> Regards, > >>>>>>> Robert > >>>>>>> > >>>>>>> --- > >>>>>>> Existing: > >>>>>>> unpredictableStringsDo: aBlock > >>>>>>> "Enumerate sources of information from my environment > >>>>>>> that > >>> > >>> should > >>>>>>> > >>>>>>> be generally hard to guess." > >>>>>>> | time | > >>>>>>> time := Time millisecondsToRun: > >>>>>>> [ aBlock > >>>>>>> value: World imageForm bits > >>>>>>> compressToByteArray ; > >>>>>>> value: Sensor mousePoint x asString ; > >>>>>>> value: Sensor mousePoint y asString ; > >>>>>>> value: Time millisecondClockValue > >>>>>>> asByteArray ; > >>>>>>> value: Date today asString ; > >>>>>>> value: Time now asString ; > >>>>>>> value: Display extent asString. > >>>>>>> 100 timesRepeat: [ aBlock value: UUID new ]. > >>>>>>> #(vmVersion platformName primVmPath imageName > >>> > >>> platformSubtype > >>>>>>> > >>>>>>> datedVersion lastQuitLogPosition vmStatisticsReportString > >>>>>>> imageName) > >>>>>>> collect: > >>>>>>> [ : each | > >>>>>>> aBlock value: (SmalltalkImage current > >>>>>>> perform: each) > >>> > >>> asByteArray > >>>>>>> > >>>>>>> ] ]. > >>>>>>> aBlock > >>>>>>> value: time asByteArray; > >>>>>>> "maybe the pointer has moved, hit it again." > >>>>>>> value: Sensor mousePoint asString ; > >>>>>>> value: Time millisecondClockValue asByteArray > >>>>>>> > >>>>>>> --- > >>>>>>> Pharo port: > >>>>>>> unpredictableStringsDo: aBlock > >>>>>>> "Enumerate sources of information from my environment > >>>>>>> that > >>> > >>> should > >>>>>>> > >>>>>>> be generally hard to guess." > >>>>>>> > >>>>>>> | time | > >>>>>>> time := Time millisecondsToRun: > >>>>>>> [ aBlock > >>>>>>> value: Time millisecondClockValue > >>>>>>> asByteArray ; > >>>>>>> value: Date today asString ; > >>>>>>> value: Time now asString. > >>>>>>> 100 timesRepeat: [ aBlock value: UUID new ]. > >>>>>>> #(version primImagePath imagePath datedVersion > >>>>>>> lastQuitLogPosition) > >>>>>>> collect: > >>>>>>> [ : each | > >>>>>>> aBlock value: (SmalltalkImage current > >>>>>>> perform: each) > >>> > >>> asByteArray > >>>>>>> > >>>>>>> ] ]. > >>>>>>> aBlock > >>>>>>> value: time asByteArray; > >>>>>>> value: Time millisecondClockValue asByteArray > >>>>>>> > >>>>>>> > >>>>>>> On 10/18/2015 04:23 AM, Robert Withers wrote: > >>>>>>>> > >>>>>>>> This is a message intended for anyone who was on the > >>>>>>>> Cryptography > >>> > >>> team. > >>>>>>>> > >>>>>>>> I recently ported it to Pharo and had to make changes to > >>>>>>> > >>>>>>> RandomGenerator > >>>>>>>> > >>>>>>>> class>>unpredictableStringsDo:. This certainly removed some > >>>>>>>> class>>uncertainty > >>>>>>>> from the results of this message. My question is what should I > >>>>>>>> do about that? This method seems to require non-headless, as it > >>>>>>>> is checking the mouse point and such. This being a crypto > >>>>>>>> cornerstone, what the best answer here. > >>>>>>>> > >>>>>>>> Thank you, > >>>>>>>> Robert > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> ----------------------------------------------------------- > >>>> Louis LaBrunda > >>>> Keystone Software Corp. > >>>> SkypeMe callto://PhotonDemon > >>>> mailto:Lou@Keystone-Software.com http://www.Keystone- > Software.com > >>>> > >>>> > >> > >> > >> > >

Oct. 19, 2015

Re: [Pharo-dev] [squeak-dev] [Cryptography port to Pharo] RandomGenerator class>>unpredictableStringsDo:

by Chris Muller

Yes, if a common package for both Squeak and Pharo is possible, that'd be great. Otherwise, the Squeak and Pharo versions should reside in separate repositories. Squeak users are still using squeaksource.com, Pharo moved to smalltalkhub and beyond.. On Mon, Oct 19, 2015 at 1:42 PM, Robert Withers <robert.w.withers(a)gmail.com> wrote: > hey Ron, > > It was actually the Pharo Cryptography team I was thinking of. Perhaps we > can get the same package to work in both squeak and Pharo, with use of > installable entropy sources or the like. In order to get SqueakElib running > in Pharo I need crypto and we may as well do it right. > > Cheers, > Robert > > > On 10/19/2015 02:28 PM, Ron Teitelbaum wrote: >> >> Hi Robert, >> >> You are already on the Cryptograph repo on SqueakSource.com as an admin. >> Please feel free to reorg if you like. >> >> Let me know if you have trouble resurrecting your account. >> >> All the best, >> >> Ron >> >>> -----Original Message----- >>> From: squeak-dev-bounces(a)lists.squeakfoundation.org [mailto:squeak-dev- >>> bounces(a)lists.squeakfoundation.org] On Behalf Of Robert Withers >>> Sent: Monday, October 19, 2015 1:53 PM >>> To: squeak-dev(a)lists.squeakfoundation.org >>> Subject: Re: [squeak-dev] [Pharo-dev] [Cryptography port to Pharo] >>> RandomGenerator class>>unpredictableStringsDo: >>> >>> This is great guys. Is there a way to get this from the image? Good to >>> get >> >> it >>> >>> with an FFI/OSProcess call or something. >>> >>> Thank you, >>> Robert >>> >>> On 10/19/2015 08:58 AM, Louis LaBrunda wrote: >>>> >>>> Hi Guys, >>>> >>>> How about getting the CPU temperature. I think most CPUs support >>>> "Digital Thermal Sensor" (I'm not sure about ARM). I think it is >>>> seven bits. The real range should be less than that but it may be >>>> enough to help add some entropy. >>>> >>>> Lou >>>> >>>> On Mon, 19 Oct 2015 07:39:19 -0400, Robert Withers >>>> <robert.w.withers(a)gmail.com> wrote: >>>> >>>>> Hi Ron , nice to see you too! It has been a number of years, hasn't it? >>>>> Crypto is timestamped back in 2010, so there is is. I hope these have >>>>> been kind years to you, as they have for me. >>>>> >>>>> I love the idea of optional sources of entropy, depending on the >>>>> deployed capabilities. So there are our mouse points and such, >>>>> because they ought to be optional. >>>>> >>>>> What are some reliably present sources in the most minimal situation? >>>>> If we could define minimal as an image with no image level I/O beyond >>>>> file I/O, I would think we'd have: Kernel, System, Collections, >>>>> Compiler and FFI. Some intransitives in that scope for entropy would be >>> >>> grand. >>>>> >>>>> >>>>> I was thinking to take 5 millisecondClockValues, separated by 4 >>>>> non-secure random intervals: take the low order byte of the 4 >>>>> intervals and reverse & concat them, as a entropic source. >>>>> >>>>> I can coordinate these changes. Ron, could you add me to the >>>>> Cryptography team so I can upload the Pharo Cryptography >>> >>> #bleedingEdge? >>>>> >>>>> >>>>> Thanks and I look forward to more, :) >>>>> >>>>> Robert >>>>> >>>>> On 10/18/2015 02:38 PM, Ron Teitelbaum wrote: >>>>>> >>>>>> Hi Robert, >>>>>> >>>>>> Nice to see you! >>>>>> >>>>>> Looks interesting I know that Chris did something gathering sources of >>> >>> entropy. Seems like the more the better. Could you just make the >>> entropy >>> sources optional such that if they exist we use them? I would have to go >>> back and see what Chris did but he was following suggestions from >>> Schneider in his secureRandom. >>>>>> >>>>>> >>>>>> All the best, >>>>>> >>>>>> Ron Teitelbaum >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On >>>>>>> Behalf Of Robert Withers >>>>>>> Sent: Sunday, October 18, 2015 5:00 AM >>>>>>> To: The general-purpose Squeak developers list; Pharo Development >>>>>>> List >>>>>>> Subject: Re: [Pharo-dev] [Cryptography port to Pharo] >>>>>>> RandomGenerator >>>>>>> class>>unpredictableStringsDo: >>>>>>> >>>>>>> I'm sorry, I forgot the code. I list the existing method, followed >>>>>>> by my modified Pharo method below. I welcome any feedback. >>>>>>> >>>>>>> Regards, >>>>>>> Robert >>>>>>> >>>>>>> --- >>>>>>> Existing: >>>>>>> unpredictableStringsDo: aBlock >>>>>>> "Enumerate sources of information from my environment that >>> >>> should >>>>>>> >>>>>>> be generally hard to guess." >>>>>>> | time | >>>>>>> time := Time millisecondsToRun: >>>>>>> [ aBlock >>>>>>> value: World imageForm bits >>>>>>> compressToByteArray ; >>>>>>> value: Sensor mousePoint x asString ; >>>>>>> value: Sensor mousePoint y asString ; >>>>>>> value: Time millisecondClockValue asByteArray >>>>>>> ; >>>>>>> value: Date today asString ; >>>>>>> value: Time now asString ; >>>>>>> value: Display extent asString. >>>>>>> 100 timesRepeat: [ aBlock value: UUID new ]. >>>>>>> #(vmVersion platformName primVmPath imageName >>> >>> platformSubtype >>>>>>> >>>>>>> datedVersion lastQuitLogPosition vmStatisticsReportString >>>>>>> imageName) >>>>>>> collect: >>>>>>> [ : each | >>>>>>> aBlock value: (SmalltalkImage current >>>>>>> perform: each) >>> >>> asByteArray >>>>>>> >>>>>>> ] ]. >>>>>>> aBlock >>>>>>> value: time asByteArray; >>>>>>> "maybe the pointer has moved, hit it again." >>>>>>> value: Sensor mousePoint asString ; >>>>>>> value: Time millisecondClockValue asByteArray >>>>>>> >>>>>>> --- >>>>>>> Pharo port: >>>>>>> unpredictableStringsDo: aBlock >>>>>>> "Enumerate sources of information from my environment that >>> >>> should >>>>>>> >>>>>>> be generally hard to guess." >>>>>>> >>>>>>> | time | >>>>>>> time := Time millisecondsToRun: >>>>>>> [ aBlock >>>>>>> value: Time millisecondClockValue asByteArray >>>>>>> ; >>>>>>> value: Date today asString ; >>>>>>> value: Time now asString. >>>>>>> 100 timesRepeat: [ aBlock value: UUID new ]. >>>>>>> #(version primImagePath imagePath datedVersion >>>>>>> lastQuitLogPosition) >>>>>>> collect: >>>>>>> [ : each | >>>>>>> aBlock value: (SmalltalkImage current >>>>>>> perform: each) >>> >>> asByteArray >>>>>>> >>>>>>> ] ]. >>>>>>> aBlock >>>>>>> value: time asByteArray; >>>>>>> value: Time millisecondClockValue asByteArray >>>>>>> >>>>>>> >>>>>>> On 10/18/2015 04:23 AM, Robert Withers wrote: >>>>>>>> >>>>>>>> This is a message intended for anyone who was on the Cryptography >>> >>> team. >>>>>>>> >>>>>>>> I recently ported it to Pharo and had to make changes to >>>>>>> >>>>>>> RandomGenerator >>>>>>>> >>>>>>>> class>>unpredictableStringsDo:. This certainly removed some >>>>>>>> class>>uncertainty >>>>>>>> from the results of this message. My question is what should I do >>>>>>>> about that? This method seems to require non-headless, as it is >>>>>>>> checking the mouse point and such. This being a crypto >>>>>>>> cornerstone, what the best answer here. >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Robert >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> ----------------------------------------------------------- >>>> Louis LaBrunda >>>> Keystone Software Corp. >>>> SkypeMe callto://PhotonDemon >>>> mailto:Lou@Keystone-Software.com http://www.Keystone-Software.com >>>> >>>> >> >> >> >

Oct. 19, 2015

Re: [Pharo-dev] [squeak-dev] [Cryptography port to Pharo] RandomGenerator class>>unpredictableStringsDo:

by Robert Withers

hey Ron, It was actually the Pharo Cryptography team I was thinking of. Perhaps we can get the same package to work in both squeak and Pharo, with use of installable entropy sources or the like. In order to get SqueakElib running in Pharo I need crypto and we may as well do it right. Cheers, Robert On 10/19/2015 02:28 PM, Ron Teitelbaum wrote: > Hi Robert, > > You are already on the Cryptograph repo on SqueakSource.com as an admin. > Please feel free to reorg if you like. > > Let me know if you have trouble resurrecting your account. > > All the best, > > Ron > >> -----Original Message----- >> From: squeak-dev-bounces(a)lists.squeakfoundation.org [mailto:squeak-dev- >> bounces(a)lists.squeakfoundation.org] On Behalf Of Robert Withers >> Sent: Monday, October 19, 2015 1:53 PM >> To: squeak-dev(a)lists.squeakfoundation.org >> Subject: Re: [squeak-dev] [Pharo-dev] [Cryptography port to Pharo] >> RandomGenerator class>>unpredictableStringsDo: >> >> This is great guys. Is there a way to get this from the image? Good to get > it >> with an FFI/OSProcess call or something. >> >> Thank you, >> Robert >> >> On 10/19/2015 08:58 AM, Louis LaBrunda wrote: >>> Hi Guys, >>> >>> How about getting the CPU temperature. I think most CPUs support >>> "Digital Thermal Sensor" (I'm not sure about ARM). I think it is >>> seven bits. The real range should be less than that but it may be >>> enough to help add some entropy. >>> >>> Lou >>> >>> On Mon, 19 Oct 2015 07:39:19 -0400, Robert Withers >>> <robert.w.withers(a)gmail.com> wrote: >>> >>>> Hi Ron , nice to see you too! It has been a number of years, hasn't it? >>>> Crypto is timestamped back in 2010, so there is is. I hope these have >>>> been kind years to you, as they have for me. >>>> >>>> I love the idea of optional sources of entropy, depending on the >>>> deployed capabilities. So there are our mouse points and such, >>>> because they ought to be optional. >>>> >>>> What are some reliably present sources in the most minimal situation? >>>> If we could define minimal as an image with no image level I/O beyond >>>> file I/O, I would think we'd have: Kernel, System, Collections, >>>> Compiler and FFI. Some intransitives in that scope for entropy would be >> grand. >>>> >>>> I was thinking to take 5 millisecondClockValues, separated by 4 >>>> non-secure random intervals: take the low order byte of the 4 >>>> intervals and reverse & concat them, as a entropic source. >>>> >>>> I can coordinate these changes. Ron, could you add me to the >>>> Cryptography team so I can upload the Pharo Cryptography >> #bleedingEdge? >>>> >>>> Thanks and I look forward to more, :) >>>> >>>> Robert >>>> >>>> On 10/18/2015 02:38 PM, Ron Teitelbaum wrote: >>>>> Hi Robert, >>>>> >>>>> Nice to see you! >>>>> >>>>> Looks interesting I know that Chris did something gathering sources of >> entropy. Seems like the more the better. Could you just make the entropy >> sources optional such that if they exist we use them? I would have to go >> back and see what Chris did but he was following suggestions from >> Schneider in his secureRandom. >>>>> >>>>> All the best, >>>>> >>>>> Ron Teitelbaum >>>>> >>>>>> -----Original Message----- >>>>>> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On >>>>>> Behalf Of Robert Withers >>>>>> Sent: Sunday, October 18, 2015 5:00 AM >>>>>> To: The general-purpose Squeak developers list; Pharo Development >>>>>> List >>>>>> Subject: Re: [Pharo-dev] [Cryptography port to Pharo] >>>>>> RandomGenerator >>>>>> class>>unpredictableStringsDo: >>>>>> >>>>>> I'm sorry, I forgot the code. I list the existing method, followed >>>>>> by my modified Pharo method below. I welcome any feedback. >>>>>> >>>>>> Regards, >>>>>> Robert >>>>>> >>>>>> --- >>>>>> Existing: >>>>>> unpredictableStringsDo: aBlock >>>>>> "Enumerate sources of information from my environment that >> should >>>>>> be generally hard to guess." >>>>>> | time | >>>>>> time := Time millisecondsToRun: >>>>>> [ aBlock >>>>>> value: World imageForm bits compressToByteArray ; >>>>>> value: Sensor mousePoint x asString ; >>>>>> value: Sensor mousePoint y asString ; >>>>>> value: Time millisecondClockValue asByteArray ; >>>>>> value: Date today asString ; >>>>>> value: Time now asString ; >>>>>> value: Display extent asString. >>>>>> 100 timesRepeat: [ aBlock value: UUID new ]. >>>>>> #(vmVersion platformName primVmPath imageName >> platformSubtype >>>>>> datedVersion lastQuitLogPosition vmStatisticsReportString >>>>>> imageName) >>>>>> collect: >>>>>> [ : each | >>>>>> aBlock value: (SmalltalkImage current perform: each) >> asByteArray >>>>>> ] ]. >>>>>> aBlock >>>>>> value: time asByteArray; >>>>>> "maybe the pointer has moved, hit it again." >>>>>> value: Sensor mousePoint asString ; >>>>>> value: Time millisecondClockValue asByteArray >>>>>> >>>>>> --- >>>>>> Pharo port: >>>>>> unpredictableStringsDo: aBlock >>>>>> "Enumerate sources of information from my environment that >> should >>>>>> be generally hard to guess." >>>>>> >>>>>> | time | >>>>>> time := Time millisecondsToRun: >>>>>> [ aBlock >>>>>> value: Time millisecondClockValue asByteArray ; >>>>>> value: Date today asString ; >>>>>> value: Time now asString. >>>>>> 100 timesRepeat: [ aBlock value: UUID new ]. >>>>>> #(version primImagePath imagePath datedVersion >>>>>> lastQuitLogPosition) >>>>>> collect: >>>>>> [ : each | >>>>>> aBlock value: (SmalltalkImage current perform: each) >> asByteArray >>>>>> ] ]. >>>>>> aBlock >>>>>> value: time asByteArray; >>>>>> value: Time millisecondClockValue asByteArray >>>>>> >>>>>> >>>>>> On 10/18/2015 04:23 AM, Robert Withers wrote: >>>>>>> This is a message intended for anyone who was on the Cryptography >> team. >>>>>>> I recently ported it to Pharo and had to make changes to >>>>>> RandomGenerator >>>>>>> class>>unpredictableStringsDo:. This certainly removed some >>>>>>> class>>uncertainty >>>>>>> from the results of this message. My question is what should I do >>>>>>> about that? This method seems to require non-headless, as it is >>>>>>> checking the mouse point and such. This being a crypto >>>>>>> cornerstone, what the best answer here. >>>>>>> >>>>>>> Thank you, >>>>>>> Robert >>>>> >>>>> >>>>> >>>> >>> ----------------------------------------------------------- >>> Louis LaBrunda >>> Keystone Software Corp. >>> SkypeMe callto://PhotonDemon >>> mailto:Lou@Keystone-Software.com http://www.Keystone-Software.com >>> >>> > > >

Oct. 19, 2015

Re: [Pharo-dev] Is storing a setting supposed to work in latest version?

by Juraj Kubelka

It is already integrated. Thanks Marcus! Cheers, Juraj > On Oct 19, 2015, at 12:33, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > > There is a bug: https://pharo.fogbugz.com/f/cases/16816/Storing-System-Settings-produces-er… > > Slice included. > Cheers, > Juraj > >> On Oct 19, 2015, at 12:21, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> When I press Store Setting in the Settings Browser, I get a DNU. >> How can I save a setting now? >> >> Stef >> >

Oct. 19, 2015

Re: [Pharo-dev] [squeak-dev] The Trunk: System-mt.771.mcz

by Chris Muller

> I quite like being able to make several changes within the same minute because I can tell that they were related > changes. With second granularity I have no chance. Just truncate the timeStamps to whatever granularity you want to group by.. DateAndTime now asDuration truncateTo: 1 minute > Do you have a programmatic reason for wanting second granularity? I thought his case sounds compelling. Is there any harm to have finer granularity? > What to others think? Are there workflow implications to the granularity of time stamps?

Oct. 19, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50393 Home: https://github.com/pharo-project/pharo-core

Oct. 19, 2015

[pharo-project/pharo-core] d375b5: 50393

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d375b50bd1a89ed16808aece1f0525a4058a488f https://github.com/pharo-project/pharo-core/commit/d375b50bd1a89ed16808aece… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-10-19 (Mon, 19 Oct 2015) Changed paths: M Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/buildVariableMenuFor_variablesFrom_menuItemBy_.st M Nautilus.package/PackageTreeNodeModel.class/instance/event handling/openFloatingEditorToRenameFromNodeMorph_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50392.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50393.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50392.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50393.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Settings-Tests.package/AbstractStoredSettingTest.class/README.md A System-Settings-Tests.package/AbstractStoredSettingTest.class/definition.st A System-Settings-Tests.package/AbstractStoredSettingTest.class/instance/tests/testEqual.st A System-Settings-Tests.package/AbstractStoredSettingTest.class/instance/tests/testHash.st A System-Settings-Tests.package/AbstractStoredSettingTest.class/instance/tests/testPrintOn.st A System-Settings-Tests.package/AbstractStoredSettingTest.class/instance/tests/testPrintOn2.st A System-Settings-Tests.package/SettingBrowserTest.class/README.md A System-Settings-Tests.package/SettingBrowserTest.class/definition.st A System-Settings-Tests.package/SettingBrowserTest.class/instance/tests/testOpening.st M System-Settings-Tests.package/SystemSettingsPersistenceTest.class/instance/running/setUp.st M System-Settings-Tests.package/SystemSettingsPersistenceTest.class/instance/tests/testAllStoredSettings.st A System-Settings-Tests.package/SystemSettingsPersistenceTest.class/instance/tests/testWriteStream.st A System-Settings.package/AbstractStoredSetting.class/instance/comparing/=.st A System-Settings.package/AbstractStoredSetting.class/instance/comparing/hash.st A System-Settings.package/AbstractStoredSetting.class/instance/printing/printOn_.st R System-Settings.package/StoredSetting.class/instance/comparing/=.st R System-Settings.package/StoredSetting.class/instance/comparing/hash.st A System-Settings.package/SystemSettingsPersistence.class/instance/accessing/ensureFileReference.st M System-Settings.package/SystemSettingsPersistence.class/instance/streams/writeStream.st R System-Settings.package/SystemSettingsPersistence.class/instance/tests/testOpening.st Log Message: ----------- 50393 16816 Storing System Settings produces error when preference directory does not exist https://pharo.fogbugz.com/f/cases/16816 16809 Sort the variables from each class in the variables-menu alphabetically https://pharo.fogbugz.com/f/cases/16809 16810 Floating editor size too large for Nautilus package pane https://pharo.fogbugz.com/f/cases/16810 http://files.pharo.org/image/50/50393.zip

Oct. 19, 2015

Re: [Pharo-dev] Is storing a setting supposed to work in latest version?

by Juraj Kubelka

There is a bug: https://pharo.fogbugz.com/f/cases/16816/Storing-System-Settings-produces-er… Slice included. Cheers, Juraj > On Oct 19, 2015, at 12:21, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > When I press Store Setting in the Settings Browser, I get a DNU. > How can I save a setting now? > > Stef >

Oct. 19, 2015

Re: [Pharo-dev] Storing System Settings using STON

by Juraj Kubelka

Here it is: ClassStoredSetting ThemeIconsStoredSetting LogicalFontStoredSetting StrikeFontSetStoredSetting StrikeFontStoredSetting FileLocatorStoredSetting AbsolutePathStoredSetting RelativePathStoredSetting Cheers, Juraj > On Oct 18, 2015, at 06:20, stepharo <stepharo(a)free.fr> wrote: > > Can you past the full tree so that I understand? > > > >

Oct. 19, 2015

Re: [Pharo-dev] Storing System Settings using STON

by Juraj Kubelka

Hi, thank you for the report. Fix in the inbox: https://pharo.fogbugz.com/f/cases/16816/Storing-System-Settings-produces-er… Cheers, Juraj > On Oct 19, 2015, at 07:09, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Le 12/10/2015 19:45, Juraj Kubelka a Ã©crit : >> Hi, >> >> we have a slice that introduce new storage solution for System Settings. >> See: https://pharo.fogbugz.com/f/cases/16681/Storing-System-Settings-using-STON >> >> You can load it using: >> >> Gofer it >> smalltalkhubUser: 'Pharo' project: 'Pharo50Inbox'; >> package: 'SLICE-Issue-16681-Storing-System-Settings-using-STON'; >> load. >> >> When you open the Setting Browser, you can see that every setting has >> new items in context menu: >> >> >> Thanks for reviewing it. >> Cheers, >> Juraj > > Hi, > > Thank you for that. > When I make store settings for the first time I have an exception on the > write stream because the file doesn't exist. I had to create the folder > 5.0 and an empty file to get it right. > In Pharo 50392 on Linux. > > I join the stack: > > FileHandle>>streamError > FileHandle>>writeStream > FileSystem>>writeStreamOn: > FileReference>>writeStream > SystemSettingsPersistence>>writeStream > SystemSettingsPersistence>>storeExactStoredSettings: > SystemSettingsPersistence>>storeStoredSettings: > SystemSettingsPersistence>>storeSettingNodes: > SystemSettingsPersistence>>storeSettingNodes > SettingTree>>storeSettingNodes > SettingBrowser>>storeSettings > PluggableButtonMorph>>performAction: > [ :m | > (m containsPoint: evt cursorPoint) > ifTrue: [ m enabled > ifTrue: [ m performAction: evt ] ] ] in > PluggableButtonMorph>>mouseUp: in Block: [ :m | ... > Array(SequenceableCollection)>>do: > PluggableButtonMorph>>mouseUp: > PluggableButtonMorph(Morph)>>handleMouseUp: > MouseButtonEvent>>sentTo: > PluggableButtonMorph(Morph)>>handleEvent: > PluggableButtonMorph(Morph)>>handleFocusEvent: > [ ActiveHand := self. > ActiveEvent := anEvent. > result := focusHolder > handleFocusEvent: > (anEvent transformedBy: (focusHolder transformedFrom: self)) ] in > HandMorph>>sendFocusEvent:to:clear: in Block: [ ActiveHand := self.... > BlockClosure>>on:do: > WorldMorph(PasteUpMorph)>>becomeActiveDuring: > HandMorph>>sendFocusEvent:to:clear: > HandMorph>>sendEvent:focus:clear: > HandMorph>>sendMouseEvent: > HandMorph>>handleEvent: > HandMorph>>processEvents > [ :h | > ActiveHand := h. > h processEvents. > ActiveHand := nil ] in WorldState>>doOneCycleNowFor: in Block: [ :h | ... > Array(SequenceableCollection)>>do: > WorldState>>handsDo: > > > -- > > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France >

Oct. 19, 2015