Ben Fritz wrote
Boost.Asio contains some SSL interfaces, which undoubtedly contains encryption technology. However, according to http://www.boost.org/doc/libs/1_57_0/doc/html/boost_asio/overview/ssl.html these interfaces require OpenSSL to be used. Does this mean that the Boost.Asio library itself does not contain encryption, it only provides an interface to another library which does the encryption? I.e., is it a true statement, that Boost.Asio contains no encryption technology in either its source code or in the compiled binary, and that in order to use encryption I would need to link in a separate library?
I wonder about this. The author of the ASIO is Christopher M. Kohlhoff who is Australian. I presume it was written there. So shipping ASIO would not "exporting" it and thus not subject to such laws. Am I missing something here. It gets even more interesting. ASIO has been proposed as an edition to the standard library. Would conforming C++ implementation then require an export license. Or what. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/Questions-to-help-me-determine-export-cla... Sent from the Boost - Dev mailing list archive at Nabble.com.