-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/10/11 12:39, Adriaan de Jong wrote:
> On 10/24/2011 11:50 AM, David Sommerseth wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 24/10/11 10:58, Adriaan de Jong wrote:
>>> Unfortunately BF isn't supported in PolarSSL though.
>>>
On 10/24/2011 11:50 AM, David Sommerseth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/10/11 10:58, Adriaan de Jong wrote:
Unfortunately BF isn't supported in PolarSSL though.
Do you have any other suggestions? I'm open to most ideas other than
"implement blowfish" :)
I agree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/10/11 10:58, Adriaan de Jong wrote:
> Unfortunately BF isn't supported in PolarSSL though.
>
> Do you have any other suggestions? I'm open to most ideas other than
> "implement blowfish" :)
I agree with JJK, that this is probably not a clever
On 10/24/2011 11:03 AM, Jan Just Keijser wrote:
Adriaan de Jong wrote:
Unfortunately BF isn't supported in PolarSSL though.
Do you have any other suggestions? I'm open to most ideas other than "implement
blowfish" :)
hmmm then perhaps the default should be changed to AES-128 ?
That's an
Unfortunately BF isn't supported in PolarSSL though.
Do you have any other suggestions? I'm open to most ideas other than "implement
blowfish" :)
Adriaan
> -Original Message-
> From: Jan Just Keijser [mailto:janj...@nikhef.nl]
> Sent: maandag 24 oktober 2011 10:55
> To: Adriaan de
I'd NACK this patch : the default behaviour of OpenVPN should be
independent of the SSL implementation.
JJK
Adriaan de Jong wrote:
> Signed-off-by: Adriaan de Jong
> ---
> options.c |5 +
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/options.c
Signed-off-by: Adriaan de Jong
---
options.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/options.c b/options.c
index 39e7a57..d917072 100644
--- a/options.c
+++ b/options.c
@@ -810,7 +810,12 @@ init_options (struct options *o, const bool