Thanks for your reply. I added some codes to the CreateSelfSignedCert function and saved the "FCertificate" and "FPrivatekey" to file "bs-cert.cert" and "bs-privatekey.pvk" when the function is invoked. Then, in the server side I added two lines of code before SSLAcceptConnection:
fclient.SSL.CertificateFile := 'd:\temp\bs-cert.cert'; fclient.SSL.PrivateKeyFile := 'd:\temp\bs-privatekey.pvk'; The client side remains no change. Did I do things right? Looks like it works but I'm not sure. In your HTTPS demo, there are four lines of code: sock.SSL.CertificateFile:='cert.pem'; sck.ssl.PrivateKeyFile:='key.pem'; sock.ssl.CertCAFile:='cacert.pem'; sock.SSL.KeyPassword:='your_pem_secret_password'; I think I don't need "CertCAFile" and "KeyPassword" to make self-signed certificate work? Thank you. Lewis Lukas Gebauer wrote: >> CreateSelfSignedCert create self-signed certificate and store them >> into PrivateKey property. (binary string) This is called when ad-hoc >> certificate is needed. >> > > ...and Certificate property too, of course! > > > ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
