nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-10 01:48:00 +00:00
Code Issues Projects Releases Wiki Activity

ECCN / FIPS - we can't be arsed.

Browse Source 
[originally from svn r6619]
This commit is contained in:
Owen Dunn 2006-03-31 09:26:59 +00:00
parent 806c2b73ce
commit de3e873b12
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/faq.but
View File

@ -1381,6 +1381,22 @@ closed-source and someone made an open-source fork, most people
would switch to the latter. Therefore, it would be pretty stupid of
us to try it.)
\S{faq-export-cert}{Question} Can you provide us with export control
information / FIPS certification for PuTTY?
Some people have asked us for an Export Control Classification Number
(ECCN) for PuTTY. We don't know whether we have one, and as a team of
free software developers based in the UK we don't have the time,
money, or effort to deal with US bureaucracy to investigate any
further. We believe that PuTTY falls under 5D002 on the US Commerce
Control List, but that shouldn't be taken as definitive. If you need
to know more you should seek professional legal advice. The same
applies to any other country's legal requirements and restrictions.
Similarly, some people have asked us for FIPS certification of the
PuTTY tools. Unless someone else is prepared to do the necessary work
and pay any costs, we can't provide this.
\H{faq-misc} Miscellaneous questions
\S{faq-openssh}{Question} Is PuTTY a port of \i{OpenSSH}, or based on