Secure kernel transactions

• US 7,591,015 B2
• Filed: 10/23/2003
• Issued: 09/15/2009
• Est. Priority Date: 10/23/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Tipton, William R., Zbikowski, Mark J., Verma, Surendra, Cargille, Jon
• Primary Examiner(s): Vu; Kimyen
• Assistant Examiner(s): TRUVAN, LEYNNA THANH
• Application Number:
  US10/692,261
• Publication Number:
  US 20050091502A1
• Time in Patent Office: 2,154 Days
• Field of Search: 726/2, 726 4- 6, 726/14, 726 17- 18, 726/21, 726/27, 726/30, 713151-152, 711/100, 711/145, 711/163, 711/205, 711/207, 705 75- 76, 709223-225, 709/229
• US Class Current: 726/18
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 21/6281 at program execution time, where the protection is within the operating system
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register

Abstract

Kernel objects for implementing a transaction have a security descriptor applied thereto. The kernel objects include, at least, a transaction object, a resource management object, and an enlistment object. The security descriptor, otherwise known as an access control list, identifies at least one user, an operation to be performed on the kernel object to which the security descriptor is applied, and a right indicating that the identified user is permitted or prohibited to perform the operation.

Claims

1. A kernel-level transaction system, comprising:

a memory;

one or more processors operatively coupled to the memory and disposed within one or more devices;

a kernel-level transaction manager disposed within each device, each said kernel-level transaction manager including a plurality of kernel objects to implement a transaction having plural operations, wherein the plurality of kernel objects include a transaction object to represent a transaction, a resource manager object to represent a resource participating in the transaction, and an enlistment object to enlist participants in the transaction, wherein the transaction is performed at the kernel-level; and

a security descriptor, applied to at least one of the kernel objects, to identify at least one user, to identify one of the operations of the transaction that may be performed on the kernel object to which the security descriptor is applied, and to identify a right indicating that the identified user is permitted or prohibited to perform the operation.

2. A system according to claim 1, wherein the security descriptor comprises at least one access control entry (ACE), which includes a security identifier (SID) and rights corresponding to the SID.

3. A system according to claim 1, wherein the security descriptor is applied to the transaction object, and the operation identified by the security descriptor includes at least one of:

set information regarding the transaction object,

enlist the transaction object in the transaction,

render data updates in connection with the transaction object durable,

abort the operation on the transaction object,

transmit data from the transaction object to another object,

the current point of the transaction at the transaction object, and

transmit data regarding the transaction to another device.

4. A system according to claim 1, wherein the security descriptor is applied to the resource manager object, and the operation identified by the security descriptor includes at least one of:

retrieve information regarding the resource manager object,

set information regarding the resource manager object,

determine the state of a transaction at a moment of transaction failure,

enlist the resource manager object in a transaction,

register the resource manager object in the transaction,

receive notification upon resolution of a transaction at the resource manager object, and

set resource data in accordance with the transaction resolution.

5. A system according to claim 1, wherein the security descriptor is applied to the enlistment object, and the operation identified by the security descriptor includes at least one of:

get information regarding the enlistment object,

set information regarding the enlistment object,

determine a state of enlistments at a moment of transaction failure

obtain and reference an enlistment key,

rollback the transaction and to respond to notifications, and

perform operations a superior transaction manager would perform.

6. A computer-readable medium having stored thereon an object attached to a kernel object, the object comprising:

a first data entry identifying at least one user;

a second data entry identifying an operation capable of being performed on the kernel object by the user identified by the first data entry, wherein the kernel object comprises a transaction object to represent a transaction, a resource manager object to represent a resource participating in the transaction and/or an enlistment object to enlist participants in the transaction, wherein the transaction is performed at the kernel-level; and

a third data entry indicating a right for the user identified by the first data entry to perform the operation identified by the second data entry;

wherein the object attached to the kernel object is a security descriptor.

7. A computer-readable medium according to claim 6, wherein the kernel object is a transaction object, and the identified operation includes at least one of:

set information regarding the transaction object,

enlist the transaction object in the transaction,

render data updates in connection with the transaction object durable,

abort the operation on the transaction object,

transmit data from the transaction object to another object,

save the current point of the transaction at the transaction object, and

transmit data regarding the transaction to another device.

8. A computer-readable medium according to claim 6, wherein the kernel object is a resource manager object, and the identified operation includes at least one of:

retrieve information regarding the resource manager object,

set information regarding the resource manager object,

determine the state of a transaction at a moment of transaction failure,

enlist the resource manager object in a transaction,

register the resource manager object in the transaction,

receive notification upon resolution of a transaction at the resource manager object, and

set resource data in accordance with the transaction resolution.

9. A computer-readable medium according to claim 6, wherein the kernel object is an enlistment object, and the identified operation includes at least one of:

get information regarding the enlistment object,

set information regarding the enlistment object,

determine a state of enlistments at a moment of transaction failure,

obtain and reference an enlistment key,

rollback the transaction and to respond to notifications, and

perform operations a superior transaction manager would perform.

10. A method of implementing a kernel-level transaction, comprising:

attaching a security descriptor to at least one of a plurality of kernel objects utilized in a kernel-level transaction, wherein the security descriptor includes identification for at least one user, an operation to be performed on the at least one kernel object to which the security descriptor is attached, and a right indicating that the identified user is permitted or prohibited to perform the operation and each of the kernel objects comprise a transaction object, a resource manager object and/or an enlistment object; and

performing an operation for a kernel-level transaction on the at least one object in accordance with the rights accorded by the security descriptor attached to the at least one object.

11. A method according to claim 10, wherein the operation identified by the security descriptor attached to the transaction object includes at least one of:

set information regarding the transaction object,

enlist the transaction object in the kernel-level transaction,

render data updates in connection with the transaction object durable,

abort the operation on the transaction object,

transmit data from the transaction object to another object,

save the current point of the kernel-level transaction at the transaction object, and

transmit data regarding the kernel-level transaction to another device.

12. A method according to claim 10, wherein the operation identified by the security descriptor attached to the resource manager object includes at least one of:

retrieve information regarding the resource manager object,

set information regarding the resource manager object,

determine the state of a kernel-level transaction at a moment of transaction failure,

enlist the resource manager object in a kernel-level transaction,

register the resource manager object in the kernel-level transaction,

receive notification upon resolution of a kernel-level transaction at the resource manager object, and

set resource data in accordance with the kernel-level transaction resolution.

13. A method according to claim 10, wherein the operation identified by the security descriptor includes at least one of:

get information regarding the enlistment object,

set information regarding the enlistment object,

determine a state of enlistments at a moment of transaction failure,

obtain and reference an enlistment key,

rollback the kernel-level transaction and to respond to notifications, and

perform operations a superior transaction manager would perform.

14. A kernel-level transaction system, comprising:

a memory;

one or more processors operatively coupled to the memory;

means for implementing a kernel-level transaction among kernel objects, wherein the kernel objects include a transaction object to represent a transaction, a resource manager object to represent a resource participating in the transaction, and an enlistment object to enlist participants in the transaction, wherein the transaction is performed at the kernel level; and

means for securing the transaction by applying a security descriptor to at least one of the kernel objects,

wherein the security descriptor identifies at least one user, an operation to be performed on the kernel object to which the security descriptor is applied, and a right indicating that the identified user is permitted or prohibited to perform the operation.

15. A system according to claim 14, wherein the security descriptor is applied to the transaction object, and the operation identified by the security descriptor includes at least one of:

set information regarding the transaction object,

enlist the transaction object in the transaction,

render data updates in connection with the transaction object durable,

abort the operation on the transaction object,

transmit data from the transaction object to another object,

save the current point of the transaction at the transaction object, and

transmit data regarding the transaction to another device.

16. A system according to claim 14, wherein the security descriptor is applied to the resource manager object, and the operation identified by the security descriptor includes at least one of:

retrieve information regarding the resource manager object,

set information regarding the resource manager object,

determine the state of a transaction at a moment of transaction failure,

enlist the resource manager object in a transaction,

register the resource manager object in the transaction,

receive notification upon resolution of a transaction at the resource manager object, and

set resource data in accordance with the transaction resolution.

17. A system according to claim 14, wherein the security descriptor is applied to the enlistment object, and the operation identified by the security descriptor includes at least one of:

get information regarding the enlistment object,

set information regarding the enlistment object, and

determine a state of enlistments at a moment of transaction failure.