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

Re: [Pharo-project] 1.3-Core

by Sven Van Caekenberghe

Alexandre, On 12 May 2011, at 21:38, Alexandre Bergel wrote: > Hi! > > I cannot open a remote repository apparently with the latest 1.3-core. Gofer and Monticello browser complain. I use: > > Pharo1.3a > Latest update: #13196 > > I am behind a proxy, so I am not sure where the problem comes from (the image or the VM). > It works well with 1.3-Oneclick however. > > Cheers, > Alexandre This probably has something to do with Zn now being used for HTTP, proxies should be supported, but I have not tested them myself. Can you try a simple thing like: ZnClient get: 'http://zn.stfx.eu/zn/small.html' Have a look at ZnNetworkingUtils class>>#socketStreamToUrl: Does this make the right decision in your setup ? Sven

May 12, 2011

[Pharo-project] 1.3-Core

by Alexandre Bergel

Hi! I cannot open a remote repository apparently with the latest 1.3-core. Gofer and Monticello browser complain. I use: Pharo1.3a Latest update: #13196 I am behind a proxy, so I am not sure where the problem comes from (the image or the VM). It works well with 1.3-Oneclick however. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 12, 2011

Re: [Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSession for Pharo/Squeak and other Smalltalk implementations

by Jan van de Sandt

Hi, No the VASt plugin is not open source. It is not really a plugin. It is just Smalltalk code that calls the OpenSSL lib using external functions (the FFI of VASt). The OpenSSL library delivered with VASt is a very old version and there are some concurrency issues on windows. So I do think that Instantiations is interested in an upgrade. If technically possible than perhaps some kind of cooperation is possible. Two years ago I created an open source alternative for VASt users on windows WinHttpClient & WinCrypt. This is of no use for Zinc because it depends on windows http stack :-( Jan. [1] http://blog.doit.st/2009/06/17/introducing-winhttpclient-for-va-smalltalk/ On Thu, May 12, 2011 at 5:21 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > Hi Jan, > > On 12 May 2011, at 17:07, Jan van de Sandt wrote: > > > Hello, > > > > I can help test the client part of a HTTPS implementation. Currently I > use Zinc-HTTP together with stunnel. > > > > Note that VA Smalltalk uses OpenSSL on Linux and Windows. So it is > possible to use OpenSSL on windows as well [1]. > > > > Jan. > > > > [1] http://www.openssl.org/related/binaries.html > > That is interesting. > Is the VAST plugin open source ? > > And of course, thanks for the offer, I knew you would be interested ! > > Sven > > >

May 12, 2011

[Pharo-project] [update 1.3] #13197

by StÃ©phane Ducasse

13197 ----- Issue 4204: PluggabeMenuItemSpec show submenu even is disabled. Thanks benjamin van ryseghem.

May 12, 2011

[Pharo-project] [COTDC] 63 - MimeConverter

by laurent laffont

Today: MimeConverter Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

May 12, 2011

Re: [Pharo-project] [COTDC] 62 - MIMEType

by laurent laffont

On Tue, May 10, 2011 at 8:31 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: MIMEType > I guess and represent the content type of a file. For a description of what is MIME, see http://en.wikipedia.org/wiki/Internet_media_type http://en.wikipedia.org/wiki/MIME Examples: MIMEType forFileNameReturnMimeTypesOrDefault: 'index.html'. MIMEType fromMIMEString: 'application/zip'. Laurent. > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

May 12, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 61 - InternetConfiguration

by laurent laffont

On Thu, May 12, 2011 at 4:17 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On May 12, 2011, at 3:41 PM, laurent laffont wrote: > > > On Mon, May 9, 2011 at 8:34 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > > Today: InternetConfiguration > > > > I read several parameters related to the OS network preferences, through > the InternetConfigPlugin VM module. > > > > For example, to get the default path where downloaded files should be > placed: > > > > InternetConfiguration getDownloadPath > > > > > > (That said, it's not used in the image). > > > > It is... it's in the startup list and setting the Proxy at SCG since years > automatically. > (it's only working on the Mac, though) > Thanks for the info, added. Laurent. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

May 12, 2011

Re: [Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSessionforPharo/Squeak and other Smalltalk implementations

by StÃ©phane Ducasse

On May 12, 2011, at 4:31 PM, Rob Withers wrote: > Stef, > > The Cryptography project, which has Cryptography, CryptographyPlugins, LayeredProtocol and SSL packages are all tagged with pharo. When I look at the pharo tag, none of these show up. Do they need to be releases? By tag I do not know :) > How can I use the pharo tag from inside of Pharo, with the Monticello Browser? > > Rob > > -----Original Message----- From: StÃ©phane Ducasse > Sent: Thursday, May 12, 2011 10:10 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSessionforPharo/Squeak and other Smalltalk implementations > > Or you keep > Cryptology and publish a pharo tag. > > Stef > > On May 12, 2011, at 3:52 PM, Rob Withers wrote: > >> Try this, after loading the Crypto packages. I haven't tried it myself, yet, as I only got on this list and loaded Pharo a few days ago, but I will probably dig into it over the weekend. I did load Crypto, though. >> >> http://www.squeaksource.com/Cryptography/SSL-mtf.16.mcz >> >> Is there a Pharo repository I could drop ported code into? >> >> Regards, >> Rob >> >> >> >> >> >> -----Original Message----- From: Sven Van Caekenberghe >> Sent: Tuesday, May 10, 2011 1:42 PM >> To: Pharo Project >> Subject: [Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSession forPharo/Squeak and other Smalltalk implementations >> >> SSL/HTTPS - SecureSocketStream/SSLSession for Pharo/Squeak and other Smalltalk implementations >> >> >> HTTP client and server functionality has become an essential part of any Smalltalk implementation. There exist various open source solutions delivering this functionality. >> >> Users quickly find out that HTTPS is not as readily available as HTTP. Although a solution exists in the form of SqueakSSL, it is not easily portable to Pharo and certainly not to other Smalltalk implementations. Furthermore, SqueakSSL is incomplete and more a working proof of concept than a high quality, high performance, maintainable piece of code, partially because of its dependence on the internals of SocketStream. >> >> Hence, some people wanting HTTPS on Pharo as well as one organisation have come foreword with a bounty to force a solution. Here are the requirements, a plan of action and a number of steps to build such a solution. >> >> >> First of all, it would be stupid not to start from the work already done for SqueakSSL. Any new solution should start from the existing plugin, from the existing set of primitives and from the current implementation of these primitives for the Windows, Mac OS X and Linux platforms. >> >> The Smalltalk part of the solution should be as platform independent as possible. We therefor need a new, clean implementation of SocketStream, with proper internal buffering and optimised versions of the bulk input and output primitives. The code should be time and space efficient. At first, only binary I/O is needed. Encoding/decoding is best done by wrapping the stream. Maybe a bivalent stream could be an option. The current ASCII support in quite limited. >> >> Next a SecureSocketStream can be implemented using this clean base combined with the SSLSession primitives. Here too, time and space efficiency are important although SSL will by definition be less efficient. >> >> Eventually, HTTP frameworks can then use this SecureSocketStream to actually implement HTTPS. Although the primary requirement is client functionality, server functionality should be provided as well. >> >> Next the existing issues with certificates need to be resolved, on all 3 platforms. >> >> Finally, the C code of the plugin for each of the 3 platforms needs to be cleaned up and improved where necessary. This requires contributions from developers who know and understand a platform as well as how SSL is supposed to work. Furthermore they have to understand and be motivated to work on Smalltalk plugins. Up to 3 different developers might be needed. >> >> The current implementation on Mac OS X does not seem to (directly) use the standard OpenSSL library from Linux although this library exists on Mac OS X. This could be an opportunity to reduce the number of implementations of the plugin to 2 API's. >> >> Needless to say the whole implementation should be open source licensed (MIT), be documented and have a number of units tests to cover it's main functionality as well edge cases encountered in the field. >> >> Friendly cooperation with other open source projects in the Smalltalk world is a plus. This project should benefit the whole community. >> >> >> The bounty should be split in different parts. >> >> The first part is setting up the new project, delivering the new SocketStream, SSLSession and SecureSocketStream, including the HTTPS client proof of concept. Traction within the community has to be developed. >> >> Next the issues with the plugin have to be identified. Then the work on the plugin code for each platform has to be defined and 3 more bounties could be offered. >> >> The goal should be to include the plugin in VM's by default. >> >> With a proper solution to the plugin issues, SSL server functionality should be no problem. >> >> >> I offer to take on part one and help manage the coordination of this project. >> >> So is there anyone capable and willing to help out on the plugin on on one or more platforms for part of the bounty ? >> >> Are there others who wish to raise the bounty ? >> >> We will need a couple of good beta testers who understand this field as well. >> >> >> Sven >> >> >> > > >

May 12, 2011

Re: [Pharo-project] Problem with CompiledMethodTrailer

by StÃ©phane Ducasse

Igor could you open a ticket that we do not forget. Stef > It seems like that with this change i opened a can of worms. > There are some tricky logic somewhere ,which uninstalls methods from > classes and then adds them back. > So, i added #dropSourcePointer at uninstalling .. then compilation > becomes too slow (because embedding source code using #becomeForward: > ). Then i changed #dropSourcePointer to actually erase the trailer > without using #become .. > but then some methods lost their source. > >> Decompiled code for old methods which were moved as part of a truncation, >> where the new versions have the exact same, and correct source doesn't sound >> like the end of the world to me. The method itself did not actually change. >> >> Cheers, >> Henry >> > > > -- > Best regards, > Igor Stasenko AKA sig. >

May 12, 2011

[Pharo-project] [update 1.3] #13196

by StÃ©phane Ducasse

13196 ----- - Issue 4130: Zinc should be added to core. Thanks sven van caekenberghe. Stef

May 12, 2011