Hi Arne, thanks for the explanation on --tls-cipher NONE.
I know that TLS is only used for Authentication. But the other peer still would have to do a TLS handshake, which is undesired in my case as well. Assuming I want to remove the TLS handshake as well, would patching options.c enough or where else should I start looking? Many thanks, Valentin On Mon, Aug 31, 2015 at 1:26 PM, Arne Schwabe <a...@rfc2549.org> wrote: > > > Am 31.08.15 um 13:17 schrieb Valentin Sawadski: >> Hello Julian, >> >> thanks for your quick response. I know about --cipher none options in >> P2P mode, but for testing with multiple clients I need --mode server. >> >> As for the --tls-cipher option, NONE is not working for me. --show-tls >> also lists no other "non encrypted" cipher I could use. >> Besides it still seems to do the TLS handshake right? > Current TLS libraries (OpenSSl, PolarSSL) might not allow NONE as > ciphersuite in default setting, you may need to recompile OpenSSL for that. >> >> Is there any way I can have the unencrypted P2P communication with >> multiple connected clients (without having OpenVPN running in >> parallel)? >> > No. Current implementation requires TLS handshake for that. And only the > handshake is encrypted, not the communication itself. > > Arne -- Valentin Sawadski Founder & Embedded Software Tel.: +49 - (0) 89 - 716 77 86 - 15 Fax: +49 - (0) 89 - 716 77 86 - 99 Mobil: +49 - (0) 162 - 460 163 4 facebook.com/tado | twitter.com/tado | youtube.com/tado www.tado.com | tado° GmbH | Lindwurmstr. 76 | 80337 Munich | Germany Managing Directors: Christian Deilmann | Johannes Schwarz | Leopold v. Bismarck Registered with the Commercial Register Munich as HRB 194769 B | VAT-No: DE 280012558
