1 | <djpig> moin moin |
---|
2 | <mattock> hi! |
---|
3 | <Giaan> hi |
---|
4 | <ordex> hi |
---|
5 | <MaxF> moin! |
---|
6 | <djpig> okay, since novaflash will not attend the meeting let me start with the first topic |
---|
7 | <mattock> +1 |
---|
8 | <djpig> "Adding explicit license for openvpn-buildbot" |
---|
9 | <mattock> I don't have particular opinions, but typically I use BSD-2-Clause for stuff where the license does not matter much |
---|
10 | <djpig> yeah, I would agree with that |
---|
11 | <djpig> don't think this needs GPL |
---|
12 | <ordex> yeah |
---|
13 | <mattock> I can send a PR that adds the license |
---|
14 | <djpig> thanks |
---|
15 | <djpig> moving on |
---|
16 | <djpig> (I will add notes to the Wiki page about the discussion) |
---|
17 | <djpig> "Pending Buildbot PRs" |
---|
18 | * becm has quit (Ping timeout: 256 seconds) |
---|
19 | <djpig> mattock: I have been reviewing https://github.com/OpenVPN/openvpn-buildbot/pull/32 today and that looks good to me |
---|
20 | <plaisthos> hey |
---|
21 | <mattock> hi plaisthos! |
---|
22 | <mattock> djpig: ok! |
---|
23 | <djpig> mattock: https://github.com/OpenVPN/openvpn-buildbot/pull/31 I honestly couldn't care less about. I just don't think this solves an actual problem right now |
---|
24 | <plaisthos> MaxF: if you want something to do, you can make mbed TLS compile with OpenVPN when -DMBEDTLS_DEPRECATED_REMOVED is set :P |
---|
25 | <mattock> djpig: I think "somebody" cared, possibly cron2 |
---|
26 | <MaxF> is this for version 2 or 3? |
---|
27 | <plaisthos> MaxF: 3 |
---|
28 | <MaxF> so 2 still works? |
---|
29 | <plaisthos> MaxF: I looked into making openvpn3 compatible with mbed TLS 3 and we have that set for 2 |
---|
30 | <plaisthos> and looked what happens when you add that in OpenVPN 2.x and it also spectularly fails |
---|
31 | <MaxF> I'll look at it when I find time. Or someone to delegate |
---|
32 | <djpig> mattock: okay, I will try to look at it. But #32 looks much more relevant to me. So I will look into deploying that first |
---|
33 | <djpig> let's move on for now |
---|
34 | <djpig> "Wiki Migration" |
---|
35 | <mattock> djpig: +1 to 31 and 32 |
---|
36 | * uddr35 (~uddr35@194.44.71.210) has joined |
---|
37 | <rob0> what is the link to new wiki? |
---|
38 | <uddr35> aloha |
---|
39 | <lev__> hola |
---|
40 | <mattock> djpig: one more note regarding #31: I think it paves the way for "different tests for different files" as well (see https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg28127.html) |
---|
41 | <mattock> rob0: I can't recall, need to dig up meeting minutes to figure it out :) |
---|
42 | <djpig> mattock: right, good point |
---|
43 | <mattock> I'll figure out the wiki addresses, no meeting minutes |
---|
44 | <djpig> maybe add them to https://community.openvpn.net/openvpn/wiki/TracWikiReplacements which is where I expected to find them ;) |
---|
45 | <mattock> yeah, the IPs are dynamic though, but at least the path would be known |
---|
46 | <djpig> and then maybe give people some more time to take a look and try the topic next week again? |
---|
47 | <mattock> works for me |
---|
48 | <djpig> Server-side testing |
---|
49 | <djpig> meeting time |
---|
50 | <mattock> https://community.openvpn.net/openvpn/wiki/TracWikiReplacements updated with URLs |
---|
51 | <ordex> • xwiki: http://18.184.233.206:8080 |
---|
52 | <ordex> • wiki.js: http://18.184.233.206:8081 |
---|
53 | <vpnHelper> Title: Main page | Wiki.js (at 18.184.233.206:8081) |
---|
54 | <ordex> just FTR |
---|
55 | <ordex> ah ok |
---|
56 | <rob0> thanks |
---|
57 | <djpig> who would like to attend that meeting about server side testing? Me, mattock. cron2, ordex ? uddr35 ? |
---|
58 | <ordex> cron2 for sure as he has the one having implemented the current version |
---|
59 | <ordex> that he uses for testing privately |
---|
60 | * becm (~Thunderbi@rtr.astos.de) has joined |
---|
61 | <ordex> I can try to join depending on the time |
---|
62 | <djpig> cron2: so what times would work for you? |
---|
63 | <uddr35> @djpig yes please |
---|
64 | <djpig> hmm, not sure whether he is here, actually |
---|
65 | <mattock> I think cron2 is missing today |
---|
66 | <ordex> normally he has time in the morning, but we need him t tell us which day :-D so let's arrange the meeting when he's online |
---|
67 | <ordex> yeah |
---|
68 | <djpig> okay |
---|
69 | <mattock> I think we're down to last topic: 2.6.9 release? |
---|
70 | <djpig> yes |
---|
71 | <djpig> the open question seems to be whether we wait for an easy-rsa fix or not |
---|
72 | <lev__> I think on Windows we are stuck with EasyRSA |
---|
73 | <djpig> lev__: what is the status of the security fix for Windows? Is that ready? |
---|
74 | <lev__> YES |
---|
75 | <lev__> oops |
---|
76 | <lev__> yes |
---|
77 | <djpig> does that go into openvpn-build or openvpn? |
---|
78 | <lev__> -build |
---|
79 | <lev__> so we could tag openvpn, I think |
---|
80 | <djpig> We could always decide to release the easy-rsa fix as an installer-only release |
---|
81 | <lev__> yeah. Also we don't have any estimate when it will be fixed |
---|
82 | <djpig> I think if we do not have a fix for easy-rsa in a few days we just go ahead with the release since it is not a regression |
---|
83 | <djpig> should we target early next week? Monday/Tuesday? |
---|
84 | <lev__> also we should probably add some easyrsa testing to windows TA |
---|
85 | <lev__> something simple like creating PKI and server/client certs and validate that something has been indeed created |
---|
86 | <djpig> makes sense. you are certainly welcome to do so :) |
---|
87 | <lev__> but then again we will have a proof that it works on Windows Server 2022, and nothing about Windows 11 |
---|
88 | <djpig> right, also the remote powershell session might have different behavior than the shell launched from UI |
---|
89 | <djpig> okay, any other topics not mentioned on the meeting page? |
---|
90 | <MaxF> yes |
---|
91 | <MaxF> Can we arrange a meeting to talk about SBOMs some time in the next two weeks? I've got one colleague at Fox who has been looking into that topic, and I thought maybe we can get together with the people at OpenVPN Inc. who are working on it. |
---|
92 | <djpig> yeah, I would be happy to talk to someone about that. Because I have been looking into it, but still have no idea what would be useful... So happy to hear from someone with a slightly different perspective |
---|
93 | <MaxF> what time would work for you? |
---|
94 | <djpig> 11:00 CET is generally a good time, except on Thursdays |
---|
95 | <uddr35> I can not make it Feb 14, everything else is good for me |
---|
96 | <djpig> MaxF: let us know if you need more options |
---|
97 | <MaxF> how about Tuesday Feb 13? |
---|
98 | <MaxF> at 11 |
---|
99 | <djpig> works for me |
---|
100 | <uddr35> works for me |
---|
101 | <djpig> MaxF: will you take care of the technical details? |
---|
102 | <MaxF> just asked my colleague, it works for him too |
---|
103 | <MaxF> yes, you guys usually use jitsi right? |
---|
104 | <djpig> we have in the past, but inside the company it is all Slack now. But I'm happy to join whatever |
---|
105 | <MaxF> djpig I have your e-mail but not uddr35 's I think |
---|
106 | <djpig> I can send it via Signal |
---|
107 | <MaxF> alright |
---|
108 | <uddr35> @djpig thanks |
---|
109 | <djpig> okay, any other topics |
---|
110 | <djpig> ? |
---|
111 | <rob0> We can set up a shared Slack channel if you want. I am a Slack admin for us. |
---|
112 | <MaxF> I never used slack, does it run in the browser? |
---|
113 | <rob0> it can |
---|
114 | <MaxF> then that should work |
---|
115 | <djpig> rob0: let's see whether we need a continous discussion. For a one-time meeting this sounds like overkill |
---|
116 | <rob0> I have done that on Linux |
---|
117 | <rob0> okay, just tossing out as a suggestion |
---|
118 | <djpig> rob0: yeah thanks. I know we have done that for e.g. security audits and other projects like that |
---|
119 | <uddr35> slack works in browser but yeah for one meeting jitsi would be just easier |
---|
120 | <MaxF> ok, then we use either jitsi or teams, I'll let you know |
---|
121 | <djpig> if there are no more topics I guess this meeting is finished for today |
---|
122 | <MaxF> nothing more from me |
---|
123 | <mattock> +1 |
---|
124 | <djpig> okay, I will try to prepare a summary mail |
---|
125 | <ordex> <o/ |
---|
126 | <djpig> mattock: do we have login credentials for the test wikis? |
---|
127 | * MaxF has quit (Quit: Client closed) |
---|
128 | <mattock> djpig: I created those for everyone who wanted when they were "revealed" |
---|
129 | <mattock> if you want an account just let me know |
---|
130 | * uddr35 has quit (Remote host closed the connection) |
---|
131 | <cron2> apologies for missing the meeting... I was in the school library, which does have wifi *and* LTE (if the windows are open), but they did something weird to the network and I was totally and utterly offline, and couldn't leave either |
---|
132 | <cron2> 2.6.9 release "early monday" would work nicely for me (so I'd tag + push sunday evening, and you tell me on monday if I bumbled something) |
---|
133 | <djpig> cron2: okay, sounds good |
---|
134 | <djpig> mattock: yes, please |
---|
135 | <cron2> so, djpig, plaisthos: I'd like to proceed with 475, but it needs 474 as prerequisite, and this is still sitting on -1, possibly caused by a misunderstanding? |
---|
136 | <plaisthos> I am still not really happy with the leak suppression that we are forced to do, I hoped to look into that much sooner |
---|
137 | <djpig> ECHAN |
---|