UserParameters attribute of a user object in Active Directory messing up the event detail in Event Viewer in Windows Server 2012.

/0 Comments/in /by
In Active Directory, userParameters attribute of a user object is used to store the terminal profile setting for a user.  Turns out that the userparameters attribute stores the terminal profile data in binary format.
Yesterday, I was working on an application where there was a requirement to read the Windows Event log to get the audit data for changes in Active Directory.  So I open the Windows Server 2012 Event Viewer to see the log for Active Directory User updates. In Event Viewer screen, following error message is showing in details view of event Meta data. Reason for this error is that event viewer is unable to parse the userParameters blob data. But this problem is only happening with Windows Server 2012 not with Windows Server 2008.

In Active Directory, userParameters attribute of a user object is used to store the terminal profile setting for a user.  Turns out that the userparameters attribute stores the terminal profile data in binary format.  Yesterday, I was working on an application where there was a requirement to read the Windows Event log to get the audit data for changes in Active Directory.  So I open the Windows Server 2012 Event Viewer to see the log for Active Directory User updates. In Event Viewer screen, following error message is showing in details view of event Meta data. Reason for this error is that event viewer is unable to parse the userParameters blob data. But this problem is only happening with Windows Server 2012 not with Windows Server 2008.

Event Viewer of Windows Server 2012

CionSystems Products Are Not Vulnerable to The Heartbleed Bug

/0 Comments/in /by

CionSystems products are not vulnerable to the Heartbleed bug:

General Information
The “Heartbleed Bug” is a security flaw in OpenSSL’s TLS implementation.  SSL/TLS provide secure the transmission for private information. The bug is actually a memory leak exploit that can potentially lead to the exposure of server keys.  This can result disclosure of private computer memory and private information. It is indeed a very serious vulnerability.
How to diagnose if your systems are vulnerable:
To determine if your systems are vulnerable to the Heartbleed bug, see http://www.kb.cert.org/vuls/id/720951
How to fix systems that are vulnerable to Heartbleed *and* the potential loss of private keys:
If you find any of your systems vulnerable to the Heartbleed bug, the steps typically involved in fixing a system include:

  1. Patching vulnerable systems with OpenSSL 1.0.1g
  2. Regenerating new private keys
  3. Submitting new CSR to your CA
  4. Obtaining and install new signed certificate
  5. Revoking old certificates

Exercise caution when revoking certificates as some systems may become inaccessible.