"Message Authentication Code" problem
The Real Bev
generally (not always) get the following message each time, and for some
sites it pops up whenever I change pages. Googling and the mozilla
knowledge base have been no help.
"<website> received a message with incorrect Message Authentication Code.
If the error occurs frequently, contact the website administrator."
Somehow I don't think this is the website admin's problem. I have both SSL
3.0 and TLS 1.0 checked, which was one person's proposed solution. Nope.
Nor do I use OCSP for certificate validation. It happens with privoxy
selected or deselected. No software firewall, just the switch/router which
was the same before I upgraded.
Ideas?
--
Cheers, Bev (Happy Linux User #85683, Slackware 11.0)
===========================================
Lawyering: the only profession that if you
didn't have it you wouldn't need it.
The Real Bev
> Thunderbird Leader The Real Bev teletyped, On 8/30/2007 7:35 PM:
>> Since I upgraded to 2.0.0.6, when I visit a site that requires a
>> login, I generally (not always) get the following message each time,
>> and for some sites it pops up whenever I change pages. Googling and
>> the mozilla knowledge base have been no help.
>>
>> "<website> received a message with incorrect Message Authentication Code.
>> If the error occurs frequently, contact the website administrator."
>>
>> Somehow I don't think this is the website admin's problem. I have
>> both SSL 3.0 and TLS 1.0 checked, which was one person's proposed
>> solution. Nope. Nor do I use OCSP for certificate validation. It
>> happens with privoxy selected or deselected. No software firewall,
>> just the switch/router which was the same before I upgraded.
>>
>> Ideas?
>>
> Those may be old sites still using SSL2. Try filtering on SSL2 in
> Config Editor and turning on SSL2 and any of it's encryption keys that
> are false. Skip those with 'null' in the name. Tb 2.0.0.x shipped with
> SSL2 set false.
Done! Maybe it IS the admins' problem.
Now let's see what happens... OK, I got the message at my bank's site. I
restarted FF, logged in to the bank and got NO message. So far so good!
--
Cheers, Bev (Happy Linux User #85683, Slackware 11.0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Nobody ever went broke underestimating the intelligence of the
American Public." -- H.L. Mencken
The Real Bev
> Ron K. wrote:
>
>> Thunderbird Leader The Real Bev teletyped, On 8/30/2007 7:35 PM:
>>> Since I upgraded to 2.0.0.6, when I visit a site that requires a
>>> login, I generally (not always) get the following message each time,
>>> and for some sites it pops up whenever I change pages. Googling and
>>> the mozilla knowledge base have been no help.
>>>
>>> "<website> received a message with incorrect Message Authentication Code.
>>> If the error occurs frequently, contact the website administrator."
>>>
>>> Somehow I don't think this is the website admin's problem. I have
>>> both SSL 3.0 and TLS 1.0 checked, which was one person's proposed
>>> solution. Nope. Nor do I use OCSP for certificate validation. It
>>> happens with privoxy selected or deselected. No software firewall,
>>> just the switch/router which was the same before I upgraded.
>>>
>>> Ideas?
>>>
>> Those may be old sites still using SSL2. Try filtering on SSL2 in
>> Config Editor and turning on SSL2 and any of it's encryption keys that
>> are false. Skip those with 'null' in the name. Tb 2.0.0.x shipped with
>> SSL2 set false.
>
> Done! Maybe it IS the admins' problem.
>
> Now let's see what happens... OK, I got the message at my bank's site. I
> restarted FF, logged in to the bank and got NO message. So far so good!
Actually, it reverted to its previous behavior soon afterward. Today it
happened every time I switched pages at the Schwab website and got
annoyed enough to bitch again.
All the SSL2 entries are set to false, the default. I'm going to set
all entries to true and see what happens.
I'm running 2.0.0.11 now. Do ALL versions since 2.0.0.x reset these
entries?
--
Cheers, Bev (Happy Linux User #85683, Slackware 11.0)
*****************************************
"Don't force it, use a bigger hammer!"
--M. Irving
The Real Bev
This just in -- the problem still exists. Rebooted FF to make sure that
the SSL2 entries were still true. Yes. No joy.
--
Cheers, Bev (Happy Linux User #85683, Slackware 11.0)
===================================================================
Giving advice likely to kill the stupid is called passive eugenics
Rinaldi J. Montessi
I just ran an openssl query on Schwab. The following may be germane to
solving your problem:
New, TLSv1/SSLv3, Cipher is AES128-SHA
Rinaldi
--
"We are on the verge: Today our program proved Fermat's next-to-last
theorem."
-- Epigrams in Programming, ACM SIGPLAN Sept. 1982