From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [openssl-announce] Forthcoming OpenSSL releases
Date: Tue, 27 Mar 2018 16:37:11 +0100 [thread overview]
Message-ID: <1522165031.556038.84.camel@ipfire.org> (raw)
In-Reply-To: <1521578471.178881.67.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
so since this isn't too bad for us, we are just going to continue with releasing
C120 as scheduled.
Best,
- -Michael
On Tue, 2018-03-20 at 20:41 +0000, Michael Tremer wrote:
> Hello,
>
> so as you can see, we can expect a security issue in OpenSSL which will be
> made
> public next Tuesday. The current release branch and next will be affected by
> what ever this problem is.
>
> We might (or might not) need to roll out an emergency Core Update before we
> can
> release Core Update 120. So we will wait with uploading that into testing
> until
> we know how to proceed.
>
> Best,
> -Michael
>
> On Tue, 2018-03-20 at 17:18 +0000, Matt Caswell wrote:
> > Forthcoming OpenSSL releases
> > ============================
> >
> > The OpenSSL project team would like to announce the forthcoming release
> > of OpenSSL versions 1.1.0h and 1.0.2o.
> >
> > These releases will be made available on 27th March 2018 between
> > approximately 1300-1700 UTC.
> >
> > These are security-fix releases. The highest severity issue fixed in
> > these releases is MODERATE.
> >
> > Yours
> >
> > The OpenSSL Project Team
> >
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlq6ZSgACgkQgHnw/2+Q
CQf93w//aBET0ccQTeBeJa2N5kOiluHG+mYd734DV21ETn3QWYuX5oB4NFyWorn2
5yRVFUKbBt7+PhaS2nXor3j7ccvYVgFJB0sp8BGEfSibG2RAfMnK9Jhv5JerCFHb
klpm+u27KSvIApOuwZfv9vLdYrVmup887r+qfBhijdvpTG5aUiSSBQ++nq36VEoT
NdgiNgyqPM90wsmPor/hf3IobAqTC8VOUs7GSIq9plhyoWnQRbxdWF2I/SK4mIxZ
IlgNxYp9zYq7o4c6x9JrkWtJonGmJk8FPyLr7/8PulpdZqjpQOBLZHkKfV5wp2z0
x6kUBdKLv9DP8bTx4I28AmFRwIV7TrjezLZIttFnaHekNDLMecZird3m+RzTANTC
yz9uwKyDg1Rgg3avbB60e7nSy6FXWhaHEKYOTNKtJDRuqTZREHyttPAKk/xbikbi
I/IGazbder1rEV3UOsTl3RLrYppxD2JhNyZsGX7WPZHDoWszGog9KtOxX7pu0gk7
ICyGxgR180s99Z+Srpmal5DGz+jDX135f60e43PIT3sSnn7ll/TO1r6easKcxT9v
K71w3QhJZQzjN5Xd/hMgjPXJBz6yS7XAj/wGsuzOcvhEKduXm24aIRo6u0t236jx
k6viumdHN+LRjRIuY7iu7vkXqtcYTIzImPq5agBfbP0lEajEe78=
=bcU/
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-03-27 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d3e945a1-8ac5-e640-ea17-d2343d735cd0@openssl.org>
2018-03-20 20:41 ` Michael Tremer
2018-03-27 15:37 ` Michael Tremer [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=1522165031.556038.84.camel@ipfire.org \
--to=michael.tremer@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