Logged Error

[batmike]

I keep getting thousands of this one error:

Date; Severity; Message; Debug Data
7/23/2008 8:37:05 PM; Error; Error decrypting data; Invalid character in a Base-64 string.

Anyone have any idea what might be going on? It doesn't seem to be interrupting anything, but I can't imagine what it's trying to do that it keeps piling up all these errors.

Thanks!
Mike

[batmike]

No ideas? It happened a lot over the weekend, when I'm not checking it as often.

[WylieE]

We just got a whole slew of these error messages this evening. It was over a three minute period and then stopped.

We turned on encryption yesterday before going live. Could this be related? Any info would be appreciated. An error is making us hyper concerned during the first few days of our rollout.


Thanks.

[batmike]

It's pretty much been narrowed down to HackerSafe/McAfee Secure - when it scans your site it'll generate all these errors. The fix is supposed to be incorporated into the 7.2 update.

If you don't have McAfee Secure, then I'm not sure what could be causing it ...

[WylieE]

It's pretty much been narrowed down to HackerSafe/McAfee Secure - when it scans your site it'll generate all these errors. The fix is supposed to be incorporated into the 7.2 update.

If you don't have McAfee Secure, then I'm not sure what could be causing it ...

OK, we do use McAfee Secure and were scanned yesterday. That's a load off my mind.

[Brewhaus]

We rarely check our error log (I know, I know) as we rarely had many errors to show. Due to a different issue we checked, and have literally tens of thousands of these errors ever since we entered an encryption key. There are so many of these errors that we cannot delete them using the Delete All option in AC. Is it safe to simply delete them directly from the SQL table?

And we are updating to 7.0.2 as soon as we clear the table. Has anyone confirmed that 7.0.2 has resolved this issue?

[Logan Rhodehamel]

Is it safe to simply delete them directly from the SQL table?

And we are updating to 7.0.2 as soon as we clear the table. Has anyone confirmed that 7.0.2 has resolved this issue?

Yes, you can delete them from the table. The logging of this particular error was unfortunate, it made sense at the time because we wanted to be sure our custom encryption/decryption was always working properly. But we did not anticipate the false positives - McAfee and tools like it are throwing in bad data on purpose. Our decryption isn't actually failing... the input is bad.

In 7.0.2 we stopped logging this "error".