Message45757
Logged In: YES
user_id=973611
> - I can't find a statement on the page you link about using
> CRYPT_VERIFYCONTEXT that way,
Note that retrying on NTE_BAD_KEYSET is only described under
the heading "Private Key Operations Are Performed", in
which case you need to open/create a private key container.
But if you use CRYPT_VERIFYCONTEXT it just creates a
temporary context in memory. More corroboration:
http://tinyurl.com/2ct2o
For awhile I was distributing code without
CRYPT_VERIFYCONTEXT, and a user ran into the NTE_BAD_KEYSET
error. But CRYPT_VERIFYCONTEXT fixed it, which is how I
stumbled on this...
> - One more important issue: It is a bad idea to use stdio
> (C's 'fopen', Python's builtin 'open') to read from
> /dev/urandom.
Good point. I've tried to update the code to use syscalls.
Is there any chance you could test this out, and see
whether the #includes look correct and portable? I don't
have a UNIX box available. If it needs fixes, feel free to
upload a new version. |
|
Date |
User |
Action |
Args |
2007-08-23 15:37:10 | admin | link | issue934711 messages |
2007-08-23 15:37:10 | admin | create | |
|