LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   HTTPS not working correctly in Chrome and Chromium... (https://www.linuxquestions.org/questions/linux-software-2/https-not-working-correctly-in-chrome-and-chromium-4175600599/)

ardvark71 03-16-2017 10:49 PM

Quote:

Originally Posted by X-LFS-2010 (Post 5684503)
it's probably rejecting you by having detected your a file shark.

Hi...

Thank you for your reply. I'm not sure what you mean by "file shark."

Quote:

Originally Posted by X-LFS-2010 (Post 5684503)
if that don't work use a "real OS" that compiles firefox from scratch without allot of headaches or build failures. it should be working then.

if not: then perhaps your authentication libraries are used by firefox and have become changed (ie, openssl). unfortunately, there are so many auth mechs these days (not just openssl: tens or hundreds of knotted auth libs PLUS kernel auth support PLUS hardware auth support)

But why does my copy of Firefox work correctly but Chrome and Chromium does not. :confused:

Quote:

Originally Posted by X-LFS-2010 (Post 5684503)
back up from this problem: don't get so close it swallows you. try the version of firefox (chrome flavor) that last worked first.

Nah, it's not worth that. :D

My copy of Chrome and Firefox are "original," meaning there were no previous versions.

Regards...

TB0ne 03-17-2017 09:08 AM

Quote:

Originally Posted by ardvark71 (Post 5684555)
But why does my copy of Firefox work correctly but Chrome and Chromium does not. :confused:

Sorry, but what are you confused about still??? Posts #2, #7, #11, #22, #23, and #28 all explain why you're having issues. What, exactly, are you confused about? What is not/has not been clear in any or all of these explanations???

Upgrade your OS, period. That's it. You're getting this problem because of the age of the cryptographic libraries, and the age of the browser. Can't update browser unless you compile from source, and even then you will STILL HAVE THE PROBLEM because your crypto libraries will STILL BE OLD.

ardvark71 03-17-2017 10:00 PM

Quote:

Originally Posted by TB0ne (Post 5684704)
Sorry, but what are you confused about still??? Posts #2, #7, #11, #22, #23, and #28 all explain why you're having issues. What, exactly, are you confused about? What is not/has not been clear in any or all of these explanations???

Hi...

In part because my copy of Chrome version 49 works fine on Windows Vista, an even older OS.

Quote:

Originally Posted by TB0ne (Post 5684704)
Upgrade your OS, period. That's it. You're getting this problem because of the age of the cryptographic libraries, and the age of the browser. Can't update browser unless you compile from source, and even then you will STILL HAVE THE PROBLEM because your crypto libraries will STILL BE OLD.

Yes, I understand that I will need to upgrade Lubuntu. Since that seems to be the only known solution, I'll go ahead and mark this thread as "SOLVED."

Thanks...

TB0ne 03-18-2017 10:41 AM

Quote:

Originally Posted by ardvark71 (Post 5684963)
Hi...
In part because my copy of Chrome version 49 works fine on Windows Vista, an even older OS.

Because Windows Vista reaches end-of-life in April of 2017. Lubuntu 14.04 reached end of life April 2016. Do you see the difference???? If that's not clear enough:
  • Windows Vista received upgraded crypto libraries
  • Lubuntu 14.04 DID NOT receive upgraded crypto libraries.
Checking end-of-life on software, reading release notes, and doing research are all things you can do for yourself.
Quote:

Yes, I understand that I will need to upgrade Lubuntu. Since that seems to be the only known solution, I'll go ahead and mark this thread as "SOLVED."
If you really did understand that, there wouldn't be three pages on this thread, with the last one still having you 'confused'.

ardvark71 03-19-2017 06:25 PM

Quote:

Originally Posted by TB0ne (Post 5685146)
Lubuntu 14.04 reached end of life April 2016

Hi...

No, support ends at some point this year, according to this page.

Regards...

TB0ne 03-19-2017 08:43 PM

Quote:

Originally Posted by ardvark71 (Post 5685659)
Hi...
No, support ends at some point this year, according to this page.

Nice that you mention you're using LTS now. Regardless, changes nothing....You don't have the libraries, and won't. Even if you want to split hairs and be "confused", it's EOL next month.

ardvark71 03-20-2017 01:10 AM

Quote:

Originally Posted by TB0ne (Post 5685691)
Nice that you mention you're using LTS now.

Hi...

You didn't know that 14.04 is LTS? As it stands, unless someone knows exactly how to fix this issue, the solution is to upgrade.

Regards...

TB0ne 03-20-2017 08:14 AM

Quote:

Originally Posted by ardvark71 (Post 5685754)
Hi...
You didn't know that 14.04 is LTS?

Nope, because Lubuntu 14.04 was the ONLY LTS version until 16.04. All other versions didn't even have the option, and you sure didn't mention it.
Quote:

As it stands, unless someone knows exactly how to fix this issue, the solution is to upgrade.
You were told NUMEROUS times how to fix it, but you either didn't read or understand the fixes. Post #2 tells you how to get this 'patched' at the very least, and post #7 follows it up. You even posted that the command-line configuration was an option (post #3), but either didn't run it, or ignored it.

The real solution is, as explained to you numerous times, is to upgrade. Nothing to be confused about, and don't know how many more times folks need to tell you this, especially since you ran your own test with a newer version of Linux and thing worked fine, proving the theory.

txslnx 05-09-2017 09:50 PM

Quote:

Originally Posted by ardvark71 (Post 5685754)
Hi...

You didn't know that 14.04 is LTS? As it stands, unless someone knows exactly how to fix this issue, the solution is to upgrade.

Regards...


I had this happen to me in 16.02 and 17.04. Both times it was a certificate problem with Chromium. Removing it and installing Chrome "fixed" it.

ardvark71 05-10-2017 01:08 AM

Quote:

Originally Posted by txslnx (Post 5708428)
I had this happen to me in 16.02 and 17.04. Both times it was a certificate problem with Chromium. Removing it and installing Chrome "fixed" it.

Hello and welcome to the forum :)

Thank you for registering to share this with me. In my case, the problem is with both Chrome and Chromium, although installing a slightly newer version of Chrome might be worth trying. :) :thumbsup:

Regards...

ardvark71 05-17-2017 07:55 AM

Hi all...

Ohhh, yeahhhh!! I finally got this problem entirely fixed without having to upgrade the OS! From what I found here, one command took care of it all...

Code:

sudo apt-get install libnss3-1d
Now both Chrome and Chromium work as they should! I probably would have never come across this had I not upgraded Chromium to version 58 and suddenly come across the error practically everywhere I tried to go. :) :thumbsup:

Regards...

Ztcoracat 05-17-2017 01:42 PM

Quote:

Originally Posted by ardvark71 (Post 5711790)
Hi all...

Ohhh, yeahhhh!! I finally got this problem entirely fixed without having to upgrade the OS! From what I found here, one command took care of it all...

Code:

sudo apt-get install libnss3-1d
Now both Chrome and Chromium work as they should! I probably would have never come across this had I not upgraded Chromium to version 58 and suddenly come across the error practically everywhere I tried to go. :) :thumbsup:

Regards...

That's great news. Congrads!

TB0ne 05-17-2017 02:16 PM

Quote:

Originally Posted by Ztcoracat (Post 5711953)
That's great news. Congrads!

I wouldn't call spending three months on solving a problem with old, outdated software something to be congratulated about. Especially since doing a fresh install would've taken about 30 minutes.

And he's still left with an outdated system that's EOL. Pointless.

rtmistler 05-17-2017 02:18 PM

error post - apologies

jeremy 05-17-2017 02:23 PM

@TB0ne, that post is in no way constructive and adds nothing to the conversation that you haven't already said. I've asked you multiple times to refrain from this kind of behavior.

-jeremy


All times are GMT -5. The time now is 09:08 AM.