From: "Brent Kennedy" <bkennedy@cfl.rr.com>
To: "'David Galloway'" <dgallowa@redhat.com>, <ceph-announce@ceph.io>,
<ceph-users@ceph.io>, <dev@ceph.io>, <ceph-devel@vger.kernel.org>,
<ceph-maintainers@ceph.io>
Subject: RE: [ceph-users] v15.2.6 Octopus released
Date: Sat, 21 Nov 2020 20:39:14 -0500 [thread overview]
Message-ID: <009401d6c070$492749b0$db75dd10$@cfl.rr.com> (raw)
In-Reply-To: <9b6eefd1-e6f9-ddc2-2eed-6ecba00fb982@redhat.com>
FYI, ceph-ansible has a problem due to ceph-volume , so don't do it via the
rolling-upgrade.yml script.
-Brent
-----Original Message-----
From: David Galloway <dgallowa@redhat.com>
Sent: Wednesday, November 18, 2020 9:39 PM
To: ceph-announce@ceph.io; ceph-users@ceph.io; dev@ceph.io;
ceph-devel@vger.kernel.org; ceph-maintainers@ceph.io
Subject: [ceph-users] v15.2.6 Octopus released
This is the 6th backport release in the Octopus series. This releases fixes
a security flaw affecting Messenger V2 for Octopus & Nautilus. We recommend
users to update to this release.
Notable Changes
---------------
* CVE 2020-25660: Fix a regression in Messenger V2 replay attacks
Getting Ceph
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-15.2.6.tar.gz
* For packages, see http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: cb8c61a60551b72614257d632a574d420064c17a
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email
to ceph-users-leave@ceph.io
prev parent reply other threads:[~2020-11-22 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 2:38 v15.2.6 Octopus released David Galloway
2020-11-19 10:47 ` [ceph-users] " Ilya Dryomov
2020-11-22 1:39 ` Brent Kennedy [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='009401d6c070$492749b0$db75dd10$@cfl.rr.com' \
--to=bkennedy@cfl.rr.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 \
--cc=dgallowa@redhat.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 NNTP newsgroup(s).