Hi,
can you write a conclusion of the database schema changes? The change in
OpenCA::DBI for splitted index is really small and can easily replace
the old hack :)
The table definition is splitted into two parts - the index columns and
the rest. Example:
CERTIFICATE => {
KEY => {"C
Hi,
>> If you change the association of EXTERNAL_CA and INTERNAL_CA in the
>> table above, all previously created entries are changed implicitly.
>> Of course, this association *should* never be changed, an INTERNAL_CA
>> is not supposed to be "changing" to another EXTERNAL_CA.
>>
>> If we keep th
Martin Bartosch wrote:
- introduce a new table, e. g. CA
Purpose:
- identification and reference of CA certificate for internal CAs
- mapping between internal and external CAs
Attributes:
INTERNAL_CA: internal CA
EXTERNAL_CA: external CA this CA belongs to
CA_CERT_SERIAL: serial number of
Martin Bartosch wrote:
- introduce a new table, e. g. CA
Purpose:
- identification and reference of CA certificate for internal CAs
- mapping between internal and external CAs
Attributes:
INTERNAL_CA: internal CA
EXTERNAL_CA: external CA this CA belongs to
CA_CERT_SERIAL: serial number of
Hi,
I forgot:
>>> - introduce a new table, e. g. CA
>>> Purpose:
>>> - identification and reference of CA certificate for internal CAs
>>> - mapping between internal and external CAs
>>> Attributes:
>>> INTERNAL_CA: internal CA
>>> EXTERNAL_CA: external CA this CA belongs to
>>> CA_
Hi,
following up our discussion in the CRL serial thread:
>> - remove the CA_CERTIFICATE table
>> Reason: CA certificates are just ordinary certificates, see below
>
> Nice idea - usually the table only includes one certificate which means
> that there is a design bug.
And it's even not very u
