public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: openssl needs updated
Date: Sun, 30 May 2021 10:17:56 -0600	[thread overview]
Message-ID: <fb6f8f54-ece8-f073-6090-175f1da717e2@SystematicSw.ab.ca> (raw)
In-Reply-To: <87fsy4lk7f.fsf@Rainer.invalid>

On 2021-05-30 02:06, Achim Gratz wrote:
> 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:
>   src_compile() {
> -       cd ${S}
> +       cd $S
>          lndirs

Those are from my own local builds I keep more up to date than releases.
I manually switch from release or local tars to check builds.

> 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.
OpenSSL 1.0.2u was EoL and unsupported end of 2019:
https://www.openssl.org/blog/blog/2019/11/07/3.0-update/
Cygwin current is 1.0.2t so close but mingw is 1.0.2o 3 years ago.

OpenSSL 3 came out a year ago and is still in alpha # 17.

I haven't even looked at mingw packages because they are so outdated.
I am afraid to find out why they have not been updated to 1.1.1! ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]



      reply	other threads:[~2021-05-30 16:17 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
2021-05-30 16:17     ` Brian Inglis [this message]

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=fb6f8f54-ece8-f073-6090-175f1da717e2@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).