From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [openssl-announce] Forthcoming OpenSSL releases
Date: Tue, 20 Mar 2018 20:41:11 +0000 [thread overview]
Message-ID: <1521578471.178881.67.camel@ipfire.org> (raw)
In-Reply-To: <d3e945a1-8ac5-e640-ea17-d2343d735cd0@openssl.org>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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+QCQcFAlqxcecACgkQgHnw/2+Q
CQfiZRAAqRLmjco4V2rxJTjNaYRM7o+YbHG9gvW5xjHdMAJURDyDaxc+DTkMJyoq
woLrf86RDylKT4SdilGDS+3AXtZuy3H/qRsKr+HjNgpgdP9Hh+bzuu9buml4n3F9
wvxOdmOuAhQKWJpwJIifuqAMjJrI6wzUhAsR13ttXX+YHr6B+dcQ0r1zZI5xmolc
YKFVF0BQBtABXnc4mjqeiQcPm1NbbIoHF0kuqD43ljz5I0C5Mc9E3LS/VSeQgQ8M
tw9BvZNyA+ul3GZ3pL98L40ORPcL3UJ6sC0YmCpVkZ6I1F1WHXs+2DKqiKOifi5x
PPBK9Q23K1gbD9fAkdvzlbjeQFOVb3eCglmZ4Jc07oeC398qXA85EOeCFqnu1fhQ
2sRa4HXT4llJS3m0HddvdHKCz4HEpc8YwQ+hGkH9t0eCVqul1u/wNujMtoZSyWqv
9/IQjxaDGVzL5kG+UqrxYIYllQ0qqfcwgx9uDZy/3u3JYdnQ+pVIMFI+fZx29F2T
gSV3McuSHBBtwZvgBBVNHCv/djNbwmhv69RBZQWQuriqxmTCTvgFMRltoDecFv8A
MkTfGwZNWaP5NjdYiV5O8fE4N4gir6ISCZUqDpe3NGoq/tE6ziPKOupJvSNjWq/a
Vt1YOx1O2uqlSStEqjtykTdS2uZ0G58kML26BY/wlDNL+1yDd/A=
=wVcZ
-----END PGP SIGNATURE-----
next parent reply other threads:[~2018-03-20 20:41 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 [this message]
2018-03-27 15:37 ` 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=1521578471.178881.67.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