> On 18 Jun 2019, at 13:46, Angel Bosch Mora wrote:
>
>> The feature doesn't exist yet, so if you write a PEM -> NSS tool, the
>> project would love to accept it to our source code. It's been
>> something I have wanted for a while, and recently I have been
>> thinking with containers I should
William Brown wrote:
On 18 Jun 2019, at 13:41, Angel Bosch wrote:
However, be mindful that the if you use attribute encryption, this
value is stored in the key3.db, and replacement of this file WILL
destroy your access to your own database! IE if you plan to use this
strategy, you MUST NOT
> The feature doesn't exist yet, so if you write a PEM -> NSS tool, the
> project would love to accept it to our source code. It's been
> something I have wanted for a while, and recently I have been
> thinking with containers I should more seriously develop it, but if
> you wanted to add this, we
> On 18 Jun 2019, at 13:41, Angel Bosch wrote:
>
>> However, be mindful that the if you use attribute encryption, this
>> value is stored in the key3.db, and replacement of this file WILL
>> destroy your access to your own database! IE if you plan to use this
>> strategy, you MUST NOT use
> However, be mindful that the if you use attribute encryption, this
> value is stored in the key3.db, and replacement of this file WILL
> destroy your access to your own database! IE if you plan to use this
> strategy, you MUST NOT use attribute encryption at the same time.
>
I'll take that into
Hi there,
NSS databases are made from 3 files:
cert8.db
key3.db
secmod.db
If you are using the newer sqlite format, it's:
cert9.db
key4.db
pkcs11.txt
389 will "prefer" the newer format if present, and there is an automatic
upgrade process in NSS. I'm not sure when NSS will swap by default,
