Message-ID: <4EA5404F.8010207@...1435...> Date: Mon, 24 Oct 2011 12:39:11 +0200 From: Adriaan de Jong MIME-Version: 1.0 References: <1319445962-21686-1-git-send-email-dejong@...1435...> <1319445962-21686-3-git-send-email-dejong@...1435...> <4EA52800.4080205@...1147...> <1CED409804E2164C8104F9E623B08B90127CB75804@...1436...> <4EA534DB.5000201@...1114...> In-Reply-To: <4EA534DB.5000201@...1114...> Subject: Re: [Openvpn-devel] [PATCH 3/3] Changed default algorithm for PolarSSL to AES-128, as BF is not supported List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit To: David Sommerseth Cc: "openvpn-devel@lists.sourceforge.net" 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 with JJK, that this is probably not a clever idea - to change the > default encryption algorithm. > > What about to enforce the use of --cipher when OpenVPN is compiled with > PolarSSL support? Stating that blowfish isn't supported and another > cipher must explicit be set. I like this idea. I'll see about implementing it instead of patch 3/3. Perhaps in the long term we could try going for a protocol change as suggested by JJK. Adriaan