I'm not quite sure I understand what you're asking me to do. Why not
simply use standard github cooperation mechanisms?
Whatever, I put the stuff into
https://github.com/OpenVPN/openvpn/pull/170 but couldn't run the command
suggested there:
$ git send-email --to=openvpn-devel@lists.sourceforge.net HEAD~1
git: 'send-email' ist kein Git-Befehl. Siehe 'git --help'.
Pardon the German of my computer: It says "send-email" is no known git
command.
Please let me know what to do now.
Regards,
--Michael
FWIW, I now have
Am 25.03.22 um 16:09 schrieb Antonio Quartulli:
On 25/03/2022 16:04, Arne Schwabe wrote:
Am 25.03.22 um 08:21 schrieb Michael Baentsch:
Thanks very much for the quick and thorough feedback. Indeed your
last question is pivotal making the patch _much_ simpler (attached):
The problem manifests itself only in the presence of providers
introduced in OpenSSL3.0. At the same time, the curve name causing
the "dance code" is permitted as of OpenSSL3.0...
So all other observations below are moot/should be resolved with the
much simpler new patch attached. Feel free to delete/amend the
comment changes as you see fit.
Thanks v2 looks much better code wise and gets ack from me. To commit
the patch could you either send the patch in git format-message
format or provide a commit subject and text so we can make full
commit of your patch?
We also need the patch to bear the sign-off-by line, so better create
an actual git commit and export it via git-format-patch.
Cheers,
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
