On Sat, 20 Mar 2010, Bram Moolenaar wrote: > > Ben Fritz wrote: > > > On Mar 17, 10:24 am, Bram Moolenaar wrote: > > > > > > I would very much like feedback on this patch. Any platform where > > > this causes problems, such as compiler warnings? > > > > Is this going to introduce any export law worries if included? > > No, I'm not in the US. I don't think the US has import laws about this.
No, I don't think it does. Unfortunately the U.S. isn't the only country to which these idiotic restrictions apply. (Idiotic in both principle [attempting to control software export in the internet age] and practice [cf. 'fax us a copy of your source code' in my previous response]) The international version is "The Wassenaar Arrangement": http://www.wassenaar.org/ (which, incidentally, *does* appear to have key-length restrictions:) http://www.wassenaar.org/controllists/index.html - category 5 - part 2 Also, you say you're not in the U.S., but Vim's hosted mostly on Sourceforge (which is a U.S.-based entity), correct? > There are some countries where _use_ of cryptography is restricted, > but that's not our problem. > > These algorithms are generally available, thus adding them to Vim > won't change anything. I agree on both counts. And the latter is why I think adding the code won't cause any trouble: it would be a bizarre world indeed if Vim were the first project with legal action pursued against it. (based on jurisdiction weirdness, and 'notability' in the "It's widely available in larger software libraries" sense) Then again, some of the ones pursued by the U.S. government are pretty weird: http://efoia.bis.doc.gov/exportcontrolviolations/tocexportviolations.htm (Of note is the fact that they're universally 'hardware' of various types. But, come on... tape drives? [E2084]) > I don't like depending on a library, because it means there will be > platforms where the library is unavailable and there you can't edit > your encrypted file, which can be very annoying. Personally, I find it slightly odd that it'd be built in to Vim. Seems like it'd be easier/preferable to add plugins to facilitate the use of external tools. But I only find it odd, not objectionable. In any case, I feel like its inclusion is unlikely to cause trouble. It's just an interesting discussion (...and probably not of general interest). I think development effort is better focused elsewhere, so I'll not pursue it further. -- Best, Ben -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php To unsubscribe from this group, send email to vim_dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
