T
Tom Allen
Guest
I have noticed in my Vista Home Premium Security log that every 30
seconds or so there are two events -
1. Key file operation
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: Not Available.
Key Name: A1 Client Cert key container
Key Type: Machine key.
Key File Operation Information:
File Path:
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\9c4d85b87d7ce4e2266e3ad33d98e11e_db08e080-c6f6-41c9-bd58-aaa574516add
Operation: Read persisted key from file.
Return Code: 0x0
2. Cryptographic operation.
Subject:
Security ID: SYSTEM
Account Name: ********$ (the system name)
Account Domain: ******* (the workgroup name)
Logon ID: 0x3e7
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: RSA
Key Name: A1 Client Cert key container
Key Type: Machine Key
Cryptographic Operation:
Operation: Open Key.
Return Code: 0x0
I don't think these used to appear but they exist in huge numbers from
the present beginning of the log on 30 Jan 2008.
Could anyone please explain this seemingly pointless and wasteful
sequence of events ?
Regards,
Tom Allen
seconds or so there are two events -
1. Key file operation
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: Not Available.
Key Name: A1 Client Cert key container
Key Type: Machine key.
Key File Operation Information:
File Path:
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\9c4d85b87d7ce4e2266e3ad33d98e11e_db08e080-c6f6-41c9-bd58-aaa574516add
Operation: Read persisted key from file.
Return Code: 0x0
2. Cryptographic operation.
Subject:
Security ID: SYSTEM
Account Name: ********$ (the system name)
Account Domain: ******* (the workgroup name)
Logon ID: 0x3e7
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: RSA
Key Name: A1 Client Cert key container
Key Type: Machine Key
Cryptographic Operation:
Operation: Open Key.
Return Code: 0x0
I don't think these used to appear but they exist in huge numbers from
the present beginning of the log on 30 Jan 2008.
Could anyone please explain this seemingly pointless and wasteful
sequence of events ?
Regards,
Tom Allen