[SERVER-23570] Make SecureAllocator a real allocator Created: 06/Apr/16 Updated: 08/Jan/24 Resolved: 03/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.7, 3.3.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 1 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | Platforms 13 (04/22/16), Platforms 14 (05/13/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
The secure allocator should be more like a real allocator. I.e. it shouldn't require a mmap or virtual alloc call for every allocation. We would need to retain the constraints that:
Lets:
|
| Comments |
| Comment by Githook User [ 10/May/16 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Also adds SecureT, a wrapper proxy for newing objects on the secure heap. (cherry picked from commit 6d7be60bbbf5a6be21c57398ab8616c4241b50a7) |
| Comment by Githook User [ 10/May/16 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Enterprise changes required by the main repo SecureAllocator changes (cherry picked from commit cbf6afe111567a61a3a8aeabe849ef90fe22aa1e) |
| Comment by Githook User [ 19/Apr/16 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Enterprise changes required by the main repo SecureAllocator changes |
| Comment by Githook User [ 19/Apr/16 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Also adds SecureT, a wrapper proxy for newing objects on the secure heap. |