X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/6894fbe1bde8ec1a4989417a2b68b4d84134ee20..5617c1e63207939cd1a3c5d44e84985be86f19dc:/doc/faq.but diff --git a/doc/faq.but b/doc/faq.but index 9df4508e..e0bfce6d 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -272,7 +272,7 @@ clearly be a useful thing, so in the long term I hope it can be brought up to release quality. There's also a third-party port at -\W{http://pocketputty.duxy.net/}\c{http://pocketputty.duxy.net/}. +\W{http://www.pocketputty.net/}\c{http://www.pocketputty.net/}. \S{faq-win31}{Question} Is there a port to \i{Windows 3.1}? @@ -1210,18 +1210,10 @@ feel perfectly free not to donate. We don't mind. \S{faq-permission}{Question} Can I have permission to put PuTTY on a cover disk / distribute it with other software / etc? -Yes. You need not bother asking us explicitly for permission. You -already have permission. Redistribution of the unmodified PuTTY -binary in this way is entirely permitted by our licence (see -\k{licence}), and you are welcome to do it as much as you like. +Yes. For most things, you need not bother asking us explicitly for +permission; our licence already grants you permission. -If you are distributing PuTTY within your own organisation, or for -use with your own product, then we recommend (but do not insist) -that you offer your own first-line technical support, to answer -questions directly relating to the interaction of PuTTY with your -particular environment. If your users mail us directly, we won't be -able to give them very much help about things specific to your own -setup. +See \k{feedback-permission} for more details. \S{faq-indemnity}{Question} Can you sign an agreement indemnifying us against security problems in PuTTY? @@ -1389,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