Hello Bob,
I've looked a bit further into the code today, and though you already
explained me those things, let me write them again in order to see if I
understood the idea:
1. Starting point:
The problem with nsSDR is that you can't choose another slot/token than the
internal one if one wants to use another storage location for his/her
encryption keys. nsSDR.cpp uses PK11_GetInternalKeySlot() at line 149
without the possiblity to choose.
2. A good solution:
I could modify nsSDR in order to be able to "browse" between all available
"PK11SlotInfo" and "NSSToken" objects, and have e.g. a GUI to ask the user
which slot / token he or her wants to use, or use the
cryptography-module-manager-window to mark the one that should be used by
default. (I have no clue how window-classes are to be implemented in XPCOM
at this point)
3. A more difficult point:
The difficulty is to implement the "browsing" of a slot-list, specially to
find the right key to use to PK11SDR_Decrypt() the login names and pwds.
Please tell me, if I understand the problem correctly, why isn't that
functionality not already implemented? I asked to myself, NSS is a complexe
and relatively old component I guess, why did nobody do that already?
Someone who is used to XPCOM/NSS could do that in a few... well... minutes?
And I'm going to need... weeks :-D
Marc
--
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto
