"dk_sz" <dk_sz@hotmail.com> wrote in message
news:45be1847$1@newsgroups.borland.com...
> Yeah OK. Problem just is it puts the responsiblity on
> me with regards to encryption technology.
So what? OpenSSL is publically available. Have your installer (or
the user) download it when needed. If you want to ship it with your
application, just be sure to host the files on a non-US server (I'm no
lawyer, but that should protect you from US export laws on
encryption).
> I have not studied the architecture of Indy to have any
> formed meaning about this. But if it had been possible to
> "plug-in" (e.g. uses clause or whatever) a Windows only
> SSL solution, that could probably still make many happy :-)
It already can be. Any class derived from TIdSSLIOHandlerSocketBase
can be used. TIdSSLIOHandlerSocketOpenSSL happens to be Indy's own
derived class. There are other third-party classes available, such as
StreamSec (http://www.streamsec.com). So there is nothing stopping
you from writing your own, as long as it fits the interface.
