Blame
| 6f02e7 | Samuli Seppänen | 2025-01-29 06:40:08 | 1 | # Basic Info |
| 2 | ||||
| 3 | - Time: Wednesday 8 November 2023 at 13:00 CEST (11:00 UTC) |
|||
| 4 | - Place: #openvpn-meeting channel on LiberaChat IRC network |
|||
| 5 | ||||
| 6 | # Topics |
|||
| 7 | ||||
| 8 | ## Current Topics |
|||
| 9 | ||||
| 10 | ### Updated: OpenVPN 2.6.7 Release |
|||
| 11 | - There is a div-by-zero bug and a critical bug we were waiting to get fixed before proceeding. |
|||
| 12 | - The patch for fixing both is on the security mailing list and has acks so will go in now. |
|||
| 13 | - The release is expected to happen today. |
|||
| 14 | ||||
| 15 | ### Updated: Publish Security Assessment of OpenVPN2 Codebase on Main Website |
|||
| 16 | - Expected to be published either this or next week. |
|||
| 17 | ||||
| 18 | ### Tunnelcrack Published Now |
|||
| 19 | - A post was published at [TunnelCrack community wiki article](https://tunnelcrack.mathyvanhoef.com) |
|||
| 20 | - More details are in the [Hackathon2023 meeting summary](https://wiki:TunnelCrack). |
|||
| 21 | - A security advisory went up on the main website [OpenVPN Security Advisories](https://openvpn.net/security-advisories/) |
|||
| 22 | - Current status: when mitigations start appearing we will mention them in meeting notes. |
|||
| 23 | ||||
| 24 | ### License Amendment for OpenVPN2 to Solve OpenSSL/MBedTLS Licensing Issues |
|||
| 25 | - The OpenSSL James Bottomley stuff is resolved now. |
|||
| 26 | - The `--tls-export-cert` feature needs to be removed by dazo and reimplemented by plaisthos. |
|||
| 27 | - Then it is up to dazo to review things so we can work on finalizing this. |
|||
| 28 | - One of the tasks is reviewing if remaining items are trivial patches, and maybe get legal advice on those if necessary. |
|||
| 29 | - For new contributions, the new license already applies so maxf is unblocked to implement mbedtls3 support on master. |
|||
| 30 | - maxf mentioned he will look into how much work it is to backport mbedtls3 to 2.6. |
|||
| 31 | ||||
| 32 | ### OpenVPN Community Meetup 2024 |
|||
| 33 | - Naming: We decided to rename from 'Hackathon' to 'OpenVPN community meetup'. This has a more open spirit to it, as we want to encourage developers and those interested in contributing to feel welcome. |
|||
| 34 | - Where: Karlsruhe, Germany. It is a relatively central location in Europe and is fairly easily reachable by train. A meeting location is yet to be arranged. |
|||
| 35 | - When: At the moment tentatively set to 20-22 September 2024. |
|||
| 36 | - Who: We'll do an open invitation to openvpn-devel mailing list, but also CC: specifically past attendees and people of interest. |
|||
| 37 | - Shirts: There is plenty of time still to prepare a shirt design. |
|||
| 38 | ||||
| 39 | ### Website Release Process Woes |
|||
| 40 | - There is actual movement on this now, they're moving the Community Downloads content now to another CMS. |
|||
| 41 | - They will also move Security Advisories to this other CMS as well so both can be updated independently from website updates. |
|||
| 42 | ||||
| 43 | ### Static-Key Mini How-to is Outdated |
|||
| 44 | - This page is badly outdated: [Static Key Mini How-to](https://openvpn.net/community-resources/static-key-mini-howto/) |
|||
| 45 | - The company will send this to a tech writer to redo based on info from the [GitHub Doc](https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/example-fingerprint.rst) and also retain a link to that GitHub doc. |
|||
| 46 | - Having a simple guide online will help adoption. |
|||
| 47 | ||||
| 48 | ### OpenVPN Release Process Topics |
|||
| 49 | - There was a request on [GitHub Issue #397](https://github.com/OpenVPN/openvpn/issues/397) to have releases on GitHub as well. |
|||
| 50 | - djpig seems to think it would be fairly doable to copy/paste that info to GitHub as well. |
|||
| 51 | - We could do this during a next release. |
|||
| 52 | ||||
| 53 | ### OpenVPN 2.6 Performance Results |
|||
| 54 | - Tests should cover: GRE, IPSec, userland, DCO |
|||
| 55 | - Platforms: Linux, FreeBSD, Windows |
|||
| 56 | - Requires time to be dedicated to doing this |
|||
| 57 | - When time available will do it. |
|||
| 58 | ||||
| 59 | ### What's Going on with New Taskbar Icons? |
|||
| 60 | - matt provided icons in [GitHub Issue #595](https://github.com/OpenVPN/openvpn-gui/issues/595) |
|||
| 61 | - **Update:** will be picked up by selva when he has time. |
|||
| 62 | ||||
| 63 | ### Security@openvpn.net Mailing List |
|||
| 64 | - The company is trying to get to SOC2 compliance. |
|||
| 65 | - Probably will need a simple NDA to be signed by recipients of emails to security@openvpn.net |
|||
| 66 | - The company guy took the standard NDA we use for contractors, suggests to use that. |
|||
| 67 | - novaflash thinks we should review that first to see if it's really suitable or not, community members are not contractors after all. |
|||
| 68 | ||||
| 69 | ### Another Key Signing Topic |
|||
| 70 | - The company switched EV code signing to CloudHSM, this is the same cert type we use for driver signing, is also suitable for binary signing. |
|||
| 71 | - In the future, we could possibly switch the community to that same key. Saves having to maintain 2 different keys. |
|||
| 72 | - Depends on how hard/easy it is to access the company key signing thing from community infrastructure. |
|||
| 73 | - Also no high priority at the moment, we have a working solution now. |
|||
| 74 | ||||
| 75 | ### SBOM Topic |
|||
| 76 | - cron2 was asked if OpenVPN has a software bill of materials. Answer was no. |
|||
| 77 | - Coincidentally, in OpenVPN Inc a security requirement is to have an SBOM so this is on our list of things to do |
|||
| 78 | - When we pick up this task we can coordinate on it. |
|||
| 79 | ||||
| 80 | ### Forums Machine on Community Infrastructure is Only Non-Linux System |
|||
| 81 | - mattock made a new forums system that runs on Rocky Linux 8 as agreed with ecrist. |
|||
| 82 | - ecrist has looked at it but the current state of the migration is unknown. |
|||
| 83 | ||||
| 84 | ### Management Interface Documentation on Main Website Will Be Updated with Info from doc/management-notes.txt |
|||
| 85 | - novaflash will pick this up at some point. |
