Pale Moon forum

http://servicearizona.com/

Click the top left option "Renew..." and I get a half finished page. PM-Safe Mode same problem, FFx49 works OK. PM-v24xxx worked fine.

I checked the webpage for W3 compliance and it is all over the place, but Government dept not likely to change any time soon. This is not progress.

Government having security not in order again. They SHOULD care.
The BASE being set to https means the style sheets should be pulled from https, as well as the other style sheets indicating https. There's no cypher overlap there. SSL testing shows that the server indicates support for aes-gcm but only with RSA key exchange which is not commonly implemented in clients, and otherwise supports only 3DES (and prefers it). That will fail in Pale Moon because it's been disabled for SWEET32.
In addition, it seems to bounce right back to the http equivalent on the server so this BASE indication is only breaking things here and otherwise doesn't even have a use

If they set up their https server properly, this will be fixed. if they don't try to enforce https in their BASE tag, this will be fixed as well, but the former is preferred, of course...

ThirdTryCharm wrote:http://servicearizona.com/

Click the top left option "Renew..." and I get a half finished page.

Clicking on that "Vehicle Registration Renewal" button I get the following: ... Is this what it should look like? ... and is not what you get? (since you describe a "half finished page")

There's a button near the bottom of this page that says "Begin Vehicle Registration Renewal", but then I get a "secure connection failed" page when clicked on. (advising the user to contact the website owners regarding the problem)

Pale Moon Rising wrote:Clicking on that "Vehicle Registration Renewal" button I get the following: What I get clicking the renew button.png... Is this what it should look like? ... and is not what you get? (since you describe a "half finished page")

The unfinished look is a direct and correct result of the style sheets issues just described by Moonchild.

satrow wrote: The unfinished look is a direct and correct result of the style sheets issues just described by Moonchild.

Got it, thanks for the heads-up satrow

Nope, this is what it looks like in FFx and used to look like in 24...

It's incorrect in Pale Moon because of what I already explained.
Firefox and earlier Pale Moon don't disable 3DES.

Moonchild wrote:It's incorrect in Pale Moon because of what I already explained.

I only posted it as you had asked what it should look like!

To me, there are more and more websites I have to use FFx for, so there seems little point in staying with PM and I am unhappy with the prospect of being forced back to FFx.

Do you have to be so rigid with what you will allow and what not?

Could you make it an about:config option, maybe with a suitable warning for allowing reckless user-behavior?

Firefox disable 3DES too so the result is the same.
You need to contact the website admin so they can fix that bad SSL/ TLS security.

But you can of course use less secure browsers if you want a connect at all cost, like Firefox does with many stuff.

Moonchild wrote:Government having security not in order again. They SHOULD care.

Agreed, they SHOULD definitely care, but then we are talking about "Government" and I'd say we should be able to all agree for the most part that to expect Government work anywhere around the world to be at the forefront of technology is a specious expectation simply based on revenue issues specifically involving the way Government work is in general funded. (and let me say right up front, as I've always said, I am totally sympathetic to the issue regarding websites that do not properly code to standards and absolutely agree that they should, period!)

I'm assuming that the v27 build is not going to make a difference.... I would add the caveat that the issue doesn't impact our household personally as we don't live in Arizona. That said, every State in the U.S. will necessarily have totally different State Vehicular Registration websites based on the concept of State Sovereignty so I for one can certainly see the potential for numerous issues arising from time to time with this in mind. As far as I'm aware the State we reside in does not have this issue with Pale Moon, but then we do not register on-line. (presumably more States than one might reasonably expect do presumably work actually )

dark_moon wrote:Firefox disable 3DES too so the result is the same.

FWIW, out of curiosity I checked and as far as I can see the website does work in FF (even w/out my "allowing" the site in NoScript): That is not to say your points are not valid ones however

Did you notice the big "IBM" in the lower right corner? Suggests they are in good hands.

I have no idea how to contact the Government in a meaningful way that could actually get the thing looked at. Plus, I don't understand enough about it to discuss it with anyone such that they would take the issue seriously enough. Contacting the webmaster, (if there is a link) would probably fall on deaf ears while they covered their collective arses anyway if it is as bad as suggested here.

It is NOT an Arizona issue, we can't use PM with two banks and two credit card sites and that list is growing. I am not going back to FFx because I want to, it is because we cannot access a growing number of sites with PM. I am sure it is all done by Moonchild with best of intentions, but we need access to those accounts and the vehicle-reg is just another site that has been added to the restricted list for PM.

dark_moon wrote: Firefox disable 3DES too so the result is the same.

I was going to let that one pass, dark_moon, I am not making this stuff up and would never say it was working in FFx if I hadn't just tested it before taking that screen shot. If you check the Exif-time on that pic it will be within minutes of when I posted it.

ThirdTryCharm wrote: I have no idea how to contact the Government in a meaningful way that could actually get the thing looked at. Plus, I don't understand enough about it to discuss it with anyone such that they would take the issue seriously enough. Contacting the webmaster, (if there is a link) would probably fall on deaf ears while they covered their collective arses anyway if it is as bad as suggested here.

I totally agree, you will very likely get nowhere even if you can figure out a way to actually contact anyone who would have any impact on the way things are done on the technical end. Government works within a different time-frame than the rest of us as far as getting anything done, I would add that any relatively large corporation is not much better these days.

ThirdTryCharm wrote: It is NOT an Arizona issue, we can't use PM with two banks and two credit card sites and that list is growing. I am not going back to FFx because I want to, it is because we cannot access a growing number of sites with PM. I am sure it is all done by Moonchild with best of intentions, but we need access to those accounts and the vehicle-reg is just another site that has been added to the restricted list for PM.

I totally understand your frustration with websites that fail to work using Pale Moon and you have made it equally clear that you just as I do as well not to mention all of the rest of the loyal supporters of Pale Moon all totally understand the dilemma facing the Pale Moon development team as far as dealing with websites that unfortunately practice negligent coding standards. That said, we also understand from the perspective of the "casual" user (which is the vast majority) that it is imperative the browser simply needs to work for these types of critical websites that people use in everyday life and any explanations about the "whys" for purposes of detailing the reasons websites fail to work for the most part tends to fall on "deaf ears" as just irrelevant tech "noise" in contrast to users needs.

As a die-hard Pale Moon user I'm past switching to anything else myself and therefore as such am totally sold on Pale Moon to the extent that I do not foresee ever even contemplating at any level a change at this point. You've made it very clear how much you would regret making a change as well. For these very reasons I've been using the Open With 5.6.3.1-signed add-on since introduced to this extension which thankfully provides me a way to always use Pale Moon as my default browser and most importantly never leave Pale Moon unless I absolutely have to when I might occasionally run across one of these type of sites that are problematic at which time it's a matter of just one-click to open up the problematic website in another of my backup browsers but otherwise be able to exclusively use Pale Moon.

The good news is that there is evidence that many of these problematic websites will be "fixed" as a result of the mile-stone 27 release of Pale Moon!

ThirdTryCharm wrote:Do you have to be so rigid with what you will allow and what not?
Could you make it an about:config option...?

It already is an about:config option.
In about:config, filter on des_ede -- it will bring up the 3DES cipher prefs, which you can toggle to "True" if you choose.

Please also see this FAQ: Secure connection errors? **READ THIS FIRST!** (point 4) and scroll down to the section starting with "For point 4: 3DES" for detailed instructions on how to enable these ciphers on a provisional basis.

ThirdTryCharm wrote:

Moonchild wrote:It's incorrect in Pale Moon because of what I already explained.

I only posted it as you had asked what it should look like!

Oooops, my mistake, sorry, Moonchild didn't ask, Pale Moon Rising did.

I sometimes make a mistake.

ThirdTryCharm wrote: I sometimes make a mistake.

I know for sure that I certainly do.