netdev - Re: [PATCH net-next 00/10] pull request for net-next: ovpn 2025-05-09

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1da26f53-634b-4562-849d-c1c7d5be2d18@openvpn.net>
Date: Fri, 9 May 2025 16:55:27 +0200
From: Antonio Quartulli <antonio@...nvpn.net>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 Sabrina Dubroca <sd@...asysnail.net>
Subject: Re: [PATCH net-next 00/10] pull request for net-next: ovpn 2025-05-09

On 09/05/2025 16:40, Andrew Lunn wrote:
> On Fri, May 09, 2025 at 04:26:10PM +0200, Antonio Quartulli wrote:
>> Hi Jakub,
>>
>> here is my first pull request for the ovpn kernel module!
>>
>> As you can see in the patches, we have various tags from
>> Gert Döring, the main maintainer of openvpn userspace,
>> who was eager to test and report malfunctionings.
>> He reported bugs, stared at fixes and tested them, hence
>> the Reported/Acked/Tested-by tags. If you think such
>> combination of tags is not truly appropriate, please let
>> me know.
> 
> Ideally, all this discussion should have happened on the netdev, where
> others can take part and learn more about how ovpn works. If this
> happened in the open on some other list, please could you include a
> link in the patches.

Reporting happens often on our IRC channel (#openvpn-devel @ 
irc.libera.chat) and then we track bugs on GitHub[1].

After getting the bug report I sent bugfixes/patches to our public 
mailing list (the one listed in MAINTAINERS).
At that point Gert reported his findings (with his tags) in response to 
the patches.

I can add a "Link:" tag to each patch, where I provide the URL of the 
patch on the openvpn-devel mailing list (with following discussion).

I don't know if I should also include the URL to the GitHub issue?
If yes, which tag should I use?

Thanks a lot!

[1]https://github.com/OpenVPN/ovpn-net-next/issues

-- 
Antonio Quartulli
OpenVPN Inc.