February 2015 - Pharo-users

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

by Sabine Manaa

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+s1294792n4808485h30(a)n4.nabble.com>: > This sounds familiar to what we reported a while back: > > http://forum.world.st/Mac-sqDecryptSSL-returning-SQSSL-GENERIC-ERROR-on-err… > > Unfortunately, we did not investigate any further. Instead, we work around > the bug by just retrying the connection on this failure as it always works > on a second try. > > Johan > > On 27 Feb 2015, at 23:36, Sven Van Caekenberghe <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4808485&i=0>> wrote: > > > On 27 Feb 2015, at 21:18, Sabine Manaa <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4808485&i=1>> 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 encrypted binary data, the out > buffer will contain the cleartext (but still in binary). > > Can you tell me, what to add to the pharo code that the encoding is > correct/so that is equal to the curl command? > > > I don't think there is an encoding problem: the charset is set to utf-8 > which will be picked up. Besides, the returned content is plain ascii > anyway. > > The issue is probably the Connection:close and the missing Content-Length. > This means that the HTTPS stream has to be read until the end. I have seen > this fail in the past in rare cases. > > Are you on Windows ? > > Could you try on Linux ? > > comparison of headers: they seem to be equal, also the content type is in > both cases 'application/json;charset=UTF-8' > The ZnResponse headers: > a ZnHeaders( > same 'Cache-Control'->#('no-cache, no-store, max-age=0, must-revalidate' > 'no-store') > same 'Connection'->'close' > same 'Content-Type'->'application/json;charset=UTF-8' > same 'Date'->'Fri, 27 Feb 2015 20:02:40 GMT' > same 'Expires'->'0' > same 'Pragma'->#('no-cache' 'no-cache') > same 'Set-Cookie'->'crbid=10.1.8.3:49247_mt03.prod.gini.net; path=/' > same 'Strict-Transport-Security'->'max-age=31536000 ; includeSubDomains' > same 'X-Application-Context'->'0.3:8080' > same 'X-Content-Type-Options'->'nosniff' > same 'X-Frame-Options'->'DENY' > same 'X-Xss-Protection'->'1; mode=block' ) > > result of curl command at command line > < HTTP/1.1 200 OK > same < Date: Fri, 27 Feb 2015 17:58:37 GMT > same < X-Content-Type-Options: nosniff > same < X-XSS-Protection: 1; mode=block > same < Cache-Control: no-cache, no-store, max-age=0, must-revalidate > same < Pragma: no-cache > same < Expires: 0 > same < Strict-Transport-Security: max-age=31536000 ; includeSubDomains > same < X-Frame-Options: DENY > same < X-Application-Context: 0.3:8080 > < Cache-Control: no-store > < Pragma: no-cache > same < Content-Type: application/json;charset=UTF-8 > same < Connection: close > same < Set-Cookie: crbid=10.1.8.5:49387_mt05.prod.gini.net; path=/ > > regards > sabine > > 2015-02-27 16:58 GMT+01:00 Sven Van Caekenberghe-2 [via Smalltalk] > <[hidden email]>: > Sabine, > > On 27 Feb 2015, at 16:36, Sabine Manaa <[hidden email]> 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: application/json' -u 'aUser:aPassword' > 'https://user.xxx.net/oauth/token?grant_type=client_credentials' > > the result is something like: > {"access_token":"a31xxxa-2a22-4xx6c-938d-2bd3ae4a0629","token_type":"bearer","expires_in":42095,"scope":"write"} > > > My current Pharo code is: > | theZnClient | > theZnClient := ZnClient new > systemPolicy ; > https; > host: 'user.xxx.net'; > path: 'oauth/token?grant_type=client_credentials'; > username: 'aUser' password: 'aPassword'; > accept: ZnMimeType applicationJson; > get. > theZnClient inspect close. > > 'aPassword' and 'aUser' and xxx.net was replaced by me for security > reasons. > > In Pharo, I get a walkback with the error message > 'SSL Exception: decrypt failed [code:-5]' > > But I see, that the ZdcSecureSocketStream has the correct result > ({"access_token":...":"write"}) in its collection attribute at > utf-8 string and at latin1-string > > so, the request is done and the result is available but then it fails > here: > ZdcSecureSocketStream(Object)>>error: > ZdcSecureSocketStream>>sslException:code: > ZdcSecureSocketStream>>fillBytes:startingAt:count: in Block: [ ... > ZdcSecureSocketStream>>fillBytes:startingAt:count: > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBufferNoWait > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer > ZdcSecureSocketStream(ZdcOptimizedSocketStream)>>readInto:startingAt:count: > > ZnUTF8Encoder>>optimizedReadInto:startingAt:count:fromStream: > ZnUTF8Encoder>>readInto:startingAt:count:fromStream: > > Sven, I could send you the 'aPassword' and 'aUser' and the url by private > message. It would be fine if you could have a short look at it. > > The fact that there is readable text in the buffer of the > ZdcSecureSocketStream is good, because it means that things basically work. > > One reason why this is failing might be that Zn tries to read more than > there is available in the stream, when the content-length does not match. > Encoding problems could be part of the problem too. > > Could you compare curl -v or curl -D - output with the request/response > headers in Pharo ? Look for content-length and compare that with what it > already read or not. Is the connection kept alive ? Also look at > content-type and see if there is any charset encoding after > application/json. > > Sven > > Regards > Sabine > > > > -- > View this message in context: > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > To start a new topic under Pharo Smalltalk Users, email [hidden email] > To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click here. > NAML > > > View this message in context: Re: Zinc SSL Exception: decrypt failed code:5 > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 28, 2015

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

by Sabine Manaa

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 <manaa.sabine(a)gmail.com > <javascript:;>> 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 encrypted binary data, the out > buffer will contain the cleartext (but still in binary). > > > Can you tell me, what to add to the pharo code that the encoding is > correct/so that is equal to the curl command? > > I don't think there is an encoding problem: the charset is set to utf-8 > which will be picked up. Besides, the returned content is plain ascii > anyway. > > The issue is probably the Connection:close and the missing Content-Length. > This means that the HTTPS stream has to be read until the end. I have seen > this fail in the past in rare cases. > > Are you on Windows ? > > Could you try on Linux ? > > > comparison of headers: they seem to be equal, also the content type is > in both cases 'application/json;charset=UTF-8' > > The ZnResponse headers: > > a ZnHeaders( > > same 'Cache-Control'->#('no-cache, no-store, max-age=0, must-revalidate' > 'no-store') > > same 'Connection'->'close' > > same 'Content-Type'->'application/json;charset=UTF-8' > > same 'Date'->'Fri, 27 Feb 2015 20:02:40 GMT' > > same 'Expires'->'0' > > same 'Pragma'->#('no-cache' 'no-cache') > > same 'Set-Cookie'->'crbid=10.1.8.3:49247_mt03.prod.gini.net; path=/' > > same 'Strict-Transport-Security'->'max-age=31536000 ; includeSubDomains' > > same 'X-Application-Context'->'0.3:8080' > > same 'X-Content-Type-Options'->'nosniff' > > same 'X-Frame-Options'->'DENY' > > same 'X-Xss-Protection'->'1; mode=block' ) > > > > result of curl command at command line > > < HTTP/1.1 200 OK > > same < Date: Fri, 27 Feb 2015 17:58:37 GMT > > same < X-Content-Type-Options: nosniff > > same < X-XSS-Protection: 1; mode=block > > same < Cache-Control: no-cache, no-store, max-age=0, must-revalidate > > same < Pragma: no-cache > > same < Expires: 0 > > same < Strict-Transport-Security: max-age=31536000 ; includeSubDomains > > same < X-Frame-Options: DENY > > same < X-Application-Context: 0.3:8080 > > < Cache-Control: no-store > > < Pragma: no-cache > > same < Content-Type: application/json;charset=UTF-8 > > same < Connection: close > > same < Set-Cookie: crbid=10.1.8.5:49387_mt05.prod.gini.net; path=/ > > > > regards > > sabine > > > > 2015-02-27 16:58 GMT+01:00 Sven Van Caekenberghe-2 [via Smalltalk] > <[hidden email]>: > > Sabine, > > > > > On 27 Feb 2015, at 16:36, Sabine Manaa <[hidden email]> 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: application/json' -u 'aUser:aPassword' > > > 'https://user.xxx.net/oauth/token?grant_type=client_credentials' > > > > > > the result is something like: > > > > {"access_token":"a31xxxa-2a22-4xx6c-938d-2bd3ae4a0629","token_type":"bearer","expires_in":42095,"scope":"write"} > > > > > > My current Pharo code is: > > > | theZnClient | > > > theZnClient := ZnClient new > > > systemPolicy ; > > > https; > > > host: 'user.xxx.net'; > > > path: 'oauth/token?grant_type=client_credentials'; > > > username: 'aUser' password: 'aPassword'; > > > accept: ZnMimeType applicationJson; > > > get. > > > theZnClient inspect close. > > > > > > 'aPassword' and 'aUser' and xxx.net was replaced by me for security > reasons. > > > > > > In Pharo, I get a walkback with the error message > > > 'SSL Exception: decrypt failed [code:-5]' > > > > > > But I see, that the ZdcSecureSocketStream has the correct result > > > ({"access_token":...":"write"}) in its collection attribute at > > > utf-8 string and at latin1-string > > > > > > so, the request is done and the result is available but then it fails > here: > > > ZdcSecureSocketStream(Object)>>error: > > > ZdcSecureSocketStream>>sslException:code: > > > ZdcSecureSocketStream>>fillBytes:startingAt:count: in Block: [ ... > > > ZdcSecureSocketStream>>fillBytes:startingAt:count: > > > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBufferNoWait > > > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer > > > > ZdcSecureSocketStream(ZdcOptimizedSocketStream)>>readInto:startingAt:count: > > > ZnUTF8Encoder>>optimizedReadInto:startingAt:count:fromStream: > > > ZnUTF8Encoder>>readInto:startingAt:count:fromStream: > > > > > > Sven, I could send you the 'aPassword' and 'aUser' and the url by > private > > > message. It would be fine if you could have a short look at it. > > The fact that there is readable text in the buffer of the > ZdcSecureSocketStream is good, because it means that things basically work. > > > > One reason why this is failing might be that Zn tries to read more than > there is available in the stream, when the content-length does not match. > Encoding problems could be part of the problem too. > > > > Could you compare curl -v or curl -D - output with the request/response > headers in Pharo ? Look for content-length and compare that with what it > already read or not. Is the connection kept alive ? Also look at > content-type and see if there is any charset encoding after > application/json. > > > > Sven > > > > > Regards > > > Sabine > > > > > > > > > > > > -- > > > View this message in context: > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > > > > > > > > If you reply to this email, your message will be added to the discussion > below: > > > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > > To start a new topic under Pharo Smalltalk Users, email [hidden email] > > To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click > here. > > NAML > > > > > > View this message in context: Re: Zinc SSL Exception: decrypt failed > code:5 > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

Feb. 28, 2015

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

by Sabine Manaa

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] > <http:///user/SendEmail.jtp?type=node&node=4808442&i=0>> 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 encrypted binary data, the out > buffer will contain the cleartext (but still in binary). > > > Can you tell me, what to add to the pharo code that the encoding is > correct/so that is equal to the curl command? > > I don't think there is an encoding problem: the charset is set to utf-8 > which will be picked up. Besides, the returned content is plain ascii > anyway. > > The issue is probably the Connection:close and the missing Content-Length. > This means that the HTTPS stream has to be read until the end. I have seen > this fail in the past in rare cases. > > Are you on Windows ? > > Could you try on Linux ? > > > comparison of headers: they seem to be equal, also the content type is > in both cases 'application/json;charset=UTF-8' > > The ZnResponse headers: > > a ZnHeaders( > > same 'Cache-Control'->#('no-cache, no-store, max-age=0, must-revalidate' > 'no-store') > > same 'Connection'->'close' > > same 'Content-Type'->'application/json;charset=UTF-8' > > same 'Date'->'Fri, 27 Feb 2015 20:02:40 GMT' > > same 'Expires'->'0' > > same 'Pragma'->#('no-cache' 'no-cache') > > same 'Set-Cookie'->'crbid=10.1.8.3:49247_mt03.prod.gini.net; path=/' > > same 'Strict-Transport-Security'->'max-age=31536000 ; includeSubDomains' > > same 'X-Application-Context'->'0.3:8080' > > same 'X-Content-Type-Options'->'nosniff' > > same 'X-Frame-Options'->'DENY' > > same 'X-Xss-Protection'->'1; mode=block' ) > > > > result of curl command at command line > > < HTTP/1.1 200 OK > > same < Date: Fri, 27 Feb 2015 17:58:37 GMT > > same < X-Content-Type-Options: nosniff > > same < X-XSS-Protection: 1; mode=block > > same < Cache-Control: no-cache, no-store, max-age=0, must-revalidate > > same < Pragma: no-cache > > same < Expires: 0 > > same < Strict-Transport-Security: max-age=31536000 ; includeSubDomains > > same < X-Frame-Options: DENY > > same < X-Application-Context: 0.3:8080 > > < Cache-Control: no-store > > < Pragma: no-cache > > same < Content-Type: application/json;charset=UTF-8 > > same < Connection: close > > same < Set-Cookie: crbid=10.1.8.5:49387_mt05.prod.gini.net; path=/ > > > > regards > > sabine > > > > 2015-02-27 16:58 GMT+01:00 Sven Van Caekenberghe-2 [via Smalltalk] > <[hidden email]>: > > Sabine, > > > > > On 27 Feb 2015, at 16:36, Sabine Manaa <[hidden email]> 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: application/json' -u 'aUser:aPassword' > > > 'https://user.xxx.net/oauth/token?grant_type=client_credentials' > > > > > > the result is something like: > > > > {"access_token":"a31xxxa-2a22-4xx6c-938d-2bd3ae4a0629","token_type":"bearer","expires_in":42095,"scope":"write"} > > > > > > > My current Pharo code is: > > > | theZnClient | > > > theZnClient := ZnClient new > > > systemPolicy ; > > > https; > > > host: 'user.xxx.net'; > > > path: 'oauth/token?grant_type=client_credentials'; > > > username: 'aUser' password: 'aPassword'; > > > accept: ZnMimeType applicationJson; > > > get. > > > theZnClient inspect close. > > > > > > 'aPassword' and 'aUser' and xxx.net was replaced by me for security > reasons. > > > > > > In Pharo, I get a walkback with the error message > > > 'SSL Exception: decrypt failed [code:-5]' > > > > > > But I see, that the ZdcSecureSocketStream has the correct result > > > ({"access_token":...":"write"}) in its collection attribute at > > > utf-8 string and at latin1-string > > > > > > so, the request is done and the result is available but then it fails > here: > > > ZdcSecureSocketStream(Object)>>error: > > > ZdcSecureSocketStream>>sslException:code: > > > ZdcSecureSocketStream>>fillBytes:startingAt:count: in Block: [ ... > > > ZdcSecureSocketStream>>fillBytes:startingAt:count: > > > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBufferNoWait > > > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer > > > > ZdcSecureSocketStream(ZdcOptimizedSocketStream)>>readInto:startingAt:count: > > > ZnUTF8Encoder>>optimizedReadInto:startingAt:count:fromStream: > > > ZnUTF8Encoder>>readInto:startingAt:count:fromStream: > > > > > > Sven, I could send you the 'aPassword' and 'aUser' and the url by > private > > > message. It would be fine if you could have a short look at it. > > The fact that there is readable text in the buffer of the > ZdcSecureSocketStream is good, because it means that things basically work. > > > > One reason why this is failing might be that Zn tries to read more than > there is available in the stream, when the content-length does not match. > Encoding problems could be part of the problem too. > > > > Could you compare curl -v or curl -D - output with the request/response > headers in Pharo ? Look for content-length and compare that with what it > already read or not. Is the connection kept alive ? Also look at > content-type and see if there is any charset encoding after > application/json. > > > > Sven > > > > > Regards > > > Sabine > > > > > > > > > > > > -- > > > View this message in context: > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > > > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > > > > > > > > > > > > > If you reply to this email, your message will be added to the discussion > below: > > > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > > To start a new topic under Pharo Smalltalk Users, email [hidden email] > > To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click > here. > > NAML > > > > > > View this message in context: Re: Zinc SSL Exception: decrypt failed > code:5 > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > <javascript:_e(%7B%7D,'cvml','ml-node%2Bs1294792n1310670h65(a)n4.nabble.com');> > To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 28, 2015

Re: [Pharo-users] Git (gitfiletree) on Pharo vs Windows

by Thierry Goubier

Le 28/02/2015 00:49, HernÃ¡n Morales Durand a Ã©crit : > Thierry, > > It seems to work fine so far. However I would like to commit and push > (propagate changes from my local git cloned repository to the remote > one) from Pharo. Is that possible right now from Monticello or an > (Smalltalk) expression? Would you us how? :) Do you mean this: making changes outside Pharo in the git, and doing a commit (and a push) ? I've integrated commit and push inside Monticello: commit is done automatically when you save, push can be done when opening the repository and pressing push... But I haven't done a GUI over Git. It could be done, but would not be that easy (and some of the existing Guis for Git, such as gitg, have serious performance issues). Thierry > I want to avoid to switch to SourceTree as in the following video (at 5:41) > > https://www.youtube.com/watch?feature=player_detailpage&v=n2WNYDtO0cE#t=344 > > HernÃ¡n > > > 2015-02-27 3:45 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>>: > > Hi HernÃ¡n, > > I didn't put ProcessWrapper as a dependency yet, you'll have to load > it first. > > Gofer new > url: > 'https://smalltalkhub.com/mc/__Pharo/MetaRepoForPharo30/main > <https://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main>'__; > configurationOf: 'ProcessWrapper'; > loadStable > > Thierry > > Le 27/02/2015 02:58, HernÃ¡n Morales Durand a Ã©crit : > > Hi Thierry, > > I have tried in Pharo 3: > > Gofer new > url: > 'https://smalltalkhub.com/mc/__Pharo/MetaRepoForPharo30/main > <https://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main>'__; > configurationOf: 'GitFileTree'; > loadDevelopment > > But it didn't load the ProcessWrapper. Can you tell me how > should I install? > > Cheers, > > HernÃ¡n > > > > > >

Feb. 28, 2015

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

by Johan Brichau

This sounds familiar to what we reported a while back: http://forum.world.st/Mac-sqDecryptSSL-returning-SQSSL-GENERIC-ERROR-on-err… <http://forum.world.st/Mac-sqDecryptSSL-returning-SQSSL-GENERIC-ERROR-on-err…> Unfortunately, we did not investigate any further. Instead, we work around the bug by just retrying the connection on this failure as it always works on a second try. Johan > On 27 Feb 2015, at 23:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 27 Feb 2015, at 21:18, Sabine Manaa <manaa.sabine(a)gmail.com> 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 encrypted binary data, the out buffer will contain the cleartext (but still in binary). > >> Can you tell me, what to add to the pharo code that the encoding is correct/so that is equal to the curl command? > > I don't think there is an encoding problem: the charset is set to utf-8 which will be picked up. Besides, the returned content is plain ascii anyway. > > The issue is probably the Connection:close and the missing Content-Length. This means that the HTTPS stream has to be read until the end. I have seen this fail in the past in rare cases. > > Are you on Windows ? > > Could you try on Linux ? > >> comparison of headers: they seem to be equal, also the content type is in both cases 'application/json;charset=UTF-8' >> The ZnResponse headers: >> a ZnHeaders( >> same 'Cache-Control'->#('no-cache, no-store, max-age=0, must-revalidate' 'no-store') >> same 'Connection'->'close' >> same 'Content-Type'->'application/json;charset=UTF-8' >> same 'Date'->'Fri, 27 Feb 2015 20:02:40 GMT' >> same 'Expires'->'0' >> same 'Pragma'->#('no-cache' 'no-cache') >> same 'Set-Cookie'->'crbid=10.1.8.3:49247_mt03.prod.gini.net; path=/' >> same 'Strict-Transport-Security'->'max-age=31536000 ; includeSubDomains' >> same 'X-Application-Context'->'0.3:8080' >> same 'X-Content-Type-Options'->'nosniff' >> same 'X-Frame-Options'->'DENY' >> same 'X-Xss-Protection'->'1; mode=block' ) >> >> result of curl command at command line >> < HTTP/1.1 200 OK >> same < Date: Fri, 27 Feb 2015 17:58:37 GMT >> same < X-Content-Type-Options: nosniff >> same < X-XSS-Protection: 1; mode=block >> same < Cache-Control: no-cache, no-store, max-age=0, must-revalidate >> same < Pragma: no-cache >> same < Expires: 0 >> same < Strict-Transport-Security: max-age=31536000 ; includeSubDomains >> same < X-Frame-Options: DENY >> same < X-Application-Context: 0.3:8080 >> < Cache-Control: no-store >> < Pragma: no-cache >> same < Content-Type: application/json;charset=UTF-8 >> same < Connection: close >> same < Set-Cookie: crbid=10.1.8.5:49387_mt05.prod.gini.net; path=/ >> >> regards >> sabine >> >> 2015-02-27 16:58 GMT+01:00 Sven Van Caekenberghe-2 [via Smalltalk] <[hidden email]>: >> Sabine, >> >>> On 27 Feb 2015, at 16:36, Sabine Manaa <[hidden email]> 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: application/json' -u 'aUser:aPassword' >>> 'https://user.xxx.net/oauth/token?grant_type=client_credentials' >>> >>> the result is something like: >>> {"access_token":"a31xxxa-2a22-4xx6c-938d-2bd3ae4a0629","token_type":"bearer","expires_in":42095,"scope":"write"} >>> >>> My current Pharo code is: >>> | theZnClient | >>> theZnClient := ZnClient new >>> systemPolicy ; >>> https; >>> host: 'user.xxx.net'; >>> path: 'oauth/token?grant_type=client_credentials'; >>> username: 'aUser' password: 'aPassword'; >>> accept: ZnMimeType applicationJson; >>> get. >>> theZnClient inspect close. >>> >>> 'aPassword' and 'aUser' and xxx.net was replaced by me for security reasons. >>> >>> In Pharo, I get a walkback with the error message >>> 'SSL Exception: decrypt failed [code:-5]' >>> >>> But I see, that the ZdcSecureSocketStream has the correct result >>> ({"access_token":...":"write"}) in its collection attribute at >>> utf-8 string and at latin1-string >>> >>> so, the request is done and the result is available but then it fails here: >>> ZdcSecureSocketStream(Object)>>error: >>> ZdcSecureSocketStream>>sslException:code: >>> ZdcSecureSocketStream>>fillBytes:startingAt:count: in Block: [ ... >>> ZdcSecureSocketStream>>fillBytes:startingAt:count: >>> ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBufferNoWait >>> ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer >>> ZdcSecureSocketStream(ZdcOptimizedSocketStream)>>readInto:startingAt:count: >>> ZnUTF8Encoder>>optimizedReadInto:startingAt:count:fromStream: >>> ZnUTF8Encoder>>readInto:startingAt:count:fromStream: >>> >>> Sven, I could send you the 'aPassword' and 'aUser' and the url by private >>> message. It would be fine if you could have a short look at it. >> The fact that there is readable text in the buffer of the ZdcSecureSocketStream is good, because it means that things basically work. >> >> One reason why this is failing might be that Zn tries to read more than there is available in the stream, when the content-length does not match. Encoding problems could be part of the problem too. >> >> Could you compare curl -v or curl -D - output with the request/response headers in Pharo ? Look for content-length and compare that with what it already read or not. Is the connection kept alive ? Also look at content-type and see if there is any charset encoding after application/json. >> >> Sven >> >>> Regards >>> Sabine >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >> >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >> To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click here. >> NAML >> >> >> View this message in context: Re: Zinc SSL Exception: decrypt failed code:5 >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 28, 2015

[ANN] Language Detection API Client

by HernÃ¡n Morales Durand

Hello, Language Detection API is a service to query the language of a given input text. You will need to register an API key in the web site http://detectlanguage.com to use the service. This client enables to use the service from Pharo Smalltalk. The output is an object containing the language code, a confidence score and a 'is reliable' boolean value. Installation and usage details in the following post: http://80738163270632.blogspot.com.ar/2015/02/languagedetection-api-client-… Cheers, HernÃ¡n

Feb. 28, 2015

Re: [Pharo-users] Postdoc position at INRIA Chile

by Alexandre Bergel

Here is the English translation: " Inria Chile was created in Chile in 2012 by Inria (www.inria.fr) in collaboration with nine Chilean universities. The Centre is supported by CORFO, Chilean Development Agency that was in charge of selecting Inria Chileâs project in the framework of the program Attraction of International Centers of Excellence for Competitiveness, aimed at developing and enhancing R&D capabilities for Chile. Inria Chile conducts its R&D activities through a development platform of applied actions, in the view of putting forward solutions for social and economic challenges in Chile, such as energy, including renewable energy, natural resources and âsmart citiesâ. The center is also working in applied topics such as sustainable development, natural disasters management or the development of advanced technologies for Astronomy. We are looking for a candidate interested in working in Chile, closely with a development team in order to carry out one of these actions. Skills are expected in particular (but not only) in the following areas: machine learning, massive data, sensors networks, interactive visualization. â Cheers, Alexandre > On Feb 27, 2015, at 5:21 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Dear All, > > I have just received a announcement for a position at INRIA Chile. > Here is an extract from the call. It is written in Spanish, however it is also open to non-spanish speaker. > > "Inria Chile fue creado en Chile en 2012 por Inria (www.inria.fr) y en colaboracioÌn con 9 universidades chilenas. Cuenta con el apoyo de CORFO, que seleccionoÌ el proyecto de Inria Chile en el marco del concurso AtraccioÌn de Centros de Excelencia Internacional para la Competitividad dedicado a desarrollar y reforzar las capacidades I+D del paiÌs. > > Inria Chile desarrolla sus actividades I+D a traveÌs de una plataforma de desarrollo de acciones aplicadas, que busca proponer soluciones a desafiÌos econoÌmicos y sociales para Chile, tal como energiÌa, en particular energiÌas renovables, recursos naturales y âciudades inteligentesâ. TambieÌn se estaÌ trabajando en temas aplicados como desarrollo sustentable, gestioÌn de cataÌstrofes naturales o el desarrollo de tecnologiÌas avanzadas para la astronomiÌa. > > Buscamos a un postdoc interesado en trabajar part-time en estrecho viÌnculo con un equipo de desarrollo que lleva a cabo una de estas acciones. Las competencias requeridas son particularmente en las aÌreas de: aprendizaje, datos masivos, redes de sensores, visualizacioÌn interactiva. Esta lista no es exhaustiva.â > > If you have a PhD and are interested, please contact me! > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 28, 2015

Re: [Pharo-users] Git (gitfiletree) on Pharo vs Windows

by HernÃ¡n Morales Durand

Thierry, It seems to work fine so far. However I would like to commit and push (propagate changes from my local git cloned repository to the remote one) from Pharo. Is that possible right now from Monticello or an (Smalltalk) expression? Would you us how? :) I want to avoid to switch to SourceTree as in the following video (at 5:41) https://www.youtube.com/watch?feature=player_detailpage&v=n2WNYDtO0cE#t=344 HernÃ¡n 2015-02-27 3:45 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi HernÃ¡n, > > I didn't put ProcessWrapper as a dependency yet, you'll have to load it > first. > > Gofer new > url: 'https://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main' > ; > configurationOf: 'ProcessWrapper'; > loadStable > > Thierry > > Le 27/02/2015 02:58, HernÃ¡n Morales Durand a Ã©crit : > > Hi Thierry, >> >> I have tried in Pharo 3: >> >> Gofer new >> url: 'https://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main' >> ; >> configurationOf: 'GitFileTree'; >> loadDevelopment >> >> But it didn't load the ProcessWrapper. Can you tell me how should I >> install? >> >> Cheers, >> >> HernÃ¡n >> >> >> >> > >

Feb. 27, 2015

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

by Sven Van Caekenberghe

> On 27 Feb 2015, at 21:18, Sabine Manaa <manaa.sabine(a)gmail.com> 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 encrypted binary data, the out buffer will contain the cleartext (but still in binary). > Can you tell me, what to add to the pharo code that the encoding is correct/so that is equal to the curl command? I don't think there is an encoding problem: the charset is set to utf-8 which will be picked up. Besides, the returned content is plain ascii anyway. The issue is probably the Connection:close and the missing Content-Length. This means that the HTTPS stream has to be read until the end. I have seen this fail in the past in rare cases. Are you on Windows ? Could you try on Linux ? > comparison of headers: they seem to be equal, also the content type is in both cases 'application/json;charset=UTF-8' > The ZnResponse headers: > a ZnHeaders( > same 'Cache-Control'->#('no-cache, no-store, max-age=0, must-revalidate' 'no-store') > same 'Connection'->'close' > same 'Content-Type'->'application/json;charset=UTF-8' > same 'Date'->'Fri, 27 Feb 2015 20:02:40 GMT' > same 'Expires'->'0' > same 'Pragma'->#('no-cache' 'no-cache') > same 'Set-Cookie'->'crbid=10.1.8.3:49247_mt03.prod.gini.net; path=/' > same 'Strict-Transport-Security'->'max-age=31536000 ; includeSubDomains' > same 'X-Application-Context'->'0.3:8080' > same 'X-Content-Type-Options'->'nosniff' > same 'X-Frame-Options'->'DENY' > same 'X-Xss-Protection'->'1; mode=block' ) > > result of curl command at command line > < HTTP/1.1 200 OK > same < Date: Fri, 27 Feb 2015 17:58:37 GMT > same < X-Content-Type-Options: nosniff > same < X-XSS-Protection: 1; mode=block > same < Cache-Control: no-cache, no-store, max-age=0, must-revalidate > same < Pragma: no-cache > same < Expires: 0 > same < Strict-Transport-Security: max-age=31536000 ; includeSubDomains > same < X-Frame-Options: DENY > same < X-Application-Context: 0.3:8080 > < Cache-Control: no-store > < Pragma: no-cache > same < Content-Type: application/json;charset=UTF-8 > same < Connection: close > same < Set-Cookie: crbid=10.1.8.5:49387_mt05.prod.gini.net; path=/ > > regards > sabine > > 2015-02-27 16:58 GMT+01:00 Sven Van Caekenberghe-2 [via Smalltalk] <[hidden email]>: > Sabine, > > > On 27 Feb 2015, at 16:36, Sabine Manaa <[hidden email]> 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: application/json' -u 'aUser:aPassword' > > 'https://user.xxx.net/oauth/token?grant_type=client_credentials' > > > > the result is something like: > > {"access_token":"a31xxxa-2a22-4xx6c-938d-2bd3ae4a0629","token_type":"bearer","expires_in":42095,"scope":"write"} > > > > My current Pharo code is: > > | theZnClient | > > theZnClient := ZnClient new > > systemPolicy ; > > https; > > host: 'user.xxx.net'; > > path: 'oauth/token?grant_type=client_credentials'; > > username: 'aUser' password: 'aPassword'; > > accept: ZnMimeType applicationJson; > > get. > > theZnClient inspect close. > > > > 'aPassword' and 'aUser' and xxx.net was replaced by me for security reasons. > > > > In Pharo, I get a walkback with the error message > > 'SSL Exception: decrypt failed [code:-5]' > > > > But I see, that the ZdcSecureSocketStream has the correct result > > ({"access_token":...":"write"}) in its collection attribute at > > utf-8 string and at latin1-string > > > > so, the request is done and the result is available but then it fails here: > > ZdcSecureSocketStream(Object)>>error: > > ZdcSecureSocketStream>>sslException:code: > > ZdcSecureSocketStream>>fillBytes:startingAt:count: in Block: [ ... > > ZdcSecureSocketStream>>fillBytes:startingAt:count: > > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBufferNoWait > > ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer > > ZdcSecureSocketStream(ZdcOptimizedSocketStream)>>readInto:startingAt:count: > > ZnUTF8Encoder>>optimizedReadInto:startingAt:count:fromStream: > > ZnUTF8Encoder>>readInto:startingAt:count:fromStream: > > > > Sven, I could send you the 'aPassword' and 'aUser' and the url by private > > message. It would be fine if you could have a short look at it. > The fact that there is readable text in the buffer of the ZdcSecureSocketStream is good, because it means that things basically work. > > One reason why this is failing might be that Zn tries to read more than there is available in the stream, when the content-length does not match. Encoding problems could be part of the problem too. > > Could you compare curl -v or curl -D - output with the request/response headers in Pharo ? Look for content-length and compare that with what it already read or not. Is the connection kept alive ? Also look at content-type and see if there is any charset encoding after application/json. > > Sven > > > Regards > > Sabine > > > > > > > > -- > > View this message in context: http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/Zinc-SSL-Exception-decrypt-failed-code-5-tp4808230p48… > To start a new topic under Pharo Smalltalk Users, email [hidden email] > To unsubscribe from Zinc SSL Exception: decrypt failed code:5, click here. > NAML > > > View this message in context: Re: Zinc SSL Exception: decrypt failed code:5 > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 27, 2015

Re: [Pharo-users] Postdoc position at INRIA Chile

by Sebastian Sastre

Maravilloso, no sabÃa que habÃa INRIA en Chile Congratulations and hats off to the ones that made that happen > On Feb 27, 2015, at 5:21 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Dear All, > > I have just received a announcement for a position at INRIA Chile. > Here is an extract from the call. It is written in Spanish, however it is also open to non-spanish speaker. > > "Inria Chile fue creado en Chile en 2012 por Inria (www.inria.fr) y en colaboracioÌn con 9 universidades chilenas. Cuenta con el apoyo de CORFO, que seleccionoÌ el proyecto de Inria Chile en el marco del concurso AtraccioÌn de Centros de Excelencia Internacional para la Competitividad dedicado a desarrollar y reforzar las capacidades I+D del paiÌs. > > Inria Chile desarrolla sus actividades I+D a traveÌs de una plataforma de desarrollo de acciones aplicadas, que busca proponer soluciones a desafiÌos econoÌmicos y sociales para Chile, tal como energiÌa, en particular energiÌas renovables, recursos naturales y âciudades inteligentesâ. TambieÌn se estaÌ trabajando en temas aplicados como desarrollo sustentable, gestioÌn de cataÌstrofes naturales o el desarrollo de tecnologiÌas avanzadas para la astronomiÌa. > > Buscamos a un postdoc interesado en trabajar part-time en estrecho viÌnculo con un equipo de desarrollo que lleva a cabo una de estas acciones. Las competencias requeridas son particularmente en las aÌreas de: aprendizaje, datos masivos, redes de sensores, visualizacioÌn interactiva. Esta lista no es exhaustiva.â > > If you have a PhD and are interested, please contact me! > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Feb. 27, 2015