Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

> On 02 Mar 2015, at 12:46, Sabine Manaa wrote: > > Hi Sven, > > great - it works! Thank you very much for your help! You're welcome. BTW, a good bug report and a repeatible case makes all the difference. This is *very* important for us to make progress. > Regards > Sabine > > 2015-03-02 1

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Sven, great - it works! Thank you very much for your help! Regards Sabine 2015-03-02 11:02 GMT+01:00 Sven Van Caekenberghe-2 [via Smalltalk] < ml-node+s1294792n4808807...@n4.nabble.com>: > Sabine, > > Here is a possible fix that works for me, this still has to be tested more > broadly, but I

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Sabine, Here is a possible fix that works for me, this still has to be tested more broadly, but I think it will be good. Could you please try it by manually loading the package ? === Name: Zodiac-Core-SvenVanCaekenberghe.36 Author: SvenVanCaekenberghe Time: 2 March 2015, 11:05:04.004975 am UUID

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Sven, thanks for the explanation. If the problem would be in Smalltalk I could _try_ to find a solution but I am not able to go into primitives. Concerning my workaround: If remove the line where the exception is thrown in >>fillBytes:startingAt:count: "processedCount < 0 ifTrue: [ ^ self sslE

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

> On 01 Mar 2015, at 13:14, Sabine Manaa wrote: > > 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? Yes, we're talking

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

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 workaro

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

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 p

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

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.

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

We got a repeatable case: https://pharo.fogbugz.com/f/cases/15022/ZdcSecureSocketStream-trouble-reading-response-with-no-content-length-and-connection-close ZnClient new get: 'https://user.gini.net/login' Now we just need a solution ;-) > On 28 Feb 2015, at 11:08, Johan Brichau wrote: > > Hi

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Sabine, I took a closer look and indeed, that strategy probably only works in our usecase where it’s a download of a zip tarball from github that fails in the Metacello code. Because on the second try, the github cache was already created, Metacello no longer sends the request to github and

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Johan, I tried this: I put an exception handler around and on error, I tried again, but the error still occurs. Regards Sabine 2015-02-28 8:54 GMT+01:00 Johan Brichau-2 [via Smalltalk] < ml-node+s1294792n4808485...@n4.nabble.com>: > This sounds familiar to what we reported a while back: > >

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

I could send password etc to you for debugging of you want. Am Freitag, 27. Februar 2015 schrieb Sven Van Caekenberghe-2 [via Smalltalk] : > > > On 27 Feb 2015, at 21:18, Sabine Manaa <[hidden email] > > wrote: > > > > Hi Sven, > > > > thank

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Sven, the error occurs on my Mac. Regards Sabine Am Freitag, 27. Februar 2015 schrieb Sven Van Caekenberghe : > > > On 27 Feb 2015, at 21:18, Sabine Manaa > wrote: > > > > Hi Sven, > > > > thank you for your hints. > > > > Indeed, the variable @in of ZdcSecureSocketStream has the string > "

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

This sounds familiar to what we reported a while back: http://forum.world.st/Mac-sqDecryptSSL-returning-SQSSL-GENERIC-ERROR-on-errSSLClosedGraceful-from-SSLRead-td4785735.html

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

> On 27 Feb 2015, at 21:18, Sabine Manaa wrote: > > Hi Sven, > > thank you for your hints. > > Indeed, the variable @in of ZdcSecureSocketStream has the string > "ZnInvalidUTF8: Illegal leading byte for utf-8 encoding" in its utf-8 > variable. That is normal: the in buffer contains encrypt

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Sven, thank you for your hints. Indeed, the variable @in of ZdcSecureSocketStream has the string "ZnInvalidUTF8: Illegal leading byte for utf-8 encoding" in its utf-8 variable. Can you tell me, what to add to the pharo code that the encoding is correct/so that is equal to the curl command? c

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Sabine, > On 27 Feb 2015, at 16:36, Sabine Manaa wrote: > > Hi Sven, > Hi all, > > I try to send a curl command (which works at command line) from Pharo. > I get the error: "SSL Exception: decrypt failed code:5" > > The working command line command is: > > curl -v -H 'Accept: applicatio

Re: [Pharo-users] Zinc SSL Exception: decrypt failed code:5

Hi Sven, Hi all, I try to send a curl command (which works at command line) from Pharo. I get the error: "SSL Exception: decrypt failed code:5" The working command line command is: curl -v -H 'Accept: application/json' -u 'aUser:aPassword' 'https://user.xxx.net/oauth/token?grant_type=clien