Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Glen Starrett wrote: > Yes, it is our problem (a US problem). The rules are that if we get some > software then want to send it back out of the country (or even to a > forigen national within the country), then we need to make sure it > complies with our > export laws. This is regardless of where we get it from. If this were a > commercial piece of software, then Tony as the head honcho of Soft Corp of > UK would likely do anything to make sure there weren't any barriers for > multinational corps to use it, but this isn't the case. Of course if I were head of a corp, producing commercial software, redistribution wouldn't be an issue :) It does seem crazy to me. In theory even the Unix crypt() function (that's actually compiled in the main cvs .exe IIRC) is >40bit and therefore needs licensing, so you can't even get away with deleting all the kerberos and ssh stuff and crippling openssl down to 40bits... it's not enough. That's why for years the Linux encrypted filesystems & IPSEC stuff was maintained separately in Europe - I think they've given up trying to comply now, and it's been rolled into 2.5. > I don't mind offering some help to others who need it where I can... and > since I've been through this, I can at least offer some guidance, which I > am (hopefully) doing already. Thanks. I'll keep out of it now since I've said about as much as I can, and leave you to it. Tony