Nicolas Weber wrote:
> > To clarify, based on my understanding: if software is exported
> > from the
> > U.S., which vim arguably is, and it is capable of powerful encryption
>
> isn't vim exported from the Netherlands?
Right, the main ftp server is in the Netherlands. All the rest are
(cac
Ken Hirsch wrote:
[...]
To clarify, based on my understanding: if software is exported from the
U.S., which vim arguably is, and it is capable of powerful encryption
(64-bit symmetric keys, other limits for public-key/elliptic
algorithms), then it _is_ subject to export restrictions. As the lin
Hi,
To clarify, based on my understanding: if software is exported
from the
U.S., which vim arguably is, and it is capable of powerful encryption
isn't vim exported from the Netherlands?
Nico
On Sun, Mar 18, 2007 at 08:55:33PM +0100, Bram Moolenaar wrote:
> Main issue is that the current encryption is breakable. We need a
> stronger encryption, which is free to distribute. We only need one new
> method.
If a strong encryption algorithm is used, the keys may still be the weak
spot. A
Matthew Winn wrote:
On Mon, 19 Mar 2007 09:22:08 -0600, Josh <[EMAIL PROTECTED]> wrote:
There are no patent issues, but there is export issues, I live in the US
The reason I suggested Rijndael is because there are no US export
issues. Not only was it developed in Flanders so implementat
On Mon, 19 Mar 2007 09:22:08 -0600, Josh <[EMAIL PROTECTED]> wrote:
> There are no patent issues, but there is export issues, I live in the US
The reason I suggested Rijndael is because there are no US export
issues. Not only was it developed in Flanders so implementations
outside the US abound,
Josh wrote:
> The main problem that I see is that adding a strong encryption
> function can have regulation issues. That was the only reason that I
> thought about using the external library is to get around this.
>
> How secure does the encryption need to be?
As far as I know Blowfish is pract
There are no patent issues, but there is export issues, I live in the US
--
Josh
On Sun, 18 Mar 2007 15:57:33 -0600, Josh <[EMAIL PROTECTED]> wrote:
> The main problem that I see is that adding a strong encryption
> function can have regulation issues. That was the only reason that I
> thought about using the external library is to get around this.
With an algorithm like Rijn
The main problem that I see is that adding a strong encryption
function can have regulation issues. That was the only reason that I
thought about using the external library is to get around this.
How secure does the encryption need to be?
--
Josh
Josh wrote:
> Another idea that I saw on the list was improving the encryption in
> vim and encrypting the swap file. The ideas that I have for this range
> from replacing the encryption function in vim with one that is more
> secure to adding support for an external library library to adding
> f
Another idea that I saw on the list was improving the encryption in
vim and encrypting the swap file. The ideas that I have for this range
from replacing the encryption function in vim with one that is more
secure to adding support for an external library library to adding
functions to modify the
12 matches
Mail list logo