public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: openssl needs updated
Date: Sun, 30 May 2021 10:06:12 +0200	[thread overview]
Message-ID: <87fsy4lk7f.fsf@Rainer.invalid> (raw)
In-Reply-To: <d31d1ca2-065a-df82-0685-30ba7ce01997@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 30 May 2021 01:06:41 -0600")

Brian Inglis writes:
> On 2021-05-28 11:13, Brian Inglis wrote:
>> openssl/libssl has not been updated since 1.1.f two years ago and now
>> has four high sev CVEs outstanding in upstream 1.1.1k: two last year,
>> two this year.
>> If maintainer is short of time, I may be able to co-maintain?

If you really want co-maint and not just take over I'd suggest you
refrain from purely stylistic changes like these:

--8<---------------cut here---------------start------------->8---
 src_compile() {
-       cd ${S}
+       cd $S
        lndirs
--8<---------------cut here---------------end--------------->8---

I'd like to see the existing MingW64 packages moving to *-openssl10 (and
getting updated to the latest version as well), then updating *-openssl
to the 1.1 branch.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2021-05-30  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 17:13 Brian Inglis
2021-05-30  7:06 ` Brian Inglis
2021-05-30  8:06   ` Achim Gratz [this message]
2021-05-30 16:17     ` Brian Inglis

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=87fsy4lk7f.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).