blob: 52fac1e6fef90d258f6e2c385a2bf5e19f993f24 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
# Notes on the PEM and cert caches
## Data relations
|---------------| |------------------------|
| PemCache | | CertDb |
|---------------| * |------------------------|
| FilePath (PK) | +---- | {Ref, SN, Issuer} (PK) |
| FileContent | | | Cert (Subject) |
|---------------| | |------------------------|
|0,1 |
| +-----------+
|0,1 |1
|-----------------| |------------|
| FileMapDb | | RefDb |
|-----------------|1 1 |------------|
| CaCertFile (PK) |---------------| Ref (PK) |
| Ref (FK) | | Counter |
|-----------------| |------------|
### PemCache
1. stores a copy of file content in memory
2. includes files from cacertfile, certfile, keyfile options
3. content is added unless FileMapDb table contains entry with specified path
### FileMapDb
1. holds relation between specific path (PEM file with CA certificates) and a ref
2. ref is generated when file from path is added for 1st time
3. ref is used as path identifier in CertDb and RefDb tables
### RefDb
1. holds an active connections counter for a specific ref
2. when counter reaches zero - related data in CertDb, FileMapDb, RefDb is deleted
### CertDb
1. holds decoded CA ceritificates (only those taken from cacertfile option)
2. used for building certificate chains
3. it is an ETS set table - when iterating in search of Issuer certificate,
processing order is not guaranted
4. Table key is: {Ref, SerialNumber, Issuer}
|
