For simple DB stuff, you can use ODBC libraries, they are
available/compilable on all platforms.
- Original Message -
From: Dr Stephen Henson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 07, 1999 9:30 AM
Subject: Re: CA DB Support
> Massimil
Dr Stephen Henson wrote:
> I've often considered using some kind of database for certificates. One
> problem is getting something that compiles on all platforms.
We could get cooperation from the OpenLDAP people as they had to do it
and I think they done a very good job. However I could say we c
Bruce Stephens wrote:
>
> Massimiliano Pala <[EMAIL PROTECTED]> writes:
>
> > I was discussing with some people from the OpenCA project and we do
> > think that a DB support (like Berkeley DB, NDBM, GDBM) should be
>
> However, I'd guess the current design is probably fine for, say, 1
> cert
Massimiliano Pala wrote:
>
> Bruce Stephens wrote:
>
> > I haven't tested. I'd guess index.txt would cause some things to slow
> > performance (but possibly not---I'm assuming there are linear searches
> > around). The public keys seem to be kept in separate files in a
> > directory: however t
>but our question is about 5/10 Millions of certificates.
You might look at what typical (traditional?) Usenet
implementations do...
__
OpenSSL Project http://www.openssl.org
Development Mailing Li
Bruce Stephens wrote:
> I haven't tested. I'd guess index.txt would cause some things to slow
> performance (but possibly not---I'm assuming there are linear searches
> around). The public keys seem to be kept in separate files in a
> directory: however they get used, that's going to cause some
Massimiliano Pala <[EMAIL PROTECTED]> writes:
> I was discussing with some people from the OpenCA project and we do
> think that a DB support (like Berkeley DB, NDBM, GDBM) should be
> added to the ca application to store certificates' information and
> assure scalability.
>
> What do you know a
