All of lore.kernel.org
 help / color / mirror / Atom feed
* [Openvpn-devel] Community meetings in June 2019
@ 2019-06-05 11:55 
  2019-06-06 19:10 ` [Openvpn-devel] Summary of the community meeting (6th June 2019) 
                   ` (3 more replies)
  0 siblings, 4 replies; 12+ messages in thread
From:  @ 2019-06-05 11:55 UTC (permalink / raw)
  To: openvpn-devel


[-- Attachment #1.1: Type: text/plain, Size: 790 bytes --]

Hi,

Our community meetings will alternate between Wed 11:30 CEST and Thu
20:00 CEST.

Next meetings have been scheduled to

- Thu 6th June 20:00 CEST
- Wed 12th June 11:30 CEST
- Thu 20th June 20:00 CEST
- Wed 26th May 11:30 CEST

The place is #openvpn-meeting IRC channel at Freenode. Meeting agendas
and summaries are in here:

<https://community.openvpn.net/openvpn/wiki/IrcMeetings>

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock





_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel


-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Openvpn-devel] Summary of the community meeting (6th June 2019)
  2019-06-05 11:55 [Openvpn-devel] Community meetings in June 2019 
@ 2019-06-06 19:10 ` 
  2019-06-12 10:16 ` [Openvpn-devel] Summary of the community meeting (12th " 
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 12+ messages in thread
From:  @ 2019-06-06 19:10 UTC (permalink / raw)
  To: openvpn-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 2188 bytes --]

Hi,

Here's the summary of the IRC meeting.

---

COMMUNITY MEETING

Place: #openvpn-meeting on irc.freenode.net
Date: Thursday 6th June 2019
Time: 20:00 CEST (18:00 UTC)

Planned meeting topics for this meeting were here:

<https://community.openvpn.net/openvpn/wiki/Topics-2019-06-06>

Your local meeting time is easy to check from services such as

<http://www.timeanddate.com/worldclock>

SUMMARY

cron2, dazo, ecrist, lev, mattock and ordex participated in this meeting.

---

Noted that the next OpenVPN hackathon will be arranged in Trento, Italy
on weekend of 8th November 2019. We will need many cakes, and a
particularly big HLK cake (assuming all HLK tests have passed by then).

---

Discussed tap-windows6 HLK testing. HLK tests are running in mattock's
physical HLK environment, but they take a huge amount of time. It may
actually be possible to make a release for Windows Server 2016/2019 next
week.

---

Discussed lev's patch to tap-windows6:

<https://github.com/OpenVPN/tap-windows6/pull/86>

OpenVPN 3 developers have some reports that it works but not with
hibernate/resume (which worked before). The error is different, though,
but it claimed that the problem surfaced with this change. Investigation
is ongoing.

---

Talked about wintun. Lev would like to get somebody to test his wintun
support in OpenVPN 2.

---

Discussed the DoS attack on forums. It was narrowed down to a single IP.
Based on historical data this kind of DoS is very rare on forums so no
action is needed at the moment.

Mattock will ensure that alert emails from forums, community (trac) and
community LDAP go to erist as well.

---

Discussed our Patchwork installation. It was agreed that an upgrade
would be useful. Mattock was fine with upgrading it after the HLK thing
is done.

---

Noted that OpenVPN 2.5 is progressing in various areas.

Next mini-hackathon will be arranged tomorrow (7th June) starting in
European morning. As usual, it will focus on OpenVPN 2.5 work.

---

Full chatlog attached.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock




[-- Attachment #1.1.2: openvpn_irc_meeting_chatlog_2019-06-06.txt --]
[-- Type: text/plain, Size: 14966 bytes --]

(21:00:38) mattock: good evening people!
(21:00:46) mattock: or morning, or whatever
(21:00:47) mattock: :)
(21:02:01) ordex: everything !
(21:02:26) ***cron2 feels sleepy, so it could be morning or evening or afternoon
(21:03:31) mattock: ecrist: there?
(21:05:00) mattock: https://community.openvpn.net/openvpn/wiki/Topics-2019-06-06
(21:05:01) vpnHelper: Title: Topics-2019-06-06 – OpenVPN Community (at community.openvpn.net)
(21:05:06) mattock: #1 "hackathon planning"
(21:07:03) ordex: yeah
(21:07:13) ordex: so, today I have sent an email saying that Nov 8th is confirmed
(21:07:15) lev__: hello
(21:07:24) ***dazo is here
(21:07:39) cron2: which was about the reason why I put the topic on the agenda - have the date fixed so we can all start planning
(21:07:43) ordex: not sure there is much more to do on your side - I will provide some details about accommodations in the area
(21:07:46) ***cron2 intends to take the train to trento
(21:07:55) mattock: hi!
(21:08:05) cron2: maybe bring $wife along if grandparents can take the kids...
(21:09:12) ordex: not a bad idea :)
(21:10:07) cron2: and we need to agree on the number of cakes to bring along :-)
(21:10:13) ordex: :D
(21:10:19) cron2: mattock needs to bring a MONSTROUSLY HUGE HLK cake
(21:10:22) ordex: I don't think there is any overflow risk
(21:11:31) mattock: maybe we should order the cake(s) on-site
(21:12:06) ordex: or cook onsite :D
(21:12:10) mattock: yeah
(21:12:53) cron2: this sounds like fun :-) - not sure it will make the hackathon turn out more code, but fun, definitely
(21:13:06) ordex: hehe
(21:13:15) ordex: if it's successful we can do v2 shortly after ;P
(21:13:24) mattock: so, shall we move forward from hackathon cakes?
(21:13:25) mattock: :P
(21:13:30) ordex: yeah
(21:13:42) mattock: maybe buildslave updates off the topic list
(21:13:52) mattock: so I just managed to have a quick look at some of the failures
(21:14:00) cron2: ohyeah :)
(21:14:21) mattock: this may have been discussed earlier but I'll ask: is there a known fix for the cmocka issue?
(21:14:30) cron2: what is "the cmocka issue"?
(21:14:41) mattock: ok, let's discuss this tomorrow in the hackathon then :)
(21:14:42) ***cron2 is not sure
(21:15:19) cron2: I have fixed my cmocka issues by breaking "git submodule", so it won't do the submodule init and the older buildslaves are happy
(21:15:36) mattock: I'll have to investigate my particular issue then
(21:15:39) mattock: anyways
(21:15:57) mattock: tap-windows6 updates: most of the HLK tests have run, there have been quite a few non-deterministic failures
(21:16:06) mattock: reruns generally succeed
(21:16:25) cron2: is this sufficient?  "try long enough until everything has succeeded once"?
(21:16:30) mattock: there is one configuration on the HLK client/support I have to fix, which might help make those problems go away
(21:16:35) mattock: yeah, it should be enough
(21:16:45) mattock: I have not even bothered with the tests that require special configuration
(21:16:54) mattock: just wanted to get most of them look green
(21:17:04) mattock: then debug and fix whatever remains
(21:17:04) cron2: so what nexxt?
(21:17:16) mattock: babysit the tests (they take a huge amount of time and occasionally hang)
(21:17:35) cron2: is this "master" or "with rozmansi's changes wrt virtual ethernet"?
(21:17:45) cron2: and with or without lev__'s change?
(21:18:07) mattock: rozmansi patch caused issues with some tests as jamallx mentioned
(21:18:26) mattock: I believe (would have to check) that this is plain "master"
(21:18:54) cron2: mmmh.  We need more active communication on this... rozmansi's patch should make issues disappear, not new ones appear...
(21:19:43) mattock: I talked to rozmansi last week and he said he'd try to have a look at the various settings in the inf file to see if those make difference in _what_ tests need to run
(21:19:58) mattock: I had a look at his settings + MS docs and his guess seemed the "correct" one
(21:20:34) lev__: it would be nice if rozmansi could have a look at openvpn2 wintun patch 
(21:20:47) mattock: rozmansi is very, very busy
(21:20:56) mattock: that is the challenge
(21:21:37) mattock: but anyways, HLK is getting there and I have rather high hopes that we will be able to actually do a release (next week)
(21:21:51) lev__: I got 27% better performance with wintun comparison to wintap in recent tests
(21:22:12) cron2: lev__: how do you talk to wintun from ovpn3?
(21:22:57) dazo: in regards to lev__'s patch to tap-windows6 ... if it's the sleep/resume issue ... we have some reports it works but not with hibernate/resume (which worked before).  Different error, though, but claims is they surfaced with this change .... lev__ might have more details
(21:23:10) lev__: cron2: same as in openvpn2 - createfile to open device, ipconfig to set up routing
(21:23:33) dazo: lev__: thos 27% ... is that with mbedtls or openssl?
(21:23:43) cron2: lev__: so openvpn3 runs as admin?
(21:23:55) lev__: dazo: with openssl
(21:24:02) lev__: cron2: yep
(21:24:39) dazo: lev__: nice! ... iirc, prior tests the diff was less with openssl
(21:24:41) cron2: mmmh.  I had hoped you have a "does not need to run as admin" solution there, like "use the service to open the driver"
(21:24:48) lev__: there is a report that Connect client doesn't reconnect after "deep sleep", but I wasn't able to reproduce it so far
(21:25:13) lev__: cron2: that's a flag in wintun, they decided to limit it to admins and localsystem
(21:25:45) lev__: "Indeed we're keeping it"
(21:25:45) lev__: locked down to SYSTEM for the time being. As we gain a better
(21:25:45) lev__: understanding of the attack surface, maybe we'll reduce that to
(21:25:47) lev__: built-in administrators.
(21:25:47) cron2: lev__: I understand that part :-) - you can't setup routing without admin privs, but we still do
(21:26:17) cron2: so, maybe is "use the service to open the driver and pass a file handle back to openvpn"...
(21:26:25) cron2: a possible approach
(21:26:42) dazo: that restriction makes somewhat sense ... but I think a similar approach to what Android does, passing the tun/wintun fd to an unprivileged openvpn process makes sense ... iservice might be the entrance here
(21:26:54) dazo: what cron2 says :-P
(21:27:18) lev__: dazo: there is no difference in wintun/tap performance with openvpn3 + openssl 
(21:27:30) cron2: reprasing my question... Connect on windows has its own service today.  Does ovpn3 use said service, or the iservice, or no service at all today?
(21:27:47) dazo: lev__: ahh, right ... I'm mixing things
(21:28:16) cron2: lev__: this is curious, because it hints "the performance issue is not in tap6"
(21:28:28) lev__: cron2: the "classic" connect which has been around for years uses service
(21:28:30) dazo: cron2: what lev__ is using now, is cli.exe - a reference client shipped in openvpn3 project ....
(21:28:50) dazo: cron2: and Connect uses the service ... but we don't havea Connect client with wintun yet
(21:28:57) cron2: so there is no "Connect based on ovpn3" yet?
(21:29:08) dazo: current Connect uses service + ovpn3
(21:29:17) dazo: (with tap-windows6)
(21:30:02) lev__: the new "universal connect?" (or whaever it is called) uses "agent" process which runs as a service to set up routing, but it opens device under unprivileged process 
(21:30:32) cron2: dazo: so "agent" is the "new iservice" for Connect?
(21:30:36) dazo: this "agent" is somewhat similar to iservice, yes
(21:30:38) cron2: (we need to get terminology right here)
(21:30:43) lev__: yep
(21:30:54) dazo: (very different approach, but serves the same purpose)
(21:31:23) ***cron2 looks forward to an architecture description in Trento :-)
(21:31:32) ecrist: sorry, I'm here
(21:31:36) dazo: heh
(21:31:39) ecrist: I know I'm late
(21:31:54) dazo: no worries
(21:32:46) mattock: hi ecrist!
(21:33:07) ecrist: hello!
(21:33:27) lev__: also I am not quite sure about buffer size for wintun, in worst case it could be 256*0xF000 and there is no scatter / gather IO support
(21:33:53) lev__: I use somethng like 1500 * 256 which tends to work
(21:34:10) dazo: so there seems to be room for improvements in the wintun api, but it's a good starting point
(21:35:00) lev__: I would appreciate if someone besides me could give wintun patch a try
(21:37:07) mattock: and then came silence
(21:37:30) dazo: :)
(21:37:36) lev__: I think everyone are busy building openvpn2 with wintun
(21:37:43) mattock: I'm sure :)
(21:37:54) ***cron2 knows this particular silence
(21:38:34) mattock: shall we move on and just accept that nobody will comment on lev's proposal? :P
(21:39:00) mattock: we still have a couple of topics to cover, especially now that ecrist is here
(21:39:13) cron2: yeah
(21:39:40) mattock: ok so the possible DoS attack on forums a while back
(21:39:47) mattock: ecrist: any further info on that one?
(21:40:21) ecrist: we narrowed it down to a single customer of a large provider
(21:40:24) ecrist: it's stopped since
(21:40:35) cron2: not even distributed...
(21:41:16) ecrist: based on the feedback I recevied in the past about cloudflare, I don't think we should, or really need, to put it in front of the forum
(21:41:44) cron2: not sure how well cloudflare works for more interactive content
(21:42:36) mattock: we do have it in front of everything "commercial", but I agree that if this kind of thing only happens every 5 years let's not put CloudFlare in front
(21:42:42) mattock: of forums
(21:43:09) ecrist: since the forums were founded in '08, I can count on one hand the number of times we've had issues.
(21:43:10) mattock: we had it in front of Trac for a while, but it caused annoying CAPTCHA issues
(21:44:00) ecrist: if there are issues that crop up, *I* don't expect the corp guys to have to deal with it, just send me a text and I'll fix it
(21:44:19) cron2: where is the forum hosted today?
(21:44:22) mattock: EC2
(21:44:38) mattock: by OpenVPN Inc.
(21:44:46) mattock: ecrist is the effective maintainer though
(21:45:02) mattock: I generally touch it when I work on some puppet stuff which might affect FreeBSD
(21:46:09) mattock: at the moment we don't have SMS alerts in general
(21:46:21) ecrist: just so it's out there, I'm perfectly fine taking community stuff out of corp hands if it's a problem
(21:46:59) mattock: the corp guys just dislike seeing the alerts if they are unable to do anything about them :)
(21:47:16) cron2: you can document the "doing" bit -> "send mail to ecrist"
(21:47:21) cron2: so they know they can do something
(21:47:22) cron2: solved
(21:47:36) dazo: If the corp side cut be somewhat more hands-on when issues crop-up, that would be beneficial ... I am NOT saying corp side should take over the responsibility, but kind of know what's happening and can take immediate actions while ecrist is sleeping or unavailable ... to kind of spread the maintenance load - and also include the corp side more on the community side as well
(21:47:40) mattock: even better, if we configured SMS alerts we could have forums alerts go directly ecrist
(21:48:44) mattock: the "normal" solution on the corp side is to use CloudFlare everywhere, which is the reason why that was to first medicine here as well
(21:49:08) mattock: ecrist: do you actually get email alerts from forums?
(21:49:09) mattock: can't recall
(21:49:30) mattock: that could be done fairly easily
(21:49:36) ecrist: no
(21:49:38) ecrist: I don't
(21:49:42) mattock: ok, want me to fix that?
(21:50:30) ecrist: sure
(21:51:12) mattock: forums only?
(21:51:19) mattock: ldap, community, patchwork?
(21:51:46) ecrist: not patchwork, but ldap, community, forums
(21:51:55) mattock: ok
(21:52:00) mattock: noting that in my ticket
(21:52:09) ecrist: and, I *did* send instructions last time we had a problem, even specific commands that could be used
(21:52:29) mattock: last time = this time, or way back when?
(21:52:36) ecrist: January
(21:52:38) ecrist: iirc
(21:53:21) mattock: ok, not sure if the guys remembered that
(21:54:15) ecrist: I'm guessing not. :)
(21:54:27) dazo: speaking of patchwork ... how up-to-date is it?
(21:57:13) cron2: I have not yet ticket off the sitnl patchset
(21:57:27) cron2: (because I want to write a summary and want to discuss next steps with ordex)
(21:57:31) cron2: besides this, should be accurate
(21:58:05) dazo: oh, I meant the patchwork software ... not our usage of it :)
(21:58:09) mattock: ah
(21:58:13) cron2: ah :-)
(21:58:23) mattock: it has not been updated since install
(21:58:29) mattock: does that answer your question?
(21:58:31) mattock: :)
(21:58:51) mattock: I'm more than happy to upgrade it post-HLK
(21:58:58) dazo: yes, can we look at an upgrade here?  I wonder if that would help making 'git pw' integrate better
(22:00:56) mattock: I guess I answered that as well
(22:00:58) mattock: I will create a ticket
(22:01:14) mattock: any other topics
(22:01:19) mattock: 1 hour 1 minute already
(22:01:22) dazo: yeah, just timing and network latency confusing us :)
(22:01:46) cron2: 64 bytes from 195.30.0.2: icmp_seq=1870 ttl=55 time=6939 ms
(22:01:52) cron2: this is latency...
(22:02:01) cron2: anyway, short update on 2.5
(22:02:05) dazo: I've started for real looking into plaisthos auth-token-hmac patches ... found an issue with 'make check', so I believe we will see some updates ... but generally diving through the patches
(22:02:40) cron2: sitnl mostly merged, except for a showstupper in 5/7
(22:03:54) cron2: and there is cleanup work to do (uncrustify, make check fails, ...)
(22:04:10) cron2: then, small patches (syzzer stuff) next, then ipv6-only
(22:04:45) dazo: you can throw autoconf/automake stuff my way ... I begin to get a fairly good grasp on that these days
(22:05:49) mattock: regarding openvpn 2.5 - who can make it to mini-hackathon tomorrow?
(22:05:53) cron2: this is good - opened a trac ticket (on the config.h stuff) just yesterday
(22:06:20) cron2: wrt tomorrow: I need to urgently show up in the datacenter tomorrow to get stuff finished that was due last week.  But I will be around afternoonish
(22:06:23) mattock: my focus will be "fix buildslaves", "babysit HLK" (the latter being the norm these days)
(22:06:24) dazo: I am planning on it tomorrow .... and I hope ordex, lev__ and plaisthos will join too :)
(22:06:34) cron2: cool
(22:06:44) mattock: maybe lev can force you guys to test wintun
(22:06:46) mattock: :P
(22:06:55) dazo: cron2: if I seem to be missing ... send me a grumpy mail! ;-)
(22:07:06) cron2: dazo: you bet!
(22:07:27) mattock: meeting concluded?
(22:07:34) cron2: (I'll just push a commit removing Dazo's name from all files... :-) )
(22:07:45) cron2: mattock1: good night
(22:07:50) cron2: see you tomorrow
(22:07:59) mattock: bye guys!
(22:08:06) ecrist: l8r folks

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Openvpn-devel] Summary of the community meeting (12th June 2019)
  2019-06-05 11:55 [Openvpn-devel] Community meetings in June 2019 
  2019-06-06 19:10 ` [Openvpn-devel] Summary of the community meeting (6th June 2019) 
@ 2019-06-12 10:16 ` 
  2019-06-20 19:14 ` [Openvpn-devel] Summary of the community meeting (20th " 
  2019-06-26 11:05 ` [Openvpn-devel] Summary of the community meeting (26th " 
  3 siblings, 0 replies; 12+ messages in thread
From:  @ 2019-06-12 10:16 UTC (permalink / raw)
  To: openvpn-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 1480 bytes --]

Hi,

Here's the summary of the IRC meeting.

---

COMMUNITY MEETING

Place: #openvpn-meeting on irc.freenode.net
Date: Wednesday 12th June 2019
Time: 11:30 CEST (9:30 UTC)

Planned meeting topics for this meeting were here:

<https://community.openvpn.net/openvpn/wiki/Topics-2019-06-12>

Your local meeting time is easy to check from services such as

<http://www.timeanddate.com/worldclock>

SUMMARY

dazo, lev, mattock, ordex and syzzer participated in this meeting.

---

Mattock gave an update on tap-windows6 HLK testing. The physical HLK
environment is working well. There a couple of odd-duck test failures
(=reason unknown/not looked into yet) as well as a few known issues
(=solution known). Some of the tests that have failed are not even
mandatory (e.g. "Static tools logo test"). A server 2019 Core HLK client
is needed to pass the "Operating in Server Core" test.

---

Mattock relayed an update from OSTIF.  The Operator Foundation should be
able to complete the obfs4, shadowsocks, and meek1 plugins (for OpenVPN)
by the end of October.

--

Talked about OpenVPN 2.x, and testing in particular. User/pass auth
testing has started to become quite complex. In that area more automated
testing would be good. Also, testing (things through) the management
interface would be a nice addition.

--

Full chatlog attached.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

[-- Attachment #1.1.2: openvpn_irc_meeting_chatlog_2019-06-12.txt --]
[-- Type: text/plain, Size: 4953 bytes --]

(12:35:24) mattock: hi!
(12:35:44) lev__: hi
(12:37:51) ordex: hi mattock1 
(12:37:51) ordex: :)
(12:38:17) dazo ha scelto come argomento: Next meeting 20/June/2019 at 20:00 CEST.  Agenda at https://community.openvpn.net/openvpn/wiki/Topics-2019-06-12
(12:38:45) dazo: hopefully at least 1 of 2 of the information parts will be valid next week :-P
(12:39:48) mattock: hi guys!
(12:39:58) mattock: let's check the agenda
(12:40:10) dazo: #1 tap-windows6 update :)
(12:40:17) mattock: https://community.openvpn.net/openvpn/wiki/Topics-2019-06-12
(12:40:19) vpnHelper: Title: Topics-2019-06-12 – OpenVPN Community (at community.openvpn.net)
(12:40:37) mattock: so, I've slowly worked through most of the tests
(12:40:57) mattock: there are a couple of odd ducks (=unknown issues) which I need to look into
(12:41:18) mattock: plus those tests which are known to fail without some special setup
(12:41:46) mattock: plus "Operate in Server Core" requires a Server 2019 Core installation
(12:41:51) mattock: =HLK client
(12:42:18) mattock: then I also need to verify which of the tests are actually mandatory (e.g. static tools logo test is failing, but it is not mandatory)
(12:43:32) mattock: so, looking good, and I _hope_ the remaining failures can be resolved this week
(12:44:30) mattock: the physical HLK test environment seems to work well
(12:44:46) mattock: that's all there is about tap-windows6 at my end
(12:46:02) mattock: I have an update from OSTIF btw
(12:46:20) mattock: maybe that would work as topic #2
(12:46:43) syzzer: at least decent progress on the tap-windows side, that's nice :)
(12:46:55) syzzer: what's with OSTIF?
(12:47:03) mattock: syzzer: yeah, though it is not done until it is done :)
(12:47:17) mattock: first of all, the wanted to thank ordex for his work
(12:47:29) dazo: syzzer: https://ostif.org/
(12:47:32) vpnHelper: Title: OSTIF.org Open Source Technology Improvement Fund (at ostif.org)
(12:47:47) mattock: "obfs4, shadowsocks, and meek1 plugins should be completed by the end of October"
(12:47:56) dazo: nice!
(12:48:11) ordex: mattock1: what for exactly ?
(12:48:32) mattock: OpenVPN I assume
(12:48:46) ordex: ah "they"
(12:49:12) mattock: so operator foundation is working on this stuff
(12:49:16) ordex: ah ok
(12:49:26) ordex: tthen yeah, it's related to the jigsaw project
(12:49:41) ordex: that I am trying to get merged
(12:49:48) mattock: yeah
(12:50:13) mattock: so things seem to be moving forward there, which is good
(12:50:13) ordex: okok
(12:50:30) mattock: so, speaking of progress
(12:50:41) mattock: anything we should/can discuss regarding openvpn 2.5?
(12:51:09) syzzer: not from my side
(12:53:09) ordex: I briefly discussed with dazo how to change the makefile to fix the t_net.sh issue we have now in master
(12:53:21) ordex: so I should fix that soon after I try it locally
(12:53:47) mattock: ok good!
(12:53:49) dazo: I'll be available to help out there anytime
(12:54:09) ordex: ok!
(12:54:36) ordex: cron2 also merged most of the sitnl patches, and he commented on something, so I will try to wrap those changes in a new patch after I fix the Makefile
(12:55:31) dazo: I'm hoping to get a chance to complete the review of the auth-token-hmac patches as well in coming days
(12:56:37) dazo: I've tested them fairly thoroughly and it works as expected.  But will need to run a few extra tests using auth-plugins (only tested with --auth-user-pass-verify so far)
(12:57:55) dazo: But user/pass auth testing is growing in complexity, as we have quite a few ways how to do that now ... and I still haven't really thought about how to test the same features using the management interface
(13:01:06) mattock: how do we test that now?
(13:01:13) mattock: "stare with eye" only?
(13:02:13) dazo: I have some test scripts ... and for the new features plaisthos introduces, I need to write a simple auth-plugin .... management interface is mostly untested from community side, but it is used by the Access Server
(13:02:43) mattock: plus openvpn-gui etc
(13:03:07) dazo: yeah, but not for server side user authentication
(13:03:39) mattock: yeah
(13:04:09) mattock: do we have any tests in openvpn 2 for testing the management interface?
(13:04:27) mattock: or "testing things by using the management interface"
(13:04:42) dazo: I've done sporadic tests using the management interface manually
(13:04:54) dazo: but nothing consistent or automated
(13:05:10) ordex: I don't think we have any script testing that
(13:05:46) mattock: would be "nice to have"
(13:05:56) dazo: yeah
(13:07:11) mattock: anything else on 2.5/testing?
(13:08:51) ordex: not on my side
(13:09:01) mattock: any other topics?
(13:12:40) ordex: maybe not ? :D
(13:13:22) mattock: sounds good :)
(13:13:48) syzzer: well, lunch time then :)
(13:13:52) dazo: :)
(13:14:01) mattock: enjoy, I already ate :)
(13:14:11) mattock: thursday next week then

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-05 11:55 [Openvpn-devel] Community meetings in June 2019 
  2019-06-06 19:10 ` [Openvpn-devel] Summary of the community meeting (6th June 2019) 
  2019-06-12 10:16 ` [Openvpn-devel] Summary of the community meeting (12th " 
@ 2019-06-20 19:14 ` 
  2019-06-21 15:59   ` Simon Rozman
  2019-06-26 11:05 ` [Openvpn-devel] Summary of the community meeting (26th " 
  3 siblings, 1 reply; 12+ messages in thread
From:  @ 2019-06-20 19:14 UTC (permalink / raw)
  To: openvpn-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 2827 bytes --]

Hi,

Here's the summary of the IRC meeting.

---

COMMUNITY MEETING

Place: #openvpn-meeting on irc.freenode.net
Date: Thursday 20th June 2019
Time: 20:00 CEST (18:00 UTC)

Planned meeting topics for this meeting were here:

<https://community.openvpn.net/openvpn/wiki/Topics-2019-06-20>

Your local meeting time is easy to check from services such as

<http://www.timeanddate.com/worldclock>

SUMMARY

cron2, dazo, mattock, ordex and zx2c4 participated in this meeting.

---

Mattock gave an update on tap-windows6 HLK testing. All but two tests
are now passing. Those two tests, namely "Operate in Server Core" and
"Static Tools Logo Test", have known solutions. If nothing jumps out of
the Pandora's box at the last minute, mattock is 90% confident he can
push out a release late next week. He will have to build a new version
of tap-windows6 and run through the whole test suite again, which takes
some days.

It was agreed to HLK-test and release Git "master" version of
tap-windows6. Version number will be 9.24.1.

It was also agreed to build a special version of tap-windows6 with Lev's
patch and sign it for Windows 10 (attestation signature):

<https://github.com/OpenVPN/tap-windows6/pull/86>

Once that build has seen enough testing Lev's patch can be merged and
released in an official installer.

---

Had a heated discussion about public portrayal of OpenVPN on the
Wireguard website, and vice versa. No resolution was reached.

---

Talked about dropping the cmocka git submodule from the OpenVPN
repository. It was useful in the past when cmocka was not so easily
available in the distributions. Now it has become a source of problems.

It was agreed to switch to using system-wide cmocka. Cron2 will do the
make/configure work and promised to pester dazo in the process.

Cmocka will be installed system-wide on all the buildslaves. Pretty much
any version of cmocka should do.

---

Talked about the missing Windows "buildslave". The old one has been gone
for about a year. It was agreed that reviving it makes sense. Mattock
agreed to do it "after HLK".

Also noted that it is possible to make Travis-CI send emails of build
failures by logging into there with one's personal GitHub credentials
and changing the settings. It would also be possible to repurpose
Travis-CI to build, with openvpn-build, on every commit to OpenVPN's Git
repository.

---

Noted that mattock and cron2 will be rather unavailable in tomorrow's
mini-hackathon due to vacations/public holidays.

---

Noted that the ARM64 Windows laptops have not arrived yet. Mattock poked
Microsoft about them during the meeting.

--

Full chatlog attached.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock


[-- Attachment #1.1.2: openvpn_irc_meeting_chatlog_2019-06-20.txt --]
[-- Type: text/plain, Size: 23178 bytes --]

(21:00:37) mattock: good evening
(21:01:24) mattock: https://community.openvpn.net/openvpn/wiki/Topics-2019-06-20
(21:01:25) vpnHelper: Title: Topics-2019-06-20 – OpenVPN Community (at community.openvpn.net)
(21:02:11) dazo: Hey!
(21:02:54) mattock: I assume my latest tap-windows6 update ended up on the mailing list?
(21:02:56) dazo ha scelto come argomento: Next meeting 26/June/2019 at 11:30 CEST.  Agenda at https://community.openvpn.net/openvpn/wiki/Topics-2019-06-20
(21:03:04) dazo: mattock2: yes
(21:03:05) ordex: hi!
(21:03:14) mattock: so only two tests remaining, and both have known solutions
(21:03:24) mattock: which take some time to resolve, but it is only work
(21:03:39) cron2: I am here!
(21:03:42) mattock: hi!
(21:03:51) dazo: o/
(21:04:13) dazo: mattock2: so, what else can jump out of pandora's box once these issues are resolved?
(21:04:24) mattock: your guess is as good as mine :)
(21:04:41) mattock: but I don't expect any new issues at this point
(21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is
(21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes
(21:05:24) mattock: yet
(21:05:32) mattock: so I am hopeful
(21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores
(21:07:23) mattock: but this is all very anecdotal and nobody knows what happens except by trying things out
(21:07:57) mattock: if there are none of these issues I'm 90% confident I can push out a release late next week
(21:08:58) mattock: I will need to double-check what exact variant of tap-windows6 I was testing again though
(21:09:19) dazo: please make sure it's the latest and greatest with Lev's fixes ;-)
(21:10:33) mattock: I'm fine with that
(21:10:48) cron2: we've briefly discussed this this afternoon, and since we do not know exactly what side effects Lev's fixes have (good or bad) we want to do "master without" and then a test build with Lev's fix and Win10 signature (attestation), so it can get proper testing
(21:10:50) mattock: then there's the PR from Simon which should resolve the Static Tools Logo Test
(21:11:00) cron2: *yawn* that has been merged ages ago
(21:11:10) cron2: like, 2 minutes :)
(21:11:17) mattock: oh :)
(21:11:17) dazo: :-P
(21:11:21) mattock: I'm so slow
(21:11:39) cron2: that's because you're only mattock2... mattock1 is much quicker :-)
(21:11:46) ordex: lol
(21:12:20) mattock: I should be mattock or mattock1, but whatever :)
(21:12:32) mattock: so "HLK test latest Git master"
(21:12:39) cron2: I would welcome back the old mattock! :-)
(21:13:00) cron2: mattock2: plus a version.m4 bump
(21:13:13) mattock: "build latest master with lev's patch (PR#86) and sign for Windows 10"
(21:13:16) mattock: and that yes
(21:13:19) cron2: yes
(21:13:20) mattock: 9.24.1
(21:13:38) ***cron2 anticipates an enormous HLK happiness cake
(21:13:49) mattock: tomorrow is midsummer eve so I won't be working much
(21:14:00) mattock: so expect stuff to happen starting next week
(21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit
(21:14:50) cron2: \o/
(21:15:04) mattock: it took like 10 minutes :)
(21:15:09) mattock: not sure why I had avoided it
(21:15:14) cron2: you could use wireguard... I'm told by people all the time that it's so much faster!! and easier to set up!!!!
(21:15:27) cron2: (and has better crypto as well)
(21:15:44) mattock: well I did have a CA, existing server, existing config, etc. :)
(21:15:50) mattock: anyways, enough of tap-windows6!
(21:15:52) cron2: :)
(21:15:53) zx2c4: is that the kind of sarcastic antagonism you really want to display in public cron2?
(21:16:04) mattock: I've worked for 9 hours in a row in HLK today
(21:16:24) cron2: zx2c4: this is what people keep telling me, and everyone else. It's even on the wireguard website.
(21:17:11) mattock: maybe when I'm done with HLK I can finally do some interesting things, including testing Wireguard
(21:17:17) mattock: and let's not get derailed, shall we
(21:17:20) zx2c4: note that we've worked for months and months on making wintun good, and on making it standalone so that you guys can get performance benefits. to date, i've mostly only received antagonistic corporate puff pieces ( https://openvpn.net/vpn-myths-wireguard-vs-openvpn/ ) and other hostilities from you all
(21:17:53) zx2c4: meanwhile i continue to assist with making openvpn faster. i've even contributed patches to you all to add features to it's certificate fingerprint mechanism
(21:18:13) zx2c4: so i kindly ask that you put away your antagonism, put aside the sarcasm, and show us the respect we're owed
(21:18:26) zx2c4: probably that should begin with dazo taking down that ridiculous article
(21:18:28) cron2: zx2c4: you are very gracious.  Did you notice that the wireguard web site still is full of negative remarks about OpenVPN?
(21:18:55) dazo: zx2c4: and lots of those negative OpenVPN remarks aren't even correct
(21:19:18) zx2c4: ahhh so you want to compare in a "tit-for-tat" basis. i see. in that case, it seems you do indeed want some sort of PR war?
(21:19:21) zx2c4: good luck guys!
(21:19:44) zx2c4: way to antagonize somebody wanting to work with you
(21:19:45) cron2: zx2c4: I'm not the one who needs to justify their own product by telling everyone how bad the *other* products are.  You started that.
(21:20:00) cron2: zx2c4: *you* put up the wireguard.net webpage.  That wasn't us.
(21:20:09) ordex: zx2c4: you should know that cron2 has no clue what "PR war" you're talking about
(21:20:13) cron2: so don't talk about "antagonizing someone"
(21:20:23) zx2c4: um... im pretty sure i didnt put the 0days in openvpn
(21:20:32) zx2c4: anyway, good luck
(21:20:37) zx2c4: it's going to be interesting...
(21:20:50) mattock: this discussion is so not going to get anywhere
(21:20:51) cron2: I'm not saying openvpn is good code, or bug-free.  Or that it is *not* bloated.
(21:21:18) zx2c4: justifying your further antagonism will only make all of your projects worse, let me assure you
(21:21:34) cron2: but it's something else if you say that about your own responsibilities (even if only inherited), instead of about someone else
(21:21:58) zx2c4: if you'd like to approach me with an aim at reconciliation, by all means, please do so. otherwise i'll continue preparing for the war path you're trotting 
(21:22:00) cron2: zx2c4: so, maybe YOU should just stop it.  Look on wireguard.net what it says about OpenVPN.  Nothing of this needs to be there.  This is not nice.
(21:22:20) dazo: zx2c4: and FTR ... the blog post URL you pointed at is no longer correct; the correct one (which it also redirect to now) is: https://openvpn.net/what-is-cloudflare-vpn/
(21:22:29) cron2: zx2c4: oh, please.  We're not the ones who started this badmouthing.
(21:22:47) zx2c4: dazo: still flawed and antagonistic as prior
(21:23:05) cron2: zx2c4: have you looked at wireguard.net today?  Start with your own side.
(21:23:08) zx2c4: anyway cron2 here has confirmed to me the openvpn inc position: that you really are engaged in a tit-for-tat dynamic, contrary to dazo's tone before
(21:23:13) cron2: I AM NOT OPENVPN INC
(21:23:14) ordex: can we continue the meeting? there are 10 minutes left ..
(21:23:20) cron2: get your facts straight, please
(21:23:33) zx2c4: a representative of the openvpn project then?
(21:23:42) ordex: zx2c4: I said this above - he has no clue what war you're talking about - he is totally unrelated to the inc.
(21:23:44) zx2c4: you all seem to share the same koolaid it appears
(21:24:08) cron2: zx2c4: yes.  A volunteer mainting openvpn 2.x code base to the best of my abilities, and we are not deserving the bad mouthing you spread on your website
(21:24:23) zx2c4: ordex: i see. well, it'd be in the inc's interest, then, to lower it's antagonism, so that this kind of thing doesn't spill over to goodfolk like cron2 then?
(21:24:39) ordex: zx2c4: dunno - talk to openvpn inc. for that
(21:24:42) dazo: let's get back on the agenda
(21:24:48) ordex: can we continue the meeting now ? we don't much free time  ...
(21:24:49) zx2c4: dazo's in here now, mostly ignoring things
(21:24:50) cron2: zx2c4: it would be in wireguard's interest to stop the badmouthing of other projects, so the antagonism doesn't spill
(21:24:56) cron2: ordex: we have 36 minutes left :-)
(21:25:01) ordex: zx2c4: becuse this was meant to be a FOSS meeting
(21:25:05) ordex: cron2: oh right :D sorry
(21:25:19) mattock: +1 on stopping this discussion
(21:25:21) mattock: and moving on
(21:25:23) zx2c4: ordex: well, i hang out here so that i can *help* with the foss aspects
(21:25:32) zx2c4: then i log in and i see antgaonistic words
(21:25:34) cron2: ordex: but you are certainly right, it is not on the agenda, so I'm not going to speak nice words about wireguard anymore :-)
(21:25:50) ordex: zx2c4: sure, but now you hijacked 15 minutes of our free time just because you assumed cron2 was making sarcasm
(21:25:53) zx2c4: so let's put it this way: do you want wintun to work for you all, or not?
(21:26:11) ordex: not sure what that question means (?) maybe it's me
(21:26:15) zx2c4: if you want cooperation, show some respect.
(21:26:18) mattock: please, let us stop here
(21:26:23) ordex: yeah
(21:26:24) mattock: this is not going anywhere
(21:26:41) zx2c4: so, time to show respect then?
(21:26:41) mattock: #2 can we drop the cmocka sub-module
(21:26:59) ordex: mattock2: yeah, we should update all the build slaves to have it installed system wide
(21:27:14) ordex: right now centos6 is for sure one needing it
(21:27:17) cron2: well, the short summary for the sake of the archive is:
(21:27:31) cron2: we have the git submodule for cmocka because "back then" distributions did not have it
(21:27:45) ordex: right and centos is still among them (it seems)
(21:27:47) cron2: with the current way cmocka works, t_net.sh fails because LD_LIBRARY_PATH
(21:28:07) cron2: getting this fixed with sudo etc. across distributions is lots of work
(21:28:10) mattock: did we check which of the current buildslaves operating systems have cmocka available as a package? or do we plan to install it from source?
(21:28:17) cron2: my proposal is:
(21:28:22) dazo: I see libcmocka available in Fedora EPEL for RHEL/CentOS
(21:28:26) cron2:  - document how to get cmocka from git & install it
(21:28:27) dazo: even RHEL6
(21:28:35) cron2:  - get rid of all our build logic for cmocka
(21:28:37) dazo: not sure about Debian though
(21:28:44) ordex: dazo: I think centos6 does not have it, does it ?
(21:28:53) cron2:  - instead have configure check for its existance (as it deos for cmake today) and "if there, run unit tests, if not, not"
(21:29:12) ordex: +1
(21:29:27) dazo: ordex: It is in EPEL 6 repos too
(21:29:27) cron2: even on those systems that do not have cmocka, installing it by means of "git clone & make & make install" is easier than continuously working around the submodule issues
(21:29:28) mattock: sounds very reasonable
(21:29:39) ordex: yap
(21:30:45) mattock: who does the makefile/configure magic?
(21:30:53) cron2: I'm sure I'm going to regret this... but I'm going to take this - change configure.ac accordingly and figure out how to make it behave
(21:31:08) cron2: and pester dazo with questions :)
(21:31:54) mattock: sounds like a plan!
(21:32:00) dazo: works for me :)
(21:32:27) cron2: the cmocka installation instructiosn would then go to INSTALL, next to the "make check" section?
(21:33:49) ordex: but didn't we say that configure.ac already checks for cmocka ?
(21:33:55) ordex: or it does not check for the system-wide lib ?
(21:34:01) dazo: cron2: something like that
(21:34:17) dazo: ordex: it only checks for the local git submodule, iirc
(21:34:19) cron2: ordex: right now it checks for cmake, and if cmake is found *and* the git submodule is initted, it will build cmocka
(21:34:50) cron2: I have the feelign the logic is going to get easier :)
(21:34:57) ordex: right, but if no cmocka submobule is there, but it is found on the system, unit-tests are still built, I think ?
(21:35:03) cron2: no
(21:35:10) cron2: right now we totally ignore system-wide cmocka
(21:35:18) cron2: (except that it happens to make t_net.sh work by chance)
(21:35:19) ordex: oh ok
(21:35:27) dazo: what cron2 say
(21:35:28) dazo: s
(21:36:16) cron2: commit 45f6e7991cfa3bb8a44f981b6cf1e794d617d51e
(21:36:17) cron2: Author: David Sommerseth <dazo@...2511...m>
(21:36:21) cron2:     Only build and run cmocka unit tests if its submodule is initialized
(21:36:27) cron2: so, again, it's all dazo's fault :-)
(21:36:37) ordex: :D
(21:36:41) cron2: (we need vpn-helper in here... :) )
(21:37:03) cron2: so - I think cmocka is covered, I have work to do.  Maybe this weekend, still on vacation with the kids
(21:37:10) cron2: 3. windows buildslave...
(21:37:19) dazo: but!  We should double check if that's clever or not btw .... I implemented googletest in openvpn3-linux for unit-testing, and based it on system wide libraries in the beginning; but googletest project recommends *not* doing that, as compiler flags and optimization may make debugging harder - as some code paths may be optimized differently - causing things to explode in a debugger or so
(21:37:50) dazo: (it was a fairly descriptive information about this issue on some googletest pages)
(21:38:18) dazo: *but* that may be due to how C++ compilers work; not sure if the same issues happens with C compilers
(21:38:44) cron2: well... I have seen that samba relies on system-wide cmocka... and they usually know why they bundle things and not-bundle others
(21:38:50) dazo: however, I do know that openvpn3-linux is hard to debug on Ubuntu if the -O compiler flag is different from what the system library uses
(21:38:51) cron2: (this is how cmocka ended up on my gentoo system)
(21:39:20) dazo: yeah, but on Gentoo, the compiler flags are usually identical when you pull things in via emerge, no?
(21:39:22) cron2: dazo: this sounds very much like a C++ issue and I do not want to even think about these complications :-)
(21:39:32) dazo: hehehe
(21:39:45) cron2: dazo: well, optimization flags, not sure.  -m$arch, yes
(21:41:21) cron2: I'm not sure cmocka really does that much interesting stuff for C programs, though :-)
(21:41:28) dazo: anyway, lets try ... and we'll see what happens.  Worst thing which happens is that we rollback again
(21:41:37) cron2: "build, link, run test, spare lots of work in setting these all up"
(21:41:37) ordex: yap
(21:41:42) cron2: yeah
(21:42:16) dazo: cmocka stuff isn't production critical at all, so it doesn't need to hold back any releases
(21:42:40) cron2: this would only go to master anyway - 2.4 works nicely as it is, the t_net problems are only in master
(21:42:55) dazo: yeah, but we have a hopefully coming 2.5 release ;-)
(21:42:59) cron2: if we decide that this is really much nicer, it can be backported, of course
(21:43:20) dazo: yeah
(21:43:32) cron2: dazo: well, it is actually annoying enough that I do not want to push anything else before this is fixed :-) - like, 20 buildbot fails on every push
(21:43:57) ordex: yeah
(21:44:02) dazo: that's understandable, indeed :)
(21:44:18) ordex: my latets patch for t_net.sh assumes this will be fixed and it does not try to address the issue anymore
(21:44:22) ordex: *latest
(21:45:23) dazo: I actually started reviewing that patch though
(21:46:32) ordex: yap - it can be merged, but then we have the Nth wave of mails from buildbot
(21:46:51) dazo: :)
(21:47:09) cron2: we can install cmocka on all affected buildbots in the meantime, though :-)
(21:47:22) cron2: ordex: do you have a list?  I threw away all the mails in annoyance :)
(21:47:24) mattock: how picky is cmocka about versions?
(21:47:35) mattock: "almost any version is good"?
(21:47:40) cron2: seems "not at all", all of them have a libcmocka.so.0
(21:47:45) cron2: and that seems to work nicely
(21:47:48) mattock: ok
(21:47:49) mattock: good
(21:47:54) ordex: cron2: same here, but I could build my branch again :D
(21:48:13) cron2: I'll just merge your patch and push
(21:48:48) cron2: dazo: I've reviewed v1 already, which was mostly the same except "plus LD_LIBRARY_PATH", so I can just ack+push
(21:48:50) ordex: ok
(21:48:56) ordex: yap
(21:49:04) cron2: or maybe not, see #openvpn-devel
(21:49:38) mattock: 11 minutes left, two more topics
(21:49:41) mattock: hint hint
(21:49:44) mattock: :)
(21:49:54) cron2: well, I thought we were at "3" already anyway :-)
(21:50:05) mattock: that's quick
(21:50:08) cron2: there used to be a windows buildslave which sends me mail if I break windows compilation
(21:50:17) mattock: "yes, it has been gone for a year, and nobody cared or noticed"
(21:50:19) cron2: and which used to put up snapshot installers...
(21:50:31) cron2: I did care, and I think I remarked a few times...
(21:50:58) mattock: yeah, I agree, but it is interesting that nobody (afaik) complained about the installers
(21:51:01) cron2: I had forgotten again, but when I broke windows like 10 commits ago, nobody noticed which is sad
(21:51:06) mattock: yeah
(21:51:14) cron2: so - is it easy to revive it?
(21:51:26) mattock: I wonder if we could repurpose travis to build the installers - openvpn-build repo already does it
(21:51:45) ordex: cron2: we have travis (and I have gitlab-ci) that build for windows and create binaries
(21:52:11) ordex: mattock2: to build the installers you need openvpn-build, no? from openvpn you ca nonly build the binary I guess
(21:52:12) ordex: ?
(21:52:22) cron2: well, travis does send mails now, but they are much less good than mattock's build mails
(21:52:32) mattock: I take that as a complement
(21:52:34) mattock: :)
(21:52:41) cron2: ("it fails, please go and click on $URL to see why")
(21:52:57) cron2: mattock2: I like one-stop problem reports.  "It failed, and here is the output: <blah>"
(21:53:00) mattock: well, assuming nothing has broken in the meanwhile reviving the buildslave should not be that big a deal 
(21:53:14) mattock: and if we're content with the functionality it used to have
(21:53:15) cron2: pretty please? ;-)
(21:53:23) mattock: "after HLK" :)
(21:53:31) cron2: *I* found it very useful
(21:53:49) mattock: noted :)
(21:54:06) mattock: so travis-ci: is there a way to receive email reports?
(21:54:14) cron2: so - after HLK is perfectly fine.  Until then, I need to review more carefully and if it looks like dangerous, run my own tests
(21:54:32) ordex: mattock2: yap, cron2 enabled that recently for himself
(21:54:54) cron2: travis-ci: we found that it can send mails - if you login with your github credentials to travis-ci, you can set in your *personal* profile that you want to receive build failure mails
(21:55:01) cron2: not in the project settings
(21:55:29) cron2: and not much to customize - so you get a mail "it failed! see $URL for why!", but it's better than "not noticing"
(21:55:51) cron2: this much for the archives - question for the group: is there more options?  Who understands travis-ci?
(21:56:27) ordex: what do you mean with "more options?" I have played with it a bit, I may be able to answer some questions
(21:56:52) cron2: like, more fine grained control on e-mail - when does it send a mail, what is in there
(21:57:54) ordex: ah  - no :) that I never found how to customize
(21:58:02) ordex: it's just a failure and then you are redirected to the job page
(21:58:33) cron2: well, good enough for today
(21:58:42) cron2: 2.5 update/planning
(21:59:04) mattock: +1
(21:59:18) cron2: mini-hackathon tomorrow?  I cannot make it (last day on the vacation resort, we have to checkout at 10 but can stay until afternoon, so laptop will be in the car and I will be at the pool...)
(21:59:56) dazo: sounds like the proper priority ;-)
(22:00:00) cron2: but you do not need me for review & ACK & new versions of some patches... I can pick up the stuff from there
(22:00:08) ordex: yap
(22:00:19) cron2: yeah, work has been... special this year, so family needed priority for a week
(22:00:40) mattock: I will be quite unavailable tomorrow due to the midsummer eve thingy
(22:00:56) ordex: mattock2: what is that about ?
(22:01:15) mattock: generally speaking people drink too much, go to sauna, go swimming and drown
(22:01:19) mattock: :)
(22:01:24) cron2: ordex: something like "dancing naked in the woods" or so
(22:01:29) ordex: LOL
(22:01:29) mattock: and that occasionally
(22:01:41) ordex: mattock2: so if you drink tomorrow you die ?
(22:01:45) ordex: :D
(22:01:47) mattock: there's the yearly dead by drowning count which people try to guess
(22:01:49) ordex: what a chain of events !!
(22:01:49) mattock: I won't
(22:01:58) ordex: on this day ?
(22:02:01) cron2: mattock2: ouch
(22:02:09) mattock: usually it extends to the weekend
(22:02:18) mattock: but the mayhem starts tomorrow
(22:02:37) mattock: I will be on small family trip, so I'm good
(22:02:58) mattock: :D
(22:03:18) mattock: are we good for today?
(22:03:20) cron2: I wish you a nice day full of family enjoyment, naked or drunk, or neither :)
(22:03:26) mattock: thank you!
(22:03:26) cron2: but please do not drown
(22:03:36) mattock: yeah, we still need to HLK test result packages!
(22:03:53) mattock: otherwise some poor sould (which is probably dazo) will take over that task
(22:03:55) mattock: :D
(22:04:03) cron2: and document the whole chore :-) - after that, you're free...
(22:04:15) mattock: it is almost completely documented: https://community.openvpn.net/openvpn/wiki/HLKTesting
(22:04:17) vpnHelper: Title: HLKTesting – OpenVPN Community (at community.openvpn.net)
(22:04:28) mattock: some anecdotes are missing
(22:05:11) mattock: ok, let's conclude this, I have the summayr ready
(22:05:21) dazo: leave the sad ones, only add the fun ones :-P
(22:05:42) cron2: there is fun in WLK testing?  well, the cake, obviously...
(22:05:48) cron2: (have the arm64 laptops arrived?)
(22:05:53) cron2: ((where is plaisthos anyway??))
(22:06:05) mattock: no, I have not seen any arm64 laptops
(22:06:09) cron2: (((and what about this new patch set...?)))
(22:06:10) mattock: I may need to poke them again
(22:06:34) dazo: cron2: on holiday, north in DE, hopefully surviving water kiting and sun
(22:06:59) cron2: dazo: ah... so hopefully, v4 of his token patchset survives your scrutiny now...
(22:07:20) dazo: hopefully :)  I'll try to get the rest reviewed tomorrow so we can get everything at once
(22:09:33) mattock: I poked them about the ARM64 device
(22:10:28) mattock: I'll send the summary now and then head home

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-20 19:14 ` [Openvpn-devel] Summary of the community meeting (20th " 
@ 2019-06-21 15:59   ` Simon Rozman
  2019-06-24 11:33     ` 
  0 siblings, 1 reply; 12+ messages in thread
From: Simon Rozman @ 2019-06-21 15:59 UTC (permalink / raw)


[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]

(21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is
(21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes

1. Do the SDV and DVL to get tap901.DVL.xml.
2. Compile the driver and EV sign it. Save PDBs too.
3. Deploy the driver on test computers (including tap901.DVL.xml, remember?).
4. Do the WHLK.
5. When creating submission package, add the driver binaries and PDBs (on HLK Studio submission page).
6. Submit the driver to Microsoft WHQL.
7. Miscrosoft should return you a WHQL signed driver in about 10 minutes.

(21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores

Microsoft is fine with that test being run on a virtual Windows Server 2019 Core in Wintun case. And this test is pretty straight forward - just checks that driver loads and adapter responds, it doesn't need to be connected and have traffic. Use devcon to make a single TAP adapter on the Server Core. No need to have a running OpenVPN connection for this test to pass.

(21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit

Not a good idea, as WHLK tests can and will interfere with all TAP-Windows6 adapters on test computers. Not just the one that is being tested. Expect OpenVPN connections to flicker or die. Just use it to access controller server only. I never experienced any issues requiring intervention on test computers.

Best regards,
Simon

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2965 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-21 15:59   ` Simon Rozman
@ 2019-06-24 11:33     ` 
  2019-06-24 18:13       ` 
  0 siblings, 1 reply; 12+ messages in thread
From:  @ 2019-06-24 11:33 UTC (permalink / raw)
  To: Simon Rozman <simon@

Hi Simon,

Thanks for the info again!

Il 21/06/19 18:59, Simon Rozman ha scritto:
> (21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is
> (21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes
> 
> 1. Do the SDV and DVL to get tap901.DVL.xml.

I'm working on this right now. Based on brief practical testing EWDK may
not be able to do this, even though it is apparently possible to produce
SDV logs from the command-line:

https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier

It _seems_ that EWDK might not have all the necessary pieces for
producing SDV log files. MS does briefly mention that EWDK is not
suitable for doing driver testing, whatever that means. So, to play it
safe, I'm installing Visual Studio 2019 plus the "normal" Windows Driver
Kit on my tapbuilder VM.

> 2. Compile the driver and EV sign it. Save PDBs too.

I assume this is not really necessary if I'm using WDKTest certificates
and have enabled test-signing?

> 3. Deploy the driver on test computers (including tap901.DVL.xml, remember?).
> 4. Do the WHLK.
> 5. When creating submission package, add the driver binaries and PDBs (on HLK Studio submission page).
> 6. Submit the driver to Microsoft WHQL.
> 7. Miscrosoft should return you a WHQL signed driver in about 10 minutes.
> 
> (21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores
> 
> Microsoft is fine with that test being run on a virtual Windows Server 2019 Core in Wintun case. And this test is pretty straight forward - just checks that driver loads and adapter responds, it doesn't need to be connected and have traffic. Use devcon to make a single TAP adapter on the Server Core. No need to have a running OpenVPN connection for this test to pass.

This is good news. I can just use a Virtualbox VM then. This test used
to pass even on EC2 Windows instances.

> (21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit
> 
> Not a good idea, as WHLK tests can and will interfere with all TAP-Windows6 adapters on test computers. Not just the one that is being tested. Expect OpenVPN connections to flicker or die. Just use it to access controller server only. I never experienced any issues requiring intervention on test computers.

The OpenVPN client I'm talking about is installed on a Linux laptop that
works as a Virtualbox host. The HLK controller is a VM on that host.
None of the HLK computers know about its existence.

The HLK test client and support machine do have OpenVPN setup, but that
is a completely separate p2p bridged setup used to allow the two-machine
NDIS tests pass. And it works well for that purpose.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

> 
> Best regards,
> Simon
> 




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-24 11:33     ` 
@ 2019-06-24 18:13       ` 
  2019-06-24 20:24         ` 
  2019-06-25  8:55         ` 
  0 siblings, 2 replies; 12+ messages in thread
From:  @ 2019-06-24 18:13 UTC (permalink / raw)
  To: Simon Rozman <simon@

Hi,

Il 24/06/19 14:33, Samuli Seppänen ha scritto:
> Hi Simon,
> 
> Thanks for the info again!
> 
> Il 21/06/19 18:59, Simon Rozman ha scritto:
>> (21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is
>> (21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes
>>
>> 1. Do the SDV and DVL to get tap901.DVL.xml.
> 
> I'm working on this right now. Based on brief practical testing EWDK may
> not be able to do this, even though it is apparently possible to produce
> SDV logs from the command-line:>
> https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier
> 
> It _seems_ that EWDK might not have all the necessary pieces for
> producing SDV log files. MS does briefly mention that EWDK is not
> suitable for doing driver testing, whatever that means. So, to play it

Actually it is probably possible to use the EWDK for running Static
Driver Verifier:

<https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/develop/creating-a-driver-verification-log.md>
<https://docs.microsoft.com/it-it/windows-hardware/drivers/devtest/static-driver-verifier>

> safe, I'm installing Visual Studio 2019 plus the "normal" Windows Driver
> Kit on my tapbuilder VM.

So, I took a stab at producing the Static Driver Verifier logs in Visual
Studio 2019 ("Extensions" -> "Static Driver Verifier"), but it just
complains about

"Please select a driver project for sdv to verify"

I wonder if I just hit a usability problem, or if something is actually
missing from tap-windows6?

Attempting to run SDV from the command-line (adapted from first link
above) fails as well. The /clean part works fine, but running SDV fails:

PS> msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
/p:Platform=x64 /target:sdv /p:inputs="/clean"

--- snip ---

PS> msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
/p:Platform=x64 /target:sdv /p:inputs="/check:default.sdv"

  [INFO] Validating XML against schema: C:\Program Files (x86)\Windows
Kits\10\TOOLS\SDV\smv\bin\Config.xsd
  [INFO] Running local scheduler with 2 threads
  [FATAL ERROR] Unrecoverable error in NormalBuild stage.
C:\Program Files (x86)\Windows
Kits\10\build\windowsdriver.Sdv.targets(136,9): error MSB3073: The
command "staticdv /ch
eck:default.sdv" exited with code -1.
[C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj]
Done Building Project
"C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj" (sdv
target(s)) -- FAILED.


Build FAILED.

"C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj" (sdv target)
(1) ->
(sdv target) ->
  C:\Program Files (x86)\Windows
Kits\10\build\windowsdriver.Sdv.targets(136,9): error MSB3073: The
command "staticdv /
check:default.sdv" exited with code -1.
[C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:02.65

---

Am I missing something [that is obvious to a Windows developer]?

Samuli

[*] Adapting the instructions of the first link, above

> 
>> 2. Compile the driver and EV sign it. Save PDBs too.
> 
> I assume this is not really necessary if I'm using WDKTest certificates
> and have enabled test-signing?
> 
>> 3. Deploy the driver on test computers (including tap901.DVL.xml, remember?).
>> 4. Do the WHLK.
>> 5. When creating submission package, add the driver binaries and PDBs (on HLK Studio submission page).
>> 6. Submit the driver to Microsoft WHQL.
>> 7. Miscrosoft should return you a WHQL signed driver in about 10 minutes.
>>
>> (21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores
>>
>> Microsoft is fine with that test being run on a virtual Windows Server 2019 Core in Wintun case. And this test is pretty straight forward - just checks that driver loads and adapter responds, it doesn't need to be connected and have traffic. Use devcon to make a single TAP adapter on the Server Core. No need to have a running OpenVPN connection for this test to pass.
> 
> This is good news. I can just use a Virtualbox VM then. This test used
> to pass even on EC2 Windows instances.
> 
>> (21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit
>>
>> Not a good idea, as WHLK tests can and will interfere with all TAP-Windows6 adapters on test computers. Not just the one that is being tested. Expect OpenVPN connections to flicker or die. Just use it to access controller server only. I never experienced any issues requiring intervention on test computers.
> 
> The OpenVPN client I'm talking about is installed on a Linux laptop that
> works as a Virtualbox host. The HLK controller is a VM on that host.
> None of the HLK computers know about its existence.
> 
> The HLK test client and support machine do have OpenVPN setup, but that
> is a completely separate p2p bridged setup used to allow the two-machine
> NDIS tests pass. And it works well for that purpose.
> 



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-24 18:13       ` 
@ 2019-06-24 20:24         ` 
  2019-06-25  8:55         ` 
  1 sibling, 0 replies; 12+ messages in thread
From:  @ 2019-06-24 20:24 UTC (permalink / raw)
  Cc: Simon Rozman <simon@

[-- Attachment #1: Type: text/plain, Size: 6255 bytes --]

пн, 24 июн. 2019 г. в 23:14, Samuli Seppänen <samuli@...515...>:

> Hi,
>
> Il 24/06/19 14:33, Samuli Seppänen ha scritto:
> > Hi Simon,
> >
> > Thanks for the info again!
> >
> > Il 21/06/19 18:59, Simon Rozman ha scritto:
> >> (21:04:58) mattock: assuming Microsoft's systems are happy with the
> test submission package, that is
> >> (21:05:12) mattock: they _should_ be, but we have not tested submitting
> anything yes
> >>
> >> 1. Do the SDV and DVL to get tap901.DVL.xml.
> >
> > I'm working on this right now. Based on brief practical testing EWDK may
> > not be able to do this, even though it is apparently possible to produce
> > SDV logs from the command-line:>
> >
> https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier
> >
> > It _seems_ that EWDK might not have all the necessary pieces for
> > producing SDV log files. MS does briefly mention that EWDK is not
> > suitable for doing driver testing, whatever that means. So, to play it
>
> Actually it is probably possible to use the EWDK for running Static
> Driver Verifier:
>
> <
> https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/develop/creating-a-driver-verification-log.md
> >
> <
> https://docs.microsoft.com/it-it/windows-hardware/drivers/devtest/static-driver-verifier
> >
>
> > safe, I'm installing Visual Studio 2019 plus the "normal" Windows Driver
> > Kit on my tapbuilder VM.
>
> So, I took a stab at producing the Static Driver Verifier logs in Visual
> Studio 2019 ("Extensions" -> "Static Driver Verifier"), but it just
> complains about
>
> "Please select a driver project for sdv to verify"
>
> I wonder if I just hit a usability problem, or if something is actually
> missing from tap-windows6?
>
> Attempting to run SDV from the command-line (adapted from first link
> above) fails as well. The /clean part works fine, but running SDV fails:
>
> PS> msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
> /p:Platform=x64 /target:sdv /p:inputs="/clean"
>
> --- snip ---
>
> PS> msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
> /p:Platform=x64 /target:sdv /p:inputs="/check:default.sdv"
>
>   [INFO] Validating XML against schema: C:\Program Files (x86)\Windows
> Kits\10\TOOLS\SDV\smv\bin\Config.xsd
>   [INFO] Running local scheduler with 2 threads
>   [FATAL ERROR] Unrecoverable error in NormalBuild stage.
> C:\Program Files (x86)\Windows
> Kits\10\build\windowsdriver.Sdv.targets(136,9): error MSB3073: The
> command "staticdv /ch
> eck:default.sdv" exited with code -1.
> [C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj]
> Done Building Project
> "C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj" (sdv
> target(s)) -- FAILED.
>
>
> Build FAILED.
>
> "C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj" (sdv target)
> (1) ->
> (sdv target) ->
>   C:\Program Files (x86)\Windows
> Kits\10\build\windowsdriver.Sdv.targets(136,9): error MSB3073: The
> command "staticdv /
> check:default.sdv" exited with code -1.
> [C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj]
>
>     0 Warning(s)
>     1 Error(s)
>
> Time Elapsed 00:00:02.65
>
> ---
>
> Am I missing something [that is obvious to a Windows developer]?
>

can you try adding /v:d

to the following line

msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
/p:Platform=x64 /target:sdv /p:inputs="/check:default.sdv"

?

(it means verbosity detailed)



>
> Samuli
>
> [*] Adapting the instructions of the first link, above
>
> >
> >> 2. Compile the driver and EV sign it. Save PDBs too.
> >
> > I assume this is not really necessary if I'm using WDKTest certificates
> > and have enabled test-signing?
> >
> >> 3. Deploy the driver on test computers (including tap901.DVL.xml,
> remember?).
> >> 4. Do the WHLK.
> >> 5. When creating submission package, add the driver binaries and PDBs
> (on HLK Studio submission page).
> >> 6. Submit the driver to Microsoft WHQL.
> >> 7. Miscrosoft should return you a WHQL signed driver in about 10
> minutes.
> >>
> >> (21:07:09) mattock: worst case scenario is that I have to reinstall the
> HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the
> "Operate in Server Core" having been run on a virtual machine, or on some
> old i5 laptop which does not have the required 4 physical processor cores
> >>
> >> Microsoft is fine with that test being run on a virtual Windows Server
> 2019 Core in Wintun case. And this test is pretty straight forward - just
> checks that driver loads and adapter responds, it doesn't need to be
> connected and have traffic. Use devcon to make a single TAP adapter on the
> Server Core. No need to have a running OpenVPN connection for this test to
> pass.
> >
> > This is good news. I can just use a Virtualbox VM then. This test used
> > to pass even on EC2 Windows instances.
> >
> >> (21:14:42) mattock: I also finally ate our own dogfood and installer
> OpenVPN on the virtual host running the HLK controller so that I can access
> the HLK controller and clients remotely, which speeds the testing up quite
> a bit
> >>
> >> Not a good idea, as WHLK tests can and will interfere with all
> TAP-Windows6 adapters on test computers. Not just the one that is being
> tested. Expect OpenVPN connections to flicker or die. Just use it to access
> controller server only. I never experienced any issues requiring
> intervention on test computers.
> >
> > The OpenVPN client I'm talking about is installed on a Linux laptop that
> > works as a Virtualbox host. The HLK controller is a VM on that host.
> > None of the HLK computers know about its existence.
> >
> > The HLK test client and support machine do have OpenVPN setup, but that
> > is a completely separate p2p bridged setup used to allow the two-machine
> > NDIS tests pass. And it works well for that purpose.
> >
>
>
>
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>

[-- Attachment #2: Type: text/html, Size: 8107 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-24 18:13       ` 
  2019-06-24 20:24         ` 
@ 2019-06-25  8:55         ` 
  2019-07-04 13:08           ` Simon Rozman
  1 sibling, 1 reply; 12+ messages in thread
From:  @ 2019-06-25  8:55 UTC (permalink / raw)
  To: Simon Rozman <simon@

Hi,

I got the Static Driver Verifier to run with help from Stephen. The
correct (command-line) procedure is now documented here:

<https://community.openvpn.net/openvpn/wiki/HLKTesting#StaticToolsLogoTest>

So it was bad usability after all. The tests are now running and
hopefully I can create the merged test result package from SDV and Code
Analysis today.

Meanwhile I'll make the HLK client work for its money by running the
other tests.

Samuli

Il 24/06/19 21:13, Samuli Seppänen ha scritto:
> Hi,
> 
> Il 24/06/19 14:33, Samuli Seppänen ha scritto:
>> Hi Simon,
>>
>> Thanks for the info again!
>>
>> Il 21/06/19 18:59, Simon Rozman ha scritto:
>>> (21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is
>>> (21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes
>>>
>>> 1. Do the SDV and DVL to get tap901.DVL.xml.
>>
>> I'm working on this right now. Based on brief practical testing EWDK may
>> not be able to do this, even though it is apparently possible to produce
>> SDV logs from the command-line:>
>> https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/creating-a-log-file-for-static-driver-verifier
>>
>> It _seems_ that EWDK might not have all the necessary pieces for
>> producing SDV log files. MS does briefly mention that EWDK is not
>> suitable for doing driver testing, whatever that means. So, to play it
> 
> Actually it is probably possible to use the EWDK for running Static
> Driver Verifier:
> 
> <https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/develop/creating-a-driver-verification-log.md>
> <https://docs.microsoft.com/it-it/windows-hardware/drivers/devtest/static-driver-verifier>
> 
>> safe, I'm installing Visual Studio 2019 plus the "normal" Windows Driver
>> Kit on my tapbuilder VM.
> 
> So, I took a stab at producing the Static Driver Verifier logs in Visual
> Studio 2019 ("Extensions" -> "Static Driver Verifier"), but it just
> complains about
> 
> "Please select a driver project for sdv to verify"
> 
> I wonder if I just hit a usability problem, or if something is actually
> missing from tap-windows6?
> 
> Attempting to run SDV from the command-line (adapted from first link
> above) fails as well. The /clean part works fine, but running SDV fails:
> 
> PS> msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
> /p:Platform=x64 /target:sdv /p:inputs="/clean"
> 
> --- snip ---
> 
> PS> msbuild.exe src\tap-windows6.vcxproj /p:Configuration="Release"
> /p:Platform=x64 /target:sdv /p:inputs="/check:default.sdv"
> 
>   [INFO] Validating XML against schema: C:\Program Files (x86)\Windows
> Kits\10\TOOLS\SDV\smv\bin\Config.xsd
>   [INFO] Running local scheduler with 2 threads
>   [FATAL ERROR] Unrecoverable error in NormalBuild stage.
> C:\Program Files (x86)\Windows
> Kits\10\build\windowsdriver.Sdv.targets(136,9): error MSB3073: The
> command "staticdv /ch
> eck:default.sdv" exited with code -1.
> [C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj]
> Done Building Project
> "C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj" (sdv
> target(s)) -- FAILED.
> 
> 
> Build FAILED.
> 
> "C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj" (sdv target)
> (1) ->
> (sdv target) ->
>   C:\Program Files (x86)\Windows
> Kits\10\build\windowsdriver.Sdv.targets(136,9): error MSB3073: The
> command "staticdv /
> check:default.sdv" exited with code -1.
> [C:\Users\samuli\opt\tap-windows6\src\tap-windows6.vcxproj]
> 
>     0 Warning(s)
>     1 Error(s)
> 
> Time Elapsed 00:00:02.65
> 
> ---
> 
> Am I missing something [that is obvious to a Windows developer]?
> 
> Samuli
> 
> [*] Adapting the instructions of the first link, above
> 
>>
>>> 2. Compile the driver and EV sign it. Save PDBs too.
>>
>> I assume this is not really necessary if I'm using WDKTest certificates
>> and have enabled test-signing?
>>
>>> 3. Deploy the driver on test computers (including tap901.DVL.xml, remember?).
>>> 4. Do the WHLK.
>>> 5. When creating submission package, add the driver binaries and PDBs (on HLK Studio submission page).
>>> 6. Submit the driver to Microsoft WHQL.
>>> 7. Miscrosoft should return you a WHQL signed driver in about 10 minutes.
>>>
>>> (21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores
>>>
>>> Microsoft is fine with that test being run on a virtual Windows Server 2019 Core in Wintun case. And this test is pretty straight forward - just checks that driver loads and adapter responds, it doesn't need to be connected and have traffic. Use devcon to make a single TAP adapter on the Server Core. No need to have a running OpenVPN connection for this test to pass.
>>
>> This is good news. I can just use a Virtualbox VM then. This test used
>> to pass even on EC2 Windows instances.
>>
>>> (21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit
>>>
>>> Not a good idea, as WHLK tests can and will interfere with all TAP-Windows6 adapters on test computers. Not just the one that is being tested. Expect OpenVPN connections to flicker or die. Just use it to access controller server only. I never experienced any issues requiring intervention on test computers.
>>
>> The OpenVPN client I'm talking about is installed on a Linux laptop that
>> works as a Virtualbox host. The HLK controller is a VM on that host.
>> None of the HLK computers know about its existence.
>>
>> The HLK test client and support machine do have OpenVPN setup, but that
>> is a completely separate p2p bridged setup used to allow the two-machine
>> NDIS tests pass. And it works well for that purpose.
>>
> 


-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock


^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Openvpn-devel] Summary of the community meeting (26th June 2019)
  2019-06-05 11:55 [Openvpn-devel] Community meetings in June 2019 
                   ` (2 preceding siblings ...)
  2019-06-20 19:14 ` [Openvpn-devel] Summary of the community meeting (20th " 
@ 2019-06-26 11:05 ` 
  3 siblings, 0 replies; 12+ messages in thread
From:  @ 2019-06-26 11:05 UTC (permalink / raw)
  To: openvpn-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 2596 bytes --]

Hi,

Here's the summary of the IRC meeting.

---

COMMUNITY MEETING

Place: #openvpn-meeting on irc.freenode.net
Date: Wednesday 26th June 2019
Time: 11:30 CEST (9:30 UTC)

Planned meeting topics for this meeting were here:

<https://community.openvpn.net/openvpn/wiki/Topics-2019-06-26>

Your local meeting time is easy to check from services such as

<http://www.timeanddate.com/worldclock>

SUMMARY

cron2, dazo, lev, mattock, sgstair and syzzer participated in this meeting.

---

Mattock gave an update on tap-windows6 HLK testing. Running code
analysis and static driver verifier (SDV) on the tap-windows6 source
code revealed some issues that need to be fixed for "Static Tools Logo
Test" to be guaranteed to pass. Sgstair already fixed some of them:

<https://github.com/OpenVPN/tap-windows6/pull/91>

Mattock will run SDV on tap-windows6 patched with this PR and report
back to sgstair. Sgstair will make a couple of additional fixes tomorrow.

Mattock will start running the "final" round of HLK tests once sgstair's
fixes are in.

Rozmansi pointed out that it should be able to run the "Operate in
Server Core" test on a virtual machine without jeopardizing the validity
of the HLK test result submission for tap-windows6.

---

The OpenVPN 3 team is putting together performance testing documentation
for tap-windows6 and wintun; it will describe how the test environment
was setup, how performance was measured and what results were obtained
from the test runs. The goal is to have a reproducible setup for others
to confirm if they want.

Noted that it would be possible to automate the setup of such a
environment with Terraform or CloudFormation.

---

Talked about various buildslave issues. Cmocka is missing from some of
them. Mattock will go through his buildslave and get that sorted out.
After this we can look into the TCP t_client problem (connects, ping4
and ping6 fail) on the Ubuntu 18.04 buildslave.

---

Talked about the "HackerOne report about sample plugin issue". Agreed
that there is a genuine problem even though it does not directly affect
OpenVPN. However, like bad configuration examples bad sample code will
get used by others and will thus cause problems indirectly. Cron2 will
look into fixing the issue.

Also agreed that we should get IBB to hand a bounty to the reporter.
Mattock will figure out how we can mark the report as worthy of a bounty.

--

Full chatlog attached.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock



[-- Attachment #1.1.2: openvpn_irc_meeting_chatlog_2019-06-26.txt --]
[-- Type: text/plain, Size: 17674 bytes --]

(12:29:14) syzzer: moin :)
(12:29:18) dazo: hey!
(12:29:33) cron2: moin :-)
(12:31:14) eworm [~eworm@...2498.../developer/eworm] è entrato nella stanza.
(12:33:23) cron2: so... has anyone seen mattock?
(12:33:36) dazo ha scelto come argomento: Next meeting 4/July/2019 at 20:00 CEST.  Agenda at https://community.openvpn.net/openvpn/wiki/Topics-2019-06-26
(12:33:57) dazo: Not more than that he appeared/joined here 10 min ago :)
(12:34:36) cron2: so, maybe we can start with 3, until then
(12:34:46) mattock: hi
(12:34:53) dazo: yeah
(12:34:56) mattock: do you think I would miss a meeting?
(12:35:00) mattock: :P
(12:35:16) cron2: mattock1: no, never ;-) - so, let's start with 1 instead
(12:37:13) mattock: so https://community.openvpn.net/openvpn/wiki/Topics-2019-06-26
(12:37:15) vpnHelper: Title: Topics-2019-06-26 – OpenVPN Community (at community.openvpn.net)
(12:37:26) mattock: let's get #1 out of the way
(12:38:14) mattock: the code analysis (enabled by rozmansi) and static driver verifier (separate tool) found issues in tap-windows6 which need to be fixed before starting the "final" HLK test run
(12:38:21) mattock: sgstair is working on those
(12:38:57) cron2: so it's not just "we need this report" but also "and we need to fix this". OK, I'll wait for PRs to show up and get reviewing.
(12:38:58) mattock: running HLK now would be pointless as any fixes (which are mandatory) would change the driver and we'd have to run the whole HLK test suite again
(12:39:04) cron2: ack
(12:39:28) mattock: so, hopefully I can start the famous "final run" early next week
(12:40:12) mattock: I also need a Windows Server 2019 Core, but rozmansi believes a virtual HLK client is sufficient for that particular test ("Operate in Server Core")
(12:40:48) mattock: anyways, that's all
(12:40:56) cron2: nice
(12:41:15) cron2: send PRs :)
(12:41:21) cron2: (can you share the report?)
(12:41:31) mattock: you mean code analysis results?
(12:41:34) cron2: yes
(12:41:39) mattock: yes, no problem
(12:41:43) mattock: where shall I put it
(12:41:44) mattock: ?
(12:41:53) cron2: I'm curious on the quality of the report, and on the actual findings
(12:42:01) cron2: mattock1: just mail it to me, pgp-crypted?
(12:42:33) lstip: hello
(12:42:54) mattock: cron2: doing it
(12:43:08) lstip: (ah wrong client)
(12:43:10) lev__: hello
(12:43:24) mattock: hi!
(12:43:28) mattock: cron2: sent
(12:43:31) cron2: hi lev, in all your personalities :)
(12:45:06) mattock: sgstair just sent a link to a commit: https://github.com/sgstair/tap-windows6/commit/33136dd79a3f8d8b0fed412f6f911005749faeb0
(12:45:07) vpnHelper: Title: Fix annotation problems noticed by code analysis. · sgstair/tap-windows6@...2514... · GitHub (at github.com)
(12:46:03) lstip ha abbandonato la stanza (quit: Quit: leaving).
(12:47:30) cron2: that was quick
(12:48:52) cron2: ok, that's no actual code change, just "tell the compiler what you are doing here, input or output parameters and such"... if I can have this as PR, I'm happy to ACK+merge it :)
(12:51:14) cron2: ok, anything else on tap?
(12:51:19) mattock: I will ask sgstair to create a PR
(12:51:20) mattock: no
(12:51:47) mattock: I can rerun code analysis + static driver verifier after or before this is merged
(12:52:35) cron2: you could run it on his branch, yes
(12:52:45) sgstair [~sgstair@...2515...] è entrato nella stanza.
(12:53:19) mattock: hi sgstair!
(12:53:20) dazo: Not directly to this tap ... but some somewhat FYI related .... We're working on putting together a performance testing documentation for tap-windows6 and wintun; documenting how we did the setup, how we measured performance and what we got in our runs ... The goal is to have a reproducible setup for others to confirm if they want
(12:53:32) sgstair: Hi!
(12:53:36) dazo: Hey!
(12:53:37) mattock: dazo: EC2-based?
(12:53:42) lev__: mattock1: yes
(12:53:44) dazo: mattock1: yes
(12:53:46) cron2: dazo: +good
(12:53:57) mattock: well, the ops team (e.g. me) can produce such a setup with Terraform
(12:54:02) mattock: that is reproducible
(12:54:19) dazo: mattock1: we're making a "document" we will put on the community wiki
(12:54:52) mattock: well, this is basically a couple of EC2 instances and some packages/setup on them, right?
(12:55:06) mattock: btw. maybe we discuss tap-windows6 a bit now that sgstair is here?
(12:55:14) mattock: I bet it is late where he is :)
(12:55:23) cron2: hi sgstair :-)
(12:55:24) dazo: mattock1: Ubuntu 18.04 LTS server with openvpn 2.4 server and Windows 2016 server
(12:55:25) sgstair: a bit late, yeah :)
(12:55:43) sgstair: hey cron2 
(12:55:44) dazo: or early, depending on time zone ;-)
(12:56:18) mattock: sgstair: does the commit you linked to fix all the MUSTFIX issues?
(12:56:26) sgstair: yes, it should
(12:56:50) mattock: ok, I can run the tests against it to verify (sgstair was unable to produce the same issues on his build setup)
(12:57:05) mattock: anything else in the code analysis results we should fix (now) in your opinion?
(12:58:09) sgstair: the other things I saw were - There are some possible integer overflow issues in stats (32bit overflow in a 64bit counter) - and there is a possibility to cause a bugcheck if the OS sends a packet smaller than the size of an ethernet header.
(12:58:43) sgstair: I'm not sure if the latter can even happen, but if it can, it would be good to fix.
(12:58:54) mattock: are these fairly trivial fixes?
(12:58:59) cron2: I thought we just look at sizes and drop packets if too small?  but yes, we should just silently throw the packet away
(12:59:01) sgstair: very.
(12:59:21) mattock: I say we fix everything we can now, rather than later
(12:59:53) sgstair: ok, I can provide another commit with further fixes tomorrow.
(12:59:56) mattock: ok, great!
(13:00:18) mattock: I will run the Static Driver Verifier with your current commit applied
(13:00:25) mattock: if there's something to report I will report back to you
(13:00:27) sgstair: cron2: this is on the path of a packet coming from NDIS - I don't recall if we have length checks there.
(13:00:59) sgstair: mattock1: sounds good.
(13:01:08) cron2: for the "is an arp or dhcp or ipv6 nd packet we need to specially handle?" we have lots of checks, but I'm not sure if we *always* check
(13:01:35) cron2: how does one annotate these IRQL things?
(13:03:36) sgstair: cron2: I'll have to double check, but you can provide an annotation on a function that indicates it's changing the IRQL. It's not too hard to find, just find the thing you're calling which does that also, and has the annotation you need.
(13:04:07) cron2: ah :)
(13:04:36) cron2: (so, yes, these look scary, but the functions are doing exactly this and named appropriately, we just need to tell the tool)
(13:05:54) sgstair: yeah, they're really not bad. Just the static analysis tools depend on the annotations being correct in order to make useful observations, so they complain when they see an inconsistency
(13:06:28) sgstair: code analysis is function-level analysis. SDV is more whole-program analysis
(13:09:19) sgstair: I looked closer at that "possible bugcheck" and it is actually somewhere different than I remember - it is a packet that has come through openvpn into the tap, but I'm not certain that guarantees it is ethernet-frame sized. Will look closer, but I'll probably add a guard regardless.
(13:10:39) sgstair: I guess it is true that it would have been padded thanks to the changes I made previously; so it should be fine.
(13:10:42) dazo: one thing is what OpenVPN does with tap-windows6 interfaces ... but OpenVPN is not the only user of this driver
(13:11:25) sgstair: yeah, true.
(13:14:02) mattock: anything else on tap-windows6?
(13:14:07) mattock: we have 16 minutes left 
(13:14:49) sgstair: nothing comes to mind from my end. Will coordinate with mattock1 over the next few days
(13:15:45) mattock: +1
(13:15:46) sgstair: I did drop the annotation changes commit into a PR
(13:16:04) cron2: sgstair: already :) - nice, I'll handle that later today
(13:16:30) sgstair: cool
(13:16:43) mattock: ls
(13:16:46) mattock: oops
(13:16:47) mattock: :)
(13:16:50) mattock: anyways
(13:16:55) mattock: so back to the test environment
(13:17:45) mattock: so there will be a document on trac describing how it is setup
(13:18:43) mattock: if we want, it would be quite easy to automate the setup with Terraform and Terraform provisioners so that even a dummy could reproduce it, provide he/she has AWS access keys and proper IAM policies
(13:19:13) cron2: not sure if I find the name "Terraform" brilliant or scary :)
(13:19:23) mattock: it is scary I tell you
(13:19:46) mattock: you can "terraform destroy" everything you built, with one command
(13:20:03) mattock: which has its uses, except in production :)
(13:20:20) mattock: dazo, lev: anything to add to the perf test environment topic?
(13:20:44) lev__: mattock1: well we are working on that doc
(13:20:55) dazo: yes, wiki page in trac giving all setup details, indicating expected results
(13:21:15) mattock: ok
(13:21:41) dazo: I'm not sure terraform has a use case now ... as lots of this documentation can be extracted and made for other kinds of setups too; like real hardware, etc
(13:21:51) lev__: is Terraform somewhat related to CloudFormation ?
(13:22:14) dazo: It shares 4 letters in the name .....
(13:22:20) dazo: 5 letters!
(13:22:40) lev__: in setup phase you are supposed to create VPC, internet gateway, security group etc. I think this all can be done with cloudformation script
(13:22:51) mattock: lev: that is correct, or with terraform
(13:23:06) lev__: so the end user could just provide API keys
(13:23:22) mattock: terraform is more useful in the sense that it support multiple clouds, _BUT_ the code you write is still effectively tied to a particular cloud
(13:23:37) mattock: because the resources are cloud-specific
(13:23:55) mattock: so not "write once, use anywhere"
(13:23:57) lev__: so for AWS it is a wrapper for CloudFormation?
(13:24:02) mattock: no
(13:24:17) mattock: the aws provider for terraform wraps raw AWS API calls
(13:24:47) mattock: I'm not sure if cloudformations support real (SSH) provisioning or just user_data
(13:25:03) mattock: but anyways, "the setup is automateable if we need/want"
(13:25:31) mattock: buildslave (lack of) maintenance next?
(13:25:56) cron2: very quickly :-) - who owns fedora29, and how can we get libcmocka installed there?
(13:26:07) mattock: me, by me running some commands :)
(13:26:09) syzzer: not me
(13:26:40) cron2: mattock1: ah, it *is* yours.  You seemed to be ducking away everytime someone said fedora29 :-) - so, please be installing libcmocka everywhere we have buildbot fails
(13:27:01) mattock: I shall do that
(13:27:05) ***cron2 was afraid that this is a "look I have donated a VM to you!"-thing where nobody can do anything
(13:27:21) cron2: then we should try to fix t_client on ubuntu 18, whatever is breaking it there for the TCP test
(13:27:38) dazo: mattock1: you need libcmocka-devel (which pulls in libcmocka)
(13:27:46) mattock: dazo: ok noted!
(13:28:09) cron2: good.  two minutes on #3...
(13:28:16) dazo: cron2: is it all TCP tests, or just one?
(13:28:30) dazo: On #3 ... That sample plugin is an ugly example ... it's not a security issue per-say (from a production perspective).  If any one puts that into production as is, it's not only insecure (even without this flaw), it's also acts completely stupid (running "sleep" in forked out process).
(13:28:30) dazo: This plug-in just demonstrates how the deferred mechanism works and how the main OpenVPN process would behave, it is far from an example of how to solve this challenge.
(13:28:37) mattock: #3 HackerOne report about sample plugin issue 
(13:28:44) cron2: dazo: it's only doing one TCP test, and that fails, but in an unexecpected way (it connects but ping fails)
(13:29:01) dazo: cron2: ipv4 or ipv6?
(13:29:07) cron2: both pings fail
(13:29:25) dazo: okay ... then it's a new issue
(13:29:35) cron2: yep :-)
(13:30:00) dazo: so .. #3 :)
(13:30:16) cron2: anyway, plugin - the way we ship it is a gaping hole.  Even if it should not be *used*, it's still showing horribly bad practice.
(13:30:41) cron2: so a) I think the report is valid and should get a bounty awarded, and b) we need to "do something".
(13:30:42) dazo: Yes, using system() plain out stupid ... but someone might think this is clever, so we should kick that out
(13:31:13) dazo: ahh ... well, it's not valid in the context that no system would ever run this in a production or even test environment
(13:31:21) dazo: it would serve no useful feature at all
(13:31:29) cron2: "just kicking out" is actually not straightforward as the whole "do async stuff with sleep and then..." is done in the system call with shell-backgrounding &
(13:32:10) dazo: cron2: exactly .... it's not a simple task ... but might get around things by using threading with join()
(13:32:37) dazo: join() once the "sleep" is done elsewhere, that is
(13:32:49) cron2: I wouldn't call it a "highly rate security vuln", and especially not "in OpenVPN" - but I still think the report should be appreciated.  Who is handling these discussions with OSTIF?  mattock1?
(13:33:04) cron2: what is join()?
(13:34:07) dazo: what you call on a thread ID to finally close it ... it will block if the thread isn't finished, otherwise it will just return the "exit code" of the thread
(13:34:13) mattock: cron2: tbh I can't recall us ever having a report on HackerOne that was worthy of bounty
(13:34:24) mattock: so I'm not exactly sure how the process goes
(13:34:37) mattock: but I believe it can all be done from within the HackerOne webui
(13:34:37) cron2: mattock1: we had no report yes, so I have no idea either :)
(13:35:26) dazo: pthread_join() is the C call :) .... std::thread objects in C++ got a .join() method
(13:35:26) cron2: dazo: mmmh, no manpage on this on my linux system... but I think the idea of the fork in the system() call was to "exit the parent right away, child communicates 20s later by file io"
(13:35:35) cron2: ah
(13:35:37) syzzer: not sure on the process, but I agree this report should be rewarded
(13:37:10) cron2: ok.  I'll look into the plugin to get the code fixed.  mattock1: can you contact hackerone/ostif on the mechanics?
(13:37:18) dazo: I have no strong opinion about the rewarding ... My argument is that this plug-in itself is of no value in a production environment
(13:37:38) cron2: true, but we still ship it as sample for "look, this is how you do it!"
(13:38:33) dazo: it's a development example demonstrating how deferred auth works .... the system() with sleep is just laziness to not write a gigantic code to make something happen later in the background
(13:38:46) syzzer: bad example code is like bad example configs, they proliferate and will and up as a real issue somewhere - even if it's not the case in the initial context
(13:38:49) mattock: cron2: yes I can contact IBB/HackerOne/OSTIF
(13:38:58) cron2: mattock1: thanks
(13:39:03) dazo: yeah, I can agree to that
(13:40:08) dazo: my point is probably more that this isn't a security vulnerability in OpenVPN ... it's just really crappy code documentation on deferred auth
(13:40:24) cron2: I agree on this
(13:40:48) cron2: but I've come to the conclusion that we need to "own" this as we ship the bad example code
(13:41:26) syzzer: what cron2 says :)
(13:41:35) dazo: yeah, agreed
(13:41:40) mattock: done for today? 11 minutes past our limit :)
(13:41:52) dazo: lets do 4 more minutes!
(13:41:52) cron2: no news on 2.5 anyway (I'll go and merge the two ACKs we have tonight)
(13:41:53) dazo: :-P
(13:42:17) dazo: I'll try to get the missing patch review out there again
(13:42:23) mattock: oh, one minor note: I will try to be on my traditional summer vacation start second week of July
(13:42:35) mattock: but I will wrap up all the important pending stuff regardless
(13:42:40) mattock: such as the infamous HLK stuff
(13:42:43) cron2: when is plaisthos back from vacation?
(13:43:01) dazo: oh ... on that note ... I'm starting my holiday tomorrow .... back July 22
(13:43:07) dazo: cron2: next week
(13:43:47) cron2: uh, 3.5 weeks... so we need to find someone else to review plaisthos v5 4/7...7/7
(13:44:18) dazo: I'll see if I get bored in the evenings .... but I won't be actively online
(13:44:18) syzzer: I might be able to step in there
(13:44:33) syzzer: this is the HMAC auth stuff, right?
(13:44:41) cron2: yep
(13:44:47) dazo: yeah, I trust syzzer is capable .... even on the broader parts too
(13:45:12) cron2: most definitely :-) - syzzer: and if your workload gets more reasonable these days "welcome back on board!" ;-)
(13:46:11) dazo: I have reviewed all ... I just need to find out where 5/7 and 6/7 went .... 5/7 I might need to write again, seems Thunderbird ate it
(13:46:34) syzzer: cron2: not likely, but I might be able to pick up work again anyway :)
(13:46:48) dazo: that said 5/7 is a more heavy one, with hmac stuff in it
(13:48:04) dazo: syzzer: Also see 9b117603-189a-b5da-b3e4-c7f22c7bc363@...2516....lists.topphemmelig.net for example configs and auth-scripts I've used for my testing
(13:48:23) syzzer: dazo: will do, thanks
(13:49:19) mattock: ok, done for today
(13:49:27) mattock: ?
(13:49:41) syzzer: yep, lunch!
(13:49:50) dazo: syzzer: 4/7 needs some fixes (compiler warnings) ... and also adds the initial hmac stuff ... your eyes here would be good
(13:50:00) cron2: syzzer:enjoy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-06-25  8:55         ` 
@ 2019-07-04 13:08           ` Simon Rozman
  2019-07-05  9:04             ` 
  0 siblings, 1 reply; 12+ messages in thread
From: Simon Rozman @ 2019-07-04 13:08 UTC (permalink / raw)


[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

Hi,

I just got from vacation and struggling to catch up on things...

> I got the Static Driver Verifier to run with help from Stephen. The
> correct (command-line) procedure is now documented here:
>
> <https://community.openvpn.net/openvpn/wiki/HLKTesting#StaticToolsLogoTe
> st>
>
> So it was bad usability after all. The tests are now running and
> hopefully I can create the merged test result package from SDV and Code
> Analysis today.

Reading your documentation, I found something odd.

I can just "cd src" and run:

msbuild tap-windows6.vcxproj /target:DVL /p:Configuration=Release;Platform=x64

And it produces tap0901.DVL.XML just fine. No need to jump into IDE and 
click-click-click to build it.

Regards,
Simon

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4919 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
  2019-07-04 13:08           ` Simon Rozman
@ 2019-07-05  9:04             ` 
  0 siblings, 0 replies; 12+ messages in thread
From:  @ 2019-07-05  9:04 UTC (permalink / raw)
  To: Simon Rozman <simon@

Hi Simon,

Il 04/07/19 16:08, Simon Rozman ha scritto:
> Hi,
> 
> I just got from vacation and struggling to catch up on things...
> 
>> I got the Static Driver Verifier to run with help from Stephen. The
>> correct (command-line) procedure is now documented here:
>>
>> <https://community.openvpn.net/openvpn/wiki/HLKTesting#StaticToolsLogoTe
>> st>
>>
>> So it was bad usability after all. The tests are now running and
>> hopefully I can create the merged test result package from SDV and Code
>> Analysis today.

The bad usability was referring to the GUI method of launching the SDV
(which I did not manage to get working).

> Reading your documentation, I found something odd.
> 
> I can just "cd src" and run:
> 
> msbuild tap-windows6.vcxproj /target:DVL /p:Configuration=Release;Platform=x64

Thanks! I added this to the documentation:

<https://community.openvpn.net/openvpn/wiki/HLKTesting#StaticToolsLogoTest>

> 
> And it produces tap0901.DVL.XML just fine. No need to jump into IDE and 
> click-click-click to build it.
> 
> Regards,
> Simon
> 


-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2019-07-05  9:04 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-05 11:55 [Openvpn-devel] Community meetings in June 2019 
2019-06-06 19:10 ` [Openvpn-devel] Summary of the community meeting (6th June 2019) 
2019-06-12 10:16 ` [Openvpn-devel] Summary of the community meeting (12th " 
2019-06-20 19:14 ` [Openvpn-devel] Summary of the community meeting (20th " 
2019-06-21 15:59   ` Simon Rozman
2019-06-24 11:33     ` 
2019-06-24 18:13       ` 
2019-06-24 20:24         ` 
2019-06-25  8:55         ` 
2019-07-04 13:08           ` Simon Rozman
2019-07-05  9:04             ` 
2019-06-26 11:05 ` [Openvpn-devel] Summary of the community meeting (26th " 

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.