Excuse the silly question but what exactly is a plugin? Is it the code which is called by the primitive? The problem is not within the pharo code itself, right? It is the result of the primitive, which is wrong, right?
Can I do something more to solve the problem or should I try to write a workaround for me (exception handler and grab the result of the request)? Regards Sabine Am Sonntag, 1. März 2015 schrieb Sven Van Caekenberghe : > Arg, and on Linux it works too. > > Below the image layer, the normal Pharo code that we see, both the Socket > plugin and the SSL plugin are three totally different implementations. This > is really frustrating. The Mac code originates from *before* Mac OS X came > on the scene ! Today, Mac OS X could probably use 99% of the Linux version. > > > On 01 Mar 2015, at 10:29, Sabine Manaa <manaa.sab...@gmail.com > <javascript:;>> wrote: > > > > Hi, > > > > I tried on Windows, there it works. > > > > Sabine > > > > > > > > -- > > View this message in context: > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p4808634.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >
