Commit 87a7da

2025-05-14 11:55:59 novaflash: -/-
Meetings/2025/2025-05-14.md ..
@@ 7,38 7,38 @@
## Current topics
- * **Updated: community.openvpn.net wiki**
- On May 12 around 14:30 CET the community wiki will be switched to otterwiki.
-
- * **security mailing list**
- Contact page was updated (probably by accident) before it was approved.
- There are several items that community would like to see addressed before it gets updated.
-
- * **Release 2.7**
- Current estimates are to have all major code items in by May 1st and then a release on July 1st.
- Because DCO kernel upstreaming was completed, a backport of that code was made. It will become the new DCO module and is incompatible with the old one.
- OpenVPN master which will become 2.7 now has the userspace code to support the new DCO code, so when 2.7 goes out, so will the new DCO module.
- An application was submitted to OTF for a security audit of DCO-WIN.
- For the security audit on 2.7 we need to make some 2.7-alpha version.
- Regarding the arm64 openssl issue that we encountered, according to microsoft, this was a bug in MSVC build tools and the new (preview) version has it fixed.
-
- * **OpenVPN GUI improvements**
- With OpenVPN 2.7 it will be possible to support server with DCO, whereas before it had to tap/wintun.
- We already wanted to remove wintun, so we'll implement a logic to autodetect if we can remap wintun to DCO otherwise TAP.
- Additionally OpenVPN GUI will add ability to add new adapters as needed, if more than one connection is active at a time.
-
- * **new --dns option support**
- https://gerrit.openvpn.net/q/topic:%22dns+option%22
- Implementation for unix-like has needed approvals but needs to go in. Windows implementation is done and in.
- Currently work is being done on expanding the test framework to test the new DNS options - server-side of that is done, client side needs to comply.
-
- * **forums situation**
- Situation in a nutshell; old forums got flooded with spam. attempt was made to make new forums to fix it. this was aborted. now we're in limbo.
- We now have someone from OpenVPN Inc to help us fix it up, so we'll let him try.
-
- * **push_update / live route updates**
- Client-side support looks to be relatively straight-forward.
- Server-side support patch is up and requires review and is a bit more involved.
+ * **Updated: community.openvpn.net wiki**\
+ On May 12 around 14:30 CET the community wiki will be switched to otterwiki.\
+
+ * **security mailing list**\
+ Contact page was updated (probably by accident) before it was approved.\
+ There are several items that community would like to see addressed before it gets updated.\
+
+ * **Release 2.7**\
+ Current estimates are to have all major code items in by May 1st and then a release on July 1st.\
+ Because DCO kernel upstreaming was completed, a backport of that code was made. It will become the new DCO module and is incompatible with the old one.\
+ OpenVPN master which will become 2.7 now has the userspace code to support the new DCO code, so when 2.7 goes out, so will the new DCO module.\
+ An application was submitted to OTF for a security audit of DCO-WIN.\
+ For the security audit on 2.7 we need to make some 2.7-alpha version.\
+ Regarding the arm64 openssl issue that we encountered, according to microsoft, this was a bug in MSVC build tools and the new (preview) version has it fixed.\
+
+ * **OpenVPN GUI improvements**\
+ With OpenVPN 2.7 it will be possible to support server with DCO, whereas before it had to tap/wintun.\
+ We already wanted to remove wintun, so we'll implement a logic to autodetect if we can remap wintun to DCO otherwise TAP.\
+ Additionally OpenVPN GUI will add ability to add new adapters as needed, if more than one connection is active at a time.\
+
+ * **new --dns option support**\
+ https://gerrit.openvpn.net/q/topic:%22dns+option%22\
+ Implementation for unix-like has needed approvals but needs to go in. Windows implementation is done and in.\
+ Currently work is being done on expanding the test framework to test the new DNS options - server-side of that is done, client side needs to comply.\
+
+ * **forums situation**\
+ Situation in a nutshell; old forums got flooded with spam. attempt was made to make new forums to fix it. this was aborted. now we're in limbo.\
+ We now have someone from OpenVPN Inc to help us fix it up, so we'll let him try.\
+
+ * **push_update / live route updates**\
+ Client-side support looks to be relatively straight-forward.\
+ Server-side support patch is up and requires review and is a bit more involved.\
---
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9