# Basic info

* Time: Wednesday 3 December 2025 at 14:00 CEST (12:00 UTC)
* Place: #openvpn-meeting channel on !LiberaChat IRC network

# Topics

- **Updated: Release 2.7**  
  Release 2.7rc3 was released on 28 November and addresses a local DoS in Windows interactive service.  
  This fix was also made available in a 2.6.17 release.  
  Note that for 2.5 branch we did put the fix in code but didn't build a new Windows installer, as that branch is out of support.  
  We're pretty close to 2.7 being ready for a stable release.  
  Currently however the signing key we use for Windows builds is expiring so we need to get a new one first.  
  Tentatively an rc4 will be coming on December 17. And followed by stable tentatively on January 14.  
  
- **Updated: Release 2.6.17**  
  The same local DoS in Windows interactive service was also fixed in 2.6 and was released with 2.6.17.  

- **community meetup 2026**  
  Where: Tentatively in Paderborn, Germany.  
  Meeting room: Potentially https://www.welcome-hotels.com/en/hotels/paderborn/events/  
  Beer: recommendation against local paderborner beer, although it is cheap.  

- **t_server and t_client testing framework**  
  mattock asked where to put the t_server stack as it is currently on ordex's open source fund funded AWS account but funds might dry up there.  
  Discussed option to move it to OpenVPN Inc. funded AWS community account. Will explore this option.  
  Needs to be picked up by either djpig or uddr.  

- **2.7 security audit**  
  ordex arranged mostly through STF funding to get a security audit of OpenVPN 2.7 (currently in release candidate phase).  
  Recently this has kicked off and 2.7 is being put through the meat grinder now by SRLabs.  
  We are processing these reports as well as reports from ZeroPath and addressing concerns raised.  

- **forums situation**  
  minx from OpenVPN Inc. originally set up flarum and started migration process, but he left the company before completion.  
  Now we have eduardo at OpenVPN Inc. who is taking a look and he managed to get migration working.  
  He suggests some further migration testing, and to then plan a hard cutover date.  
  Current time schedule somewhere in November or December.