<br>I sort of didn't understand Yanni's difficulty. I worked through the SSL tutorial at <a href="http://squeakingalong.wordpress.com">http://squeakingalong.wordpress.com</a> and I started to see it. I have a solution, I think, as usual, it's sort of a hack.<br>
<br>It's predicated on the idea that modules don't load into the image until they're needed. My solution is sort of to just shake the image. If you put the bundle in the right place (ensuring that you don't house it in SqueakSSL-bin file folder it came in) then it looks like this: <br>
<br><a href="http://smalltalktelevision.com/ssl1.jpg">http://smalltalktelevision.com/ssl1.jpg</a><br><br>Then you try Smalltalk listLoadedModules and it doesn't appear. It needs to be primed at this point so try one of these or both: <br>
<br> (WebClient httpGet: '<a href="https://encrypted.google.com/">https://encrypted.google.com/</a>') content.<br> <br> SqueakSSL google: 'squeak'<br><br>It complains. Save and quit. Restart. Then try Smalltalk listLoadedModules again, and SqueakSSL plugin will appear in the list. If still not there, prime again with the above in Workspace. Sufficiently shook, I proceed through the blog tutorial and set this to accept: <br>
<br><a href="http://smalltalktelevision.com/ssl2.jpg">http://smalltalktelevision.com/ssl2.jpg</a><br><br>It doesn't like that: <br><br><a href="http://smalltalktelevision.com/ssl3.jpg">http://smalltalktelevision.com/ssl3.jpg</a><br>
<br>But I'm not disappointed. My knowledge of whether I'm supposed to feed it the newkey.pem, newreq.pem or the demoCA/cacert.pem is not something I have. Perhaps somebody could tell me which is supposed to be the "the .pem file which must include both the certificate and the private key". With the correct file offered up to the image, I think it's on its way.<br>
<br>Chris <br>