From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-announce@ceph.io, ceph-users@ceph.io, dev@ceph.io,
ceph-devel@vger.kernel.org, ceph-maintainers@ceph.io
Subject: v15.2.2 Octopus released
Date: Mon, 18 May 2020 22:27:21 +0200 [thread overview]
Message-ID: <87ftbx3s5y.fsf@suse.com> (raw)
We're happy to announce the second bugfix release of Ceph Octopus stable
release series, we recommend that all Octopus users upgrade. This
release has a range of fixes across all components and a security fix.
Notable Changes
---------------
* CVE-2020-10736: Fixed an authorization bypass in mons & mgrs (Olle
SegerDahl, Josh Durgin)
For the complete changelog please refer to the full release blog at
https://ceph.io/releases/v15-2-2-octopus-released/
Getting Ceph
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-15.2.2.tar.gz
* For packages, see
http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: 0c857e985a29d90501a285f242ea9c008df49eb8
--
Abhishek Lekshmanan
SUSE Software Solutions Germany GmbH
GF: Felix Imendörffer, HRB 36809 (AG Nürnberg)
reply other threads:[~2020-05-18 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ftbx3s5y.fsf@suse.com \
--to=abhishek@suse.com \
--cc=ceph-announce@ceph.io \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-maintainers@ceph.io \
--cc=ceph-users@ceph.io \
--cc=dev@ceph.io \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.