Home A - Z
Page Index

An Otter Wiki

Blame

6f02e7 Samuli Seppänen 2025-01-29 06:40:08 1 
# Basic info
2
3
- **Time:** Wednesday 31 May 2023 at 13:00 CET (12:00 UTC)
4
- **Place:** #openvpn-meeting channel on LiberaChat IRC network
5
6
# Topics
7
8
## Current topics
9
10
- **2.6.5 release plans**
11
- *in about 2 to 6 weeks from now so anywhere between half June and half July*
12
13
- **Hackathon arrangements**
14
- *When: [Poll Link](https://nuudel.digitalcourage.de/t1hjepaHGhdpiV2P) => Probably October 6th-October 8th*
15
- *Location: Torrevieja. Lev looking into venue.*
16
- *Topics: Yes.*
17
18
- **2.7 plans, if any?**
19
- [Status of OpenVPN 2.7](https://community.openvpn.net/openvpn/wiki/StatusOfOpenvpn27)
20
21
- **Status of PoC using Gerrit for code review.**
22
- *Buildbot builds from Gerrit should work now for all workers. Please use!*
23
24
- **Security assessment of OpenVPN2 codebase.**
25
- *dazo has the final report and is reviewing. Will raise any remaining issues.*
26
27
- **License amendment for OpenVPN2 to solve openssl/mbedtls licensing issues**
28
- *Current status: [License Change](https://github.com/OpenVPN/openvpn-license-change)*
29
- *Issue with a particular contributor looks to be resolved.*
30
- *Now only 6 people remaining to approve.*
31
- *novaflash will assist plaisthos next week with trying to contact them.*
32
33
## Topics on standby
34
35
- **security@openvpn.net mailing list**
36
- *Company is trying to get to SOC2 compliance.*
37
- *Probably will need a simple NDA to be signed by recipients of emails to security@openvpn.net*
38
- *Company guy took standard NDA we use for contractors, suggests to use that.*
39
- *novaflash thinks we should review that first to see if it's really suitable or not, community members are not contractors after all.*
40
41
- **Website release process woes**
42
- *Website team claims their solution is 95% done. We'll see.*
43
44
- **Another key signing topic**
45
- *Company switched EV code signing to CloudHSM, this is the same cert type we use for driver signing, is also suitable for binary signing.*
46
- *In future, we could possibly switch community to that same key. Saves having to maintain 2 different keys.*
47
- *Depends on how hard/easy it is to access company key signing thing from community infrastructure.*
48
- *Also no high priority at the moment, we have a working solution now.*
49
50
- **Can we have someone at OpenVPN create nicer windows traybar logos?**
51
- *Matt is currently working on it in [GitHub Issue #595](https://github.com/OpenVPN/openvpn-gui/issues/595)*
52
53
- **SBOM topic**
54
- *cron2 was asked if OpenVPN has a software bill of materials. Answer was no.*
55
- *Coincidentally, in OpenVPN Inc a security requirement is to have an SBOM so this is on our list of things to do*
56
- *When we pick up this task we can coordinate on it.*
57
58
- **Forums machine on community infrastructure is only non-Linux system.**
59
- *Mattock made a new forums system that runs on Rocky Linux 8 as agreed with ecrist.*
60
- *Ecrist has looked at it but the current state of the migration is unknown.*
61
62
- **OpenVPN 2.6 performance results.**
63
- *We should work on an article to publish some performance results when 2.6 is out as stable. but first press release.*
64
65
- **Management interface documentation on main website will be updated with info from doc/management-notes.txt**
66
- *novaflash will pick this up at some point*
67
68
- **[OpenVPN Quickstart](https://openvpn.net/community-resources/openvpn-quickstart/) will be updated from /doc/man-sections/example-fingerprint.rst information.**
69
- *Static-key will be deprecated and contents updated with peer-fingerprint stuff.*
70
- *novaflash will pick this up again as time permits and other more important topics are done.*