Kris, I merged your changes in (except for the default being false instead of true for logging) - Thanks! === Name: Zodiac-Core-SvenVanCaekenberghe.35 Author: SvenVanCaekenberghe Time: 24 October 2014, 1:56:40.080389 pm UUID: d27bbfa1-187d-4ab9-b7e8-5a77a34aeb6a Ancestors: Zodiac-Core-KrisGybels.32 Merging in Kris' code to enable logging of the native code inside the plugin (Thx Kris Gybels) Disabled the experimental changes in 32 Jumping over some versions that exist out there === Sven
On 24 Oct 2014, at 12:55, Kris Gybels <kris@yesplan.be> wrote:
Op 22-okt.-2014, om 13:39 heeft Sven Van Caekenberghe <sven@stfx.eu> het volgende geschreven:
I do not know how to enable the logging inside the plugin, Chris Gybels just told me that he got that working, maybe he can answer. Kris ?
Here's a version of Zodiac-Core with ZdcPluginSSLSession changed to enable the logging done by the SSL plugin, if that helps.
On a Mac, to see the output of the plugin, you need to run the VM from the Terminal. If you execute [ ZnClient new url: 'https://www.google.com'; get ] in a workspace, you should see some output like this in the Terminal:
$ /Applications/Pharo.app/Contents/MacOS/Pharo Pharo.image sqConnectSSL: 2d9a30 sqConnectSSL: input token 0 bytes sqConnectSSL: Setting up SSL sqSetupSSL: Setting up new context SqueakSSLWrite: Writing 158 bytes, having 17408 free SqueakSSLRead: Requesting 1 bytes, having 0 bytes sqConnectSSL: Produced 158 token bytes sqConnectSSL: 2d9a30 [...]
The output on Linux / Windows will be somewhat different I assume, I haven't tried it. To understand what is being logged, you'll need to look at the C code of the plugin:
https://code.google.com/p/squeakssl/source/browse/src/#src
<Zodiac-Core-KrisGybels.32.mcz>