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

Re: [Pharo-project] Issue 3797 in pharo: ServerDirectory depends on MorphicExplorer

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3639 Comment #3 on issue 3797 by marcus.d...(a)gmail.com: ServerDirectory depends on MorphicExplorer http://code.google.com/p/pharo/issues/detail?id=3797 (No comment was entered for this change.)

March 24, 2011

Re: [Pharo-project] Issue 3639 in pharo: ServerDirectory contains a lot of old and unused code

by pharo＠googlecode.com

Comment #2 on issue 3639 by marcus.d...(a)gmail.com: ServerDirectory contains a lot of old and unused code http://code.google.com/p/pharo/issues/detail?id=3639 Issue 3797 has been merged into this issue.

March 24, 2011

Re: [Pharo-project] Issue 3851 in pharo: Remove all classes in Network-RemoteDirectory

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3639 Comment #1 on issue 3851 by marcus.d...(a)gmail.com: Remove all classes in Network-RemoteDirectory http://code.google.com/p/pharo/issues/detail?id=3851 (No comment was entered for this change.)

March 24, 2011

Re: [Pharo-project] Issue 3639 in pharo: ServerDirectory contains a lot of old and unused code

by pharo＠googlecode.com

Comment #1 on issue 3639 by marcus.d...(a)gmail.com: ServerDirectory contains a lot of old and unused code http://code.google.com/p/pharo/issues/detail?id=3639 Issue 3851 has been merged into this issue.

March 24, 2011

[Pharo-project] Issue 3859 in pharo: Pluggin control

by pharo＠googlecode.com

Status: FixToInclude Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3859 by stephane...(a)gmail.com: Pluggin control http://code.google.com/p/pharo/issues/detail?id=3859 Hello, just as outcome of previous discussion about security. I think that we missing a mechanism(s) in VM, which will prevent loading new modules into running system, to ensure that no external code could compromise a system security. In terms of implementation a change is quite simple: - add a flag into VM's state, named moduleLoadingEnabled - initially this flag should be set to true during system startup - add a primitive which resets this flag Then modify ioLoadModule: OfLength: to fail unconditionally if module loading is disabled. In practice this means that knowing a secure set of modules you are need for your deployment scenario and have them all loaded at startup, you intentionally disabling a module loading mechanism, to prevent any chance to interact with modules which could compromise your security model. There's also a missing bit in VM api to explicitly load the module with given name. However it is included in IA32ABIPlugin (#primLoadLibrary), but then maybe you don't want to have IA32ABIPlugin at first place, that's why i proposing to promote this primitive to core VM API. So, by having these bits working, one could implement sandbox mode quite easily, by doing something like following during image startup: self deployed ifTrue: [ " make sure we loaded modules we will need" #( 'PluginA' 'PluginB' .... 'PluginZ' ) do: [ :each | Smalltalk loadModule: each ]. Smalltalk disableModuleLoading. ]. Then later any code that will try to use plugins, that is not loaded before you disabled module loading mechanism, will simply fail. This will be good addition to existing security mechanisms. Attachments: SmalltalkImage-loadModule.st 424 bytes SmalltalkImage-disableModuleLoading.st 460 bytes

March 24, 2011

Re: [Pharo-project] Issue 3858 in pharo: On windows, Error when dropping an image in the vm

by pharo＠googlecode.com

Comment #2 on issue 3858 by stephane...(a)gmail.com: On windows, Error when dropping an image in the vm http://code.google.com/p/pharo/issues/detail?id=3858 the person downloaded the moose one click image.

March 24, 2011

Re: [Pharo-project] Issue 3858 in pharo: On windows, Error when dropping an image in the vm

by pharo＠googlecode.com

Comment #1 on issue 3858 by Torsten....(a)astares.de: On windows, Error when dropping an image in the vm http://code.google.com/p/pharo/issues/detail?id=3858 can you be more specific: - which error? - which VM (Cog or standard), click on the file in Explorer, select Properties and click on the Versions tab - which Pharo image (1.2 or 1.3, which update number - see about box) - which Windows Version - is an *.ini file beside the VM executable?

March 24, 2011

[Pharo-project] Issue 3858 in pharo: On windows, Error when dropping an image in the vm

by pharo＠googlecode.com

Status: Accepted Owner: cy.delau...(a)gmail.com New issue 3858 by cy.delau...(a)gmail.com: On windows, Error when dropping an image in the vm http://code.google.com/p/pharo/issues/detail?id=3858 On windows, when you want to open an image by dropping it on the vm icon, The image is opened with an Error

March 24, 2011

Re: [Pharo-project] Issue 2786 in pharo: Mixed concerns on Object>>saveOnFile

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #2 on issue 2786 by marcus.d...(a)gmail.com: Mixed concerns on Object>>saveOnFile http://code.google.com/p/pharo/issues/detail?id=2786 saveOnFile is categorized *morphic, but Morph reimplements it. No senders and not a good idea anyway. Attached changeset removes it Attachments: KillSaveOnFile.1.cs 133 bytes

March 24, 2011

Re: [Pharo-project] Issue 954 in pharo: Baseline test results code & scripts

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 954 by marcus.d...(a)gmail.com: Baseline test results code & scripts http://code.google.com/p/pharo/issues/detail?id=954 Hmm.... I take the liberty of closing this entry as there was no activity since July 2009 *and* this issue was more a placeholder for an ongoing project, not an actionable issue.

March 24, 2011