NSS: Collect additional info when public_slot is null
One of the theories why NSS might fail to open the
public slot is if something is wrong with the filesystem.
Add additional debug code for diagnosing the issue and move
the CHECK closer to where the problem actually occurs.
Example output:
Check failed: false. Public slot is invalid.
NSS path: /home/chronos/u-3a3b35f75b9fff436fe702dbd010ff696ee069dc/.pki/nssdb
Public slot database files:
pkcs11.txt, 100644, 500 bytes, readable
cert9.db, 100444, 28672 bytes, readable
key4.db, 100644, 36864 bytes, readable
Enumerate error code: 0
nssdb, 40750
Enumerate error code: 0
.pki, 40750
Enumerate error code: 0
NSS path exists.
Bug: 1163303
Test: Manual
Change-Id: I133ce2b743827aa5ffe2b9d4059af8b5228bfc3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3592993
Auto-Submit: Michael Ershov <miersh@google.com>
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/main@{#994444}
NOKEYCHECK=True
GitOrigin-RevId: 0d751203a84df5a4f26f169dc71b24ae86ff2dbe
3 files changed
