From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Current branch of OpenSSL 3
Date: Tue, 21 Mar 2023 16:11:48 +0100 [thread overview]
Message-ID: <7e0aec78-fe12-fe22-4fcc-ee0735a9893a@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Hi Peter,
You were going to provide me with your current branch of OpenSSL 3 so I
can build it and test out OpenVPN with it to see if it causes anything
to break on my configuration.
Regards,
Adolf.
--
Sent from my laptop
next reply other threads:[~2023-03-21 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 15:11 Adolf Belka [this message]
2023-03-22 9:30 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e0aec78-fe12-fe22-4fcc-ee0735a9893a@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox