meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:openvpn:issues [2023/01/30 10:15] – niziaklinux:openvpn:issues [2023/10/11 14:20] (current) – niziak
Line 1: Line 1:
 ====== Issues ====== ====== Issues ======
 +
 +===== digest algorithm too weak =====
 +
 +<code>error=CA signature digest algorithm too weak:</code>
 +
 +Solution: upgrade server CA to use at least SHA256
 +
 +Workaround: 
 +
 +<file conf client.conf>
 +# to work around the cert too weak issue 
 +tls-cipher "DEFAULT:@SECLEVEL=0"
 +</file>
 +
 +And from [[https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_security_level.html|man 3 SSL_CTX_set_security_level]]:
 +
 +<code>
 +Level 0
 +
 +    Everything is permitted. This retains compatibility with previous versions of OpenSSL.
 +
 +Level 1
 +
 +    The security level corresponds to a minimum of 80 bits of security. Any parameters offering below 80 bits of security are excluded. As a result RSA, DSA and DH keys shorter than 1024 bits and ECC keys shorter than 160 bits are prohibited. All export cipher suites are prohibited since they all offer less than 80 bits of security. SSL version 2 is prohibited. Any cipher suite using MD5 for the MAC is also prohibited.
 +</code>
 +
  
 ===== /sbin/resolvconf: 31: kill: Operation not permitted ===== ===== /sbin/resolvconf: 31: kill: Operation not permitted =====
Line 6: Line 32:
 /sbin/resolvconf: 31: kill: Operation not permitted /sbin/resolvconf: 31: kill: Operation not permitted
 </code> </code>
 +
 +Reason:
 +[[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998388|openresolv: resolvconf fails if called from openvpn during system start with "kill: Operation not permitted"]]
 +
 +Problematic script: ''/lib/resolvconf/libc.d/avahi-daemon''
 +
 +
  
 ===== IP packet with unknown IP version=15 seen ===== ===== IP packet with unknown IP version=15 seen =====
Line 13: Line 46:
 Solution: Solution:
  
- explicitly disable ''comp-lzo no'' on client or allow compression on server.+ explicitly disable ''comp-lzo no'' on server.