[SERVER-38217] Consider recording failed attempts to kill cursors in the audit log Created: 20/Nov/18  Updated: 29/Oct/23  Resolved: 16/Apr/19

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: None
Fix Version/s: 4.0.10

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Sara Golemon
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Security 2019-04-22
Participants:

 Description   

See TODOs here (which I intend to remove soon after filing this ticket):
https://github.com/mongodb/mongo/blob/e768373f878c43100c023565c01ed16ad810ad1b/src/mongo/db/cursor_manager.cpp#L188-L189

https://github.com/mongodb/mongo/blob/e768373f878c43100c023565c01ed16ad810ad1b/src/mongo/db/cursor_manager.cpp#L198-L199

These are cases where someone attempted to kill a cursor but failed.



 Comments   
Comment by Githook User [ 16/Apr/19 ]

Author:

{'name': 'Sara Golemon', 'username': 'sgolemon', 'email': 'sara.golemon@mongodb.com'}

Message: SERVER-38217 audit failed OP_KILL_CURSOR
Branch: v4.0
https://github.com/mongodb/mongo/commit/8d3de2bd46d679a32c8075f318731ef2d023b731

Generated at Thu Feb 08 04:48:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.