Difference between revisions of "OpenVPN/IRC meetings/Topics-2010-04-01"

From Secure Computing Wiki
Jump to: navigation, search
(Created page with '# '''Community comments''' ## Implement a solution for deprecating warnings like: ##* "WARNING: Make sure you understand the semantics of --tls-remote before using it (see the ma...')
 
Line 5: Line 5:
 
##* Suggestion: Introduce a new configure option to allow filtering of different start-up warnings.
 
##* Suggestion: Introduce a new configure option to allow filtering of different start-up warnings.
 
##** Do not remove all messages by one entry, but add a possibility to filter each message separately. This way newer warnings will be shown and needs to be disabled explicitly.<br /><br />
 
##** Do not remove all messages by one entry, but add a possibility to filter each message separately. This way newer warnings will be shown and needs to be disabled explicitly.<br /><br />
 +
 +
# '''New patches/issues'''
 +
## [http://search.gmane.org/?query=VLAN+tagging&author=fabian.knittel%40avona.com&group=gmane.network.openvpn.devel&sort=relevance&DEFAULTOP=and&xP=vlan%09Ztag&xFILTERS=Gnetwork.openvpn.devel---A Fabian Knittel's VLAN tagging patchset]
  
 
# '''Old patches/issues'''
 
# '''Old patches/issues'''

Revision as of 09:23, 1 April 2010

  1. Community comments
    1. Implement a solution for deprecating warnings like:
      • "WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page)."
      • "NOTE: the current --script-security setting may allow this configuration to call user-defined scripts"
      • Suggestion: Introduce a new configure option to allow filtering of different start-up warnings.
        • Do not remove all messages by one entry, but add a possibility to filter each message separately. This way newer warnings will be shown and needs to be disabled explicitly.

  1. New patches/issues
    1. Fabian Knittel's VLAN tagging patchset
  1. Old patches/issues
    1. 802.1Q --passtos patch
      • No test reports from users yet
  1. Possible bugs/issues
    1. Assertion fails in socket.c:429 in p2p mode due to Debian ipv6 patch
  1. sf.net trackers
    1. bug? wrong CN in client-disconnect with username-as-common-name