Minor documentation fixes, PR#2345
This commit is contained in:
parent
f10986bab4
commit
84f1c14396
1 changed files with 1 additions and 1 deletions
|
@ -373,7 +373,7 @@ should be some heuristic that determines the correct encryption certificate.
|
|||
Ideally a database should be maintained of a certificates for each email address.
|
||||
|
||||
The code doesn't currently take note of the permitted symmetric encryption
|
||||
algorithms as supplied in the SMIMECapabilities signed attribute. this means the
|
||||
algorithms as supplied in the SMIMECapabilities signed attribute. This means the
|
||||
user has to manually include the correct encryption algorithm. It should store
|
||||
the list of permitted ciphers in a database and only use those.
|
||||
|
||||
|
|
Loading…
Reference in a new issue