summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorIlya Dryomov <idryomov@gmail.com>2016-12-02 16:35:09 +0100
committerSasha Levin <alexander.levin@verizon.com>2017-01-12 20:56:57 -0500
commite1589b27ffb95ef8286dee5c2a2e4f7ab97763cd (patch)
tree4ad3f44afe490a0a477cb714375d42a468bdc33a /drivers
parented21b94ebbf4218baadbaad82bbea8a43a8bf5a9 (diff)
libceph: verify authorize reply on connect
[ Upstream commit 5c056fdc5b474329037f2aa18401bd73033e0ce0 ] After sending an authorizer (ceph_x_authorize_a + ceph_x_authorize_b), the client gets back a ceph_x_authorize_reply, which it is supposed to verify to ensure the authenticity and protect against replay attacks. The code for doing this is there (ceph_x_verify_authorizer_reply(), ceph_auth_verify_authorizer_reply() + plumbing), but it is never invoked by the the messenger. AFAICT this goes back to 2009, when ceph authentication protocols support was added to the kernel client in 4e7a5dcd1bba ("ceph: negotiate authentication protocol; implement AUTH_NONE protocol"). The second param of ceph_connection_operations::verify_authorizer_reply is unused all the way down. Pass 0 to facilitate backporting, and kill it in the next commit. Cc: stable@vger.kernel.org Signed-off-by: Ilya Dryomov <idryomov@gmail.com> Reviewed-by: Sage Weil <sage@redhat.com> Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions