On 2010-07-19 10:56 PDT, Caden.smith Smith wrote:
> Just for your information, here is the tree:
>
> JSS4.DLL
> NSPR4.DLL
> ADVAPI32.DLL
The factors under the control of the way in which JSS and NSPR are built
end here. Anything below this point has NOTHING to do with them.
Everything be
Hi Cad,
On Mon, Jul 19, 2010 at 10:56 AM, Caden.smith Smith
wrote:
>
> Just for your information, here is the tree:
>
> JSS4.DLL
> NSPR4.DLL
> ADVAPI32.DLL
> SECUR32.DLL
> NETAPI32.DLL
> DNSAPI.DLL
> MPRAPI.DLL
> SETUPAPI.DLL
> SHELL
I'll look into this tomorrow.
Just for your information, here is the tree:
JSS4.DLL
NSPR4.DLL
ADVAPI32.DLL
SECUR32.DLL
NETAPI32.DLL
DNSAPI.DLL
MPRAPI.DLL
SETUPAPI.DLL
SHELL32.DLL
SHDOCVW.DLL
I can suggest two things to help track this down.
1. Find out which DLLs require IESHIMS.DLL and WER.DLL.
This should be a chain of DLL dependencies that ultimately
leads to an NSS or NSPR DLLs (the "culprit"). Right now I
don't know what the culprit is.
The NSPR DLLs are:
nspr4.dll, plc4.dll, p
Hello
Sorry to revive the thread but I find the same problem.
I went to see why the referred libs don't exist in Windows XP and the
explanation is quite simple. for instance:
http://stackoverflow.com/questions/2465111/dependency-walker-reports-ieshims-dll-and-wer-dll-missing
However, I used a Wi
Hello, Nelson.
Thank you for detailed answer.
I am very curious about:
FIPS 140 will not allow *any* hardware pure noise source to be used by itself
as a random number/bit source. Instead, such a source MUST be fed into a DRBG
from which any internal random data is taken.
The statement abo
6 matches
Mail list logo
