On Fri, Mar 19, 2010 at 12:50:36AM -0400, Benjamin R. Haskell wrote: > > On Thu, Mar 18, 2010 at 7:22 AM, Ben Fritz <[email protected]> wrote: > > > Is this going to introduce any export law worries if included? > > My general thought would be that it would be much easier to include the > patch if it could be reworked to use some commonly-available, external > crypto library (thus Vim doesn't contain crypto software, so isn't > exporting crypto). (e.g. use OpenSSL or ...well, OpenSSL.)
There's also libgcrypt, which doesn't have OpenSSL's problem of being GPL incompatible. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]> -- 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.
