the Windows version of Kermit) with security built in, in binary form?
permission from the US Department of Commerce Bureau of Industry and Security. This time-consuming and laborious process would be required for each C-Kermit binary, of which there are hundreds. Unfortunately we don’t have the resources to do that. In many cases, all you need to do is download the current source-code package, unpack it, and give a ‘make’ command referencing the appropriate target, e.g. “make freebsd50+openssl”, “make openbsd30+openssl”, “make hpux1100o+openssl”, “make linux+openssl”, etc. These targets are like the regular (non-secure) targets but with certain definitions added, certain directories added to the header-file search list, some extra libraries linked in. In case there is not a premade target in the makefile for the desired platform and security method(s), first check the latest development build (not released yet), maybe it has been added. If not, you will need to add one yourself, using similar targets as a model. For more information see the Kermit Securi
