Browse Prior Art Database

Better Database Appended Sequence Tags Based On Trusted Computing Group Technology

IP.com Disclosure Number: IPCOM000127426D
Original Publication Date: 2005-Aug-30
Included in the Prior Art Database: 2005-Aug-30
Document File: 2 page(s) / 29K

Publishing Venue

IBM

Abstract

Better Database Appended Sequence Tags Based On Trusted Computing Group Technology is a method which allows databases to manage write append database records as a single file separated by tags without the possibility of malicious or inadvertent tag spoofing.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 1 of 2

Better Database Appended Sequence Tags Based On Trusted Computing Group Technology

Databases often place sequence tag or marker in appended data records. This eliminates the need to track separate metadata records each time data was added to a file and allows the database to easily manage write append records as a single file.

A problem can occur when the user enters data in the format of a sequence marker. We'll used the fictitious database of fooDB to illustrate this situation.

An example of a fooDB Record is:

<Note by shawnm (Mullen, Shawn), 2004/05/28 09:37:34, seq: 15 rel: 0 action: note>

This tag is added to the DB write append file whenever user shawnm appends data to the record. This tag is used to distinguish the data entered by user shawnm.

Another user could use this tag in the text they enter, inadvertently causing fooDB difficulty in distinguishing DB entries. For example,

1: <Note by john (Doe, John), 2004/05/28 09:38:00, seq: 16 rel: 0 action: note> 2 : According to shawn's remarks in the DB entry: 3: <Note by shawnm (Mullen, Shawn), 2004/05/28 09:37:34, seq: 15 rel: 0 action: note>

This could cause fooDB problems because it would read John's tag on line one, and then see another possibly valid tag on line 3. Would fooDB know that the tag on line3 was added by John, or should fooDB check the DB for possible corruption.

Additionally, a user would enter a tag maliciously: 1: <Note by john (Doe, John), 2004/05/29 09:38:00, seq: 17 rel: 0 action: note>...