Yes, you can use Chromium Legacy as your main browser. I do. That said, you should turn off the V8 optimizer until Chromium Legacy is next updated. Yes the vulnerability is serious, but it goes away completely if the "optimizer" is disabled.But i'm super paranoid about safety and security, and my question is, can I use chromium legacy as the only browser on my mac? Are there any vulnerabilities/threats I should know about? Can I safely sign into it and other websites with my accounts?
My PrefPane adds automatic updates (although there have not been many updates lately, but at one point there were and maybe there will be again), and other workarounds for various bugs or design inconsistencies. I recommend using the PrefPane if you are on OS X 10.7 – 10.9. I don't test the PrefPane on anything newer than that, so please don't use it on any OS past 10.9, except maybe 10.10 where lots of people have reported success.1) What is wowfunhappy's preference pane? What is it for?
Oh i'm only paranoid because a lot of devices get hacked in my country, and my mac is pretty old, has a lot of my personal data. Nothing too serious. Btw as I specified earlier, its not my main laptop. My main is a 2015 Mbp.Yes, you can use Chromium Legacy as your main browser. I do. That said, you should turn off the V8 optimizer until Chromium Legacy is next updated. Yes the vulnerability is serious, but it goes away completely if the "optimizer" is disabled.
That said, as much as I obviously adore classic OS X, if you are truly "paranoid" about security you should be using an up-to-date operating system! I don't know why you are "paranoid", but if it's because you could potentially be subject of a targeted attack—if you have access to data or information which would make a skilled hacker want to put money and resources into attacking you specifically, over and above just some random person—please update your operating system or get a new computer (and turn on Apple's advanced protection while you're at it).
I'm using Firefox 131 in Mavericks, but this probably needs to be discussed in the other thread, as this is for Chromium.To those who have said Firefox 115esr has reached end of life that is not true it ends in October so theres about another three weeks and there is another build to address a few more vulnerabilities before it kicks the can(friend works for Mozilla)….link to eol dates here for all esrs
No, I meant to post it here because others were discussing different options and going back and forth about when it ends, and I wanted to correct them since this has come up multiple times in this thread. I appreciate your input, but I’ll post where I want to, just like you can. If an admin asks me to post elsewhere, I’ll adhere to that, but you're just a regular user like me, so it's not for you to tell others where or what to post. I hope you have a good day, and stay blessed, friend.I'm using Firefox 131 in Mavericks, but this probably needs to be discussed in the other thread, as this is for Chromium.
Look, it's a web browser. At the moment it's still able to browse the web capably, with basically zero website compatibility issues. Enjoy it, or don't. But I would encourage everyone to stop worrying about what may or may not happen in the future. There's just no point.And let’s be real here...
You see, this is the whole problem for me. There are several reasons why I still use Mavericks, one of which is that I can stream live TV using legacy browsers. Being disabled, it’s more comfortable to watch on my computer than anywhere else. That was the whole reason I discovered and started using Chromium Legacy.Widevine compatibility is a ticking time bomb no matter what. This has nothing to do with Bluebox or Chromium Legacy. Widevine is closed source, and the fact that it works/worked on Mavericks is a happy accident.
For my part I just avoid DRM'd video sources. It helps that I don't really watch TV.
Look, it's a web browser. At the moment it's still able to browse the web capably, with basically zero website compatibility issues. Enjoy it, or don't. But I would encourage everyone to stop worrying about what may or may not happen in the future. There's just no point.
There is at least one other project under active development to port a fully modern web browser to Mavericks, so I'm not too worried about being stuck. (But I would really prefer that this thread focused on Chromium Legacy specifically, thank you!)
By the way, "Widevine working in Mavericks" is not correct: Wv is not an OS feature, it's a BROWSER feature - i.e. whenever Wv is updated, each browser (whether Safari, Firefox, Chrome, Edge, whatever) gets their own component of it. If I invoke Chromium/settings/components and scroll down, it tells me that Wv is "up to date" when in fact it's not. Unfortunately I can't run the latest version of any browser that's not a GitHub project, so I don't know what the up to date version number is, not that it would make much difference if I did know as there's nothing I can do about it.Widevine compatibility is a ticking time bomb no matter what. This has nothing to do with Bluebox or Chromium Legacy. Widevine is closed source, and the fact that it works/worked on Mavericks is a happy accident.
It is a browser feature, but it isn't a part of the browser. Widevine is a separate binary—a separate program, a so-called "binary blob"—provided by Google. The widevine binary is closed-source and resistant to tampering. If it is no longer compatible with a given OS, there is a limited amount anyone can do. (It is still possible that some small hack will get it working again, but I wouldn't count on it.)Wv is not an OS feature, it's a BROWSER feature - i.e. whenever Wv is updated, each browser (whether Safari, Firefox, Chrome, Edge, whatever) gets their own component of it.
chrome://components/
says Widevine is up-to-date, it probably is, but that doesn't mean the most-recent Widevine binary actually works on Mavericks. Firefox uses the same Widevine binary blob that Chromium does. I understand that it's a problem for you and I sympathize, I just don't know that it can be fixed! As we all agree, this is why DRM totally sucks.You see, this is the whole problem for me.
Actually, I do use VMs! The highest I can go in Mavericks is a High Sierra (Parallels) VM which I've just upgraded to from Sierra. Unfortunately, even High Sierra is now way out of date, and won't run the latest versions of Safari, Chrome, or Firefox. However, it DOES run Firefox 115 ESR which does stream DRM video, so for now, I'm good.I understand that it's a problem for you and I sympathize, I just don't know that it can be fixed! As we all agree, this is why DRM totally sucks.
The one thing I could potentially suggest is using a Virtual Machine to watch Netflix. VMWare Fusion and Parallels have desktop integration features that will make using a web browser inside a VM relatively seamless with your Mac. If you need a Mavericks-compatible copy of VMWare Fusion, please send me a PM.
You will have soooo much more success virtualizing Windows than virtualizing macOS! VMWare and Parallels and invested much more time into making Windows guests work smoothly, and the difference is night and day.Actually, I do use VMs! The highest I can go in Mavericks is a High Sierra (Parallels) VM
Realize that you want to keep this discussion limited to Chromium Legacy. Forgive me, but can't resist asking about firefox-dynasty:There is at least one other project under active development to port a fully modern web browser to Mavericks, so I'm not too worried about being stuck. (But I would really prefer that this thread focused on Chromium Legacy specifically, thank you!)
I answered here: https://forums.macrumors.com/threads/web-browsers-for-early-intel-macs.2280783/page-10Realize that you want to keep this discussion limited to Chromium Legacy. Forgive me, but can't resist asking about firefox-dynasty:
Do you think it's ready for prime time (the developer's somewhat off-putting hip hop style comments not withstanding)? And do you know if it will run in High Sierra?
Remember that now, thanks. Still pretty buggy, so will pass.
Never mind buggy - it doesn't have the latest Widevine (I've reported that on GitHub) so won't stream TV or DRM video. Yet Firefox 115 ESR has been converted so for now that's what I'm having to use.Remember that now, thanks. Still pretty buggy, so will pass.
Unfortunately, there's no version of Windows that can compare with Mavericks!You will have soooo much more success virtualizing Windows than virtualizing macOS! VMWare and Parallels and invested much more time into making Windows guests work smoothly, and the difference is night and day.
I'm suggesting you use Mavericks as the host and Windows as the guest. It's basically the only option I know of to get Widevine working.Unfortunately, there's no version of Windows that can compare with Mavericks!
That means I'd have to buy Windows!I'm suggesting you use Mavericks as the host and Windows as the guest. It's basically the only option I know of to get Widevine working.
You can always use it deactivated, and you can always activate using MASThat means I'd have to buy Windows!
I've had a quick look at that website - I may come back and ask you for more details if (when) Widevine fails in Firefox 115 ESR.You can always use it deactivated, and you can always activate using MAS
Isos for older oses, like xp, vista, 7 and 8.1 are also available on their website
massgrave.dev
Again, Widevine is not a part of the browser, it's a separate binary. And unfortunately, it's not open source.Even if only getting the Widevine update, it would make the browser 100% more usable.