[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Basic Cert-2-Directory mapping question
I've got a slightly older copy of the papers I mentioned a few days ago
available online, they're linked via my home page
http://www.cs.auckland.ac.nz/~pgut001/, with the text extracted below. There
are also some slides from my talk at ACSAC which cover some things I didn't
have room for in the paper, I'll put those online within the next week. I'd
be interested in feedback.
-- Snip --
One section of my thesis, which covered certificate stores, had to be dropped
due to size constraints. As with the work in the other chapters, it begins by
analysing the requirements (in this case for a reliable, scalable,
general-purpose certificate store), and then examines various potential
candidates which might meet these requirements. The single chapter ended up
broken down into two papers because of its size, the first paper (published at
ACSAC 2000) mostly stands by itself but the second one, not yet published, is
rather lopsided and needs the first paper to lean against. Both have had some
minor revisions made based on feedback which postdate the online versions, in
addition the second one (which was put together in a bit of a hurry at the
same time my thesis was due and definitely isn't my best work) covers a
slightly older design than what's currently being used and needs some changes
to bring it up to date. I also need to add pointers to work which has
appeared after it was written such as the CCS 2000 papers on undeniable
attestations and fault-tolerant revocations, which is similar to the scheme
which I examine in the second half of the paper. Don't treat this as a
finished work.
The first paper, http://www.cryptoengines.com/~peter/09a_cert_store.pdf A
Reliable, Scalable, General-purpose Certificate Store has a pretty
self-explanatory title. The second one,
http://www.cryptoengines.com/~peter/09b_cert_store.pdf Certificate Management
as Transaction Processing looks at certificate and certificate
status/revocation management from a TP perspective.
-- Snip --
Peter.