OpenVPN Client with "cipher none" segmentation fault.

[illfated]

When I try to connect to a openvpn server with "cipher none" the ON button switches back to OFF when I try to enable it.
The log just says:

Jan  1 22:09:10 openvpn[1022]: OpenVPN 2.3.6 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Dec 27 2014
Jan  1 22:09:10 openvpn[1022]: library versions: OpenSSL 1.0.0o 15 Oct 2014, LZO 2.08
Jan  1 22:09:10 openvpn[1022]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan  1 22:09:10 openvpn[1022]: ******* WARNING *******: null cipher specified, no encryption will be used
Jan  1 22:09:10 openvpn[1022]: Control Channel Authentication: using 'static.key' as a OpenVPN static key file
Jan  1 22:09:10 openvpn[1022]: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Jan  1 22:09:10 openvpn[1022]: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

When I run it manually from bash there is a "Segmentation fault" at the end:

Thu Jan  1 22:35:25 2015 OpenVPN 2.3.6 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Dec 27 2014
Thu Jan  1 22:35:25 2015 library versions: OpenSSL 1.0.0o 15 Oct 2014, LZO 2.08
Thu Jan  1 22:35:25 2015 ******* WARNING *******: null cipher specified, no encryption will be used
Thu Jan  1 22:35:25 2015 Control Channel Authentication: tls-auth using INLINE static key file
Thu Jan  1 22:35:25 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jan  1 22:35:25 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Segmentation fault

I tried the same openvpn file on a windows and debian client, it works there without any issues.

 

[RMerlin]

Don't set it to None. Basically I have no idea why the original author added it as an option, and is something I intend to remove at some point since that setting simply doesn't make any sense.

 

[rb64]

When I try to connect to a openvpn server with "cipher none" the ON button switches back to OFF when I try to enable it.
The log just says:

When I run it manually from bash there is a "Segmentation fault" at the end:

I tried the same openvpn file on a windows and debian client, it works there without any issues.

According to the openvpn source code, there were a couple of fixes to
the "cipher none" bug. And the second fix didn't make it into version 2.3.6.
Here is the github commit:

https://github.com/OpenVPN/openvpn/commit/98156e90e1e83133a6a6a020db8e7333ada6156b

Although "cipher none" may at first seem like a useless option,
it is used for at least a couple of situations, like
when one needs to test if the vpn speed can some close to the
max bandwidth of one's internet provider;
also there are some cases when the ISP throttles under
certain conditions - and using vpn with no encryption is a
quick & dirty solution (with no performance penalty).

 

[illfated]

Don't set it to None. Basically I have no idea why the original author added it as an option, and is something I intend to remove at some point since that setting simply doesn't make any sense.

I wanted to test the max speed of the vpn on the router without encryption. In another thread you mentioned that the router cant handle more than 10-15mbit with the openvpn encryption (RT-N66U) I've got a 100mbit Internet connection so using the vpn with only 15mbit is not really worth it :\

According to the openvpn source code, there were a couple of fixes to
the "cipher none" bug. And the second fix didn't make it into version 2.3.6.
Here is the github commit:

https://github.com/OpenVPN/openvpn/commit/98156e90e1e83133a6a6a020db8e7333ada6156b

Although "cipher none" may at first seem like a useless option,
it is used for at least a couple of situations, like
when one needs to test if the vpn speed can some close to the
max bandwidth of one's internet provider;
also there are some cases when the ISP throttles under
certain conditions - and using vpn with no encryption is a
quick & dirty solution (with no performance penalty).

exactly