| Version 10 (modified by , 14 years ago) (diff) |
|---|
Possible bugs/issues
- Update on a few issues discussed first in this email thread and later in this meeting.
- (Windows) All error codes when using the InternetQueryOption? API are lost. See also http://support.microsoft.com/kb/226473. Openvpn 2.1 uses the "old" IE4 API.
- Enabling auto-proxy to work in configs that contain both UDP and TCP-based "<connection>" profiles?
- In a similar vein, the following ticket is in the bug tracking system. There seems to be a general problem with mixing TCP and UDP options (eg. mssfix, nobind, fragment) SourceForge.net tracker item
- Using --inactive and --ping seems to defeat each other http://thread.gmane.org/gmane.network.openvpn.devel/3556
Patch Queue
New / awaiting ACK
- Avoid repetition of "this config may cache passwords in memory" (v2)
- Revamped the script-security warning logging (version 2)
- (PULL-REQUEST v3) VLAN-Tagging
- This patch set is available via the 'feat_vlan_tagging' branch in openvpn-testing.git for review. It is not merged into allmerged at the moment. It needs an ACK to take that step. The branch will be rebuilt based on a better branch from Fabian Knittel in the near future - and before a merge into allmerged.
In progress - awaiting dazo
- "Unpackaged Windows binaries"
In progress / awaiting further feedback
- MacOSX Keychain Certificate support
- MacOSX making .dmg/.pkg
- Solaris tun/tap support
- Gert is supervising this patch and will merge this patch into his IPv6 payload tree, as he does several improvements to tun.c there.
Awaiting testing before ACK
Other
- Community site Trac configuration
- Plugins, editable/protected pages etc.
- Roadmap
- Who will be responsible for creating and following the roadmap?
- How do we integrate organic development ("random" patches to ml) and planned development (roadmap)
- Bad TCP-over-TCP performance. What could be done to make it less bad? See this thread and Stephen Carville's response.
- Coding style guidelines
- Several begins to touch this issue. Which coding style guidelines do we have? How do we enforce it? For patches the most critical one is to decide whether to use tabs or spaces.
