Are you sharing technology, shipping, transmitting or transferring University of Tennessee-developed, non-commercial encryption software* in source code or object code.**
*The sharing, shipping, transmission or transfer of almost all encryption software in either source code or object code is subject to US export regulations.
International Traffic in Arms (ITAR)
The sharing, shipping, transmission or transfer of all encryption software in either source code or object code that is specifically designed or developed for a military, intelligence or space application is subject to the International Traffic in Arms Regulations (ITAR). ITAR-related encryption software is controlled for export and cannot be shared with a foreign person unless the code is already published or otherwise in the public domain.
Export Administration Regulations (EAR)
The sharing, shipping, transmission or transfer of almost all dual-use encryption software in either source code or object code is subject to the Export Administration Regulations. Even most of today’s publicly available dual-use encryption software, which uses “strong” encryption, is captured by the EAR and requires the availability of a License Exception to exit the US.
** Source code is generally understood to mean programming statements that are created by a programmer with a text editor or a visual programming tool and then saved in a file. Object code generally refers to the output, a compiled file, which is produced when the Source Code is compiled with a C compiler. The object code file contains a sequence of machine-readable instructions that is processed by the CPU in a computer. Operating system or application software is usually in the form of compiled object code.
Back to Export Controls Decision Tree starting point.
Design and content used by permission of Stanford Univeristy (updated 2008).