[ntp:questions] Re: exporting NTP from the US
mayer at ntp.isc.org
Thu Mar 30 04:00:32 UTC 2006
> Thanks, Harlan.
> We are planning on using the NTP package that Meinberg has available
> for Windows. Many of our customers isolate their private networks from
> the Internet making it difficult for them to download the package so we
> are planning on making it available to them on our own release media.
I'm puzzled by this. If they isolate their networks how are they
expecting to use NTP?
> This in effect would make us an exporter, and consequently my
> The package as downloaded from Meinberg includes both the SSLeay32.dll
> and libeay32.dll libraries.
NTP only needs libeay32.dll so I think they made a mistake in including
> The following FAQ
> mentions some ITAR issues concerning SSL but does not really go into
> details. I am assuming that these two libraries, which are used by
> NTP, contain the encryption algorithms that are of concern. Since the
> API of these libraries is well documented on the Internet, anyone would
> be able to make use of the encryption algorithms once they have the
You can view the function calls by running depends.exe on the dll which
will tell you what functions can be called inside the DLL.
The OpenSSL project is developed outside of the US in order to get
around these laws and the source code is available everywhere so these
laws and regulations have no real practical effect except to reduce the
ability of American companies to compete in this market. That doesn't
help you of course, but that's the reality. You can of course get a
subsidiary outside the US obtain and ship the software, particularly as
Meinberg is a German company and not a US one, though I don't know if
the regulations also prevent that. As usual consult a lawyer.
What I can tell you is that BIND also uses OpenSSL and vendors ship that
everywhere. So if Unisys ships BIND then if can mostly like ship NTP as
well under the same conditions.
More information about the questions