Blame
| 6f02e7 | Samuli Seppänen | 2025-01-29 06:40:08 | 1 | # Basic Info |
| 2 | ||||
| 3 | - **Time:** Wednesday 25 October 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: Publish security assessment of OpenVPN2 codebase on main website.** |
|||
| 11 | - Approvals and preparations are done for this. |
|||
| 12 | - Marketing decided to make it a larger topic and include past security assessments. |
|||
| 13 | - Expected to be published within the next 3 weeks. |
|||
| 14 | ||||
| 15 | - **Updated: License amendment for OpenVPN2 to solve openssl/mbedtls licensing issues** |
|||
| 16 | - The OpenSSL James Bottomley stuff is resolved now. |
|||
| 17 | - The --tls-export-cert feature needs to be removed by dazo and reimplemented by plaisthos. |
|||
| 18 | - Then it is up to dazo to review things so we can work on finalizing this. |
|||
| 19 | - One of the tasks is reviewing if remaining items are trivial patches, and maybe get legal advice on those if necessary. |
|||
| 20 | - For new contributions the new license already applies so maxf is unblocked to implement mbedtls3 support on master. |
|||
| 21 | - maxf mentioned he will look into how much work it is to backport mbedtls3 to 2.6. |
|||
| 22 | ||||
| 23 | - **Updated: OpenVPN 2.6.7 release** |
|||
| 24 | - CMake backport is in. |
|||
| 25 | - We are working on some outstanding patches that we are working to get in. |
|||
| 26 | - Also there is a div-by-zero bug we want to get out soon so we're waiting until that is in. |
|||
| 27 | ||||
| 28 | - **Tunnelcrack published now [https://tunnelcrack.mathyvanhoef.com](https://tunnelcrack.mathyvanhoef.com)** |
|||
| 29 | - A post was published at [TunnelCrack community wiki article](https://wiki.openvpn.net/TunnelCrack) |
|||
| 30 | - More details are in the Hackathon2023 meeting summary. |
|||
| 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 outdated badly: [https://openvpn.net/community-resources/static-key-mini-howto/](https://openvpn.net/community-resources/static-key-mini-howto/) |
|||
| 45 | - Company will send this to tech writer to redo based on [https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/example-fingerprint.rst](https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/example-fingerprint.rst) info 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 in [https://github.com/OpenVPN/openvpn/issues/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 [https://github.com/OpenVPN/openvpn-gui/issues/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 | - 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 | - Company guy took standard NDA we use for contractors, suggests using 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 | - 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 future, we could possibly switch community to that same key. Saves having to maintain 2 different keys. |
|||
| 72 | - Depends on how hard/easy it is to access company key signing thingee 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. |