Showing posts with label Firefox. Show all posts
Showing posts with label Firefox. Show all posts

July 01, 2021

Dear FireFox 89+, I hate your new Proton UI, especially tabs look/feel.

EDIT 2021-Aug-11:  FireFox 91 changed something, this no longer works 😠😡😠😡😠😡.  Please see https://support.mozilla.org/en-US/questions/1339768#answer-1434053


Problem: new Firefox tabs look horrible and do not stand out as visible tabs.



about:config > browser.proton.enabled > false  (no longer works in FF-91)

Fixed.




NEW SOLUTION:
1) Create a new folder/file in your user profile as chrome/userChrome.css
and fill it with contents (generated from your selected preferences) from this link: https://www.userchrome.org/firefox-89-styling-proton-ui.html#tabstyler
2) set toolkit.legacyUserProfileCustomizations.stylesheets as true via about:config .
3) restart FireFox.

example result: (https://sharetext.me/heyafkro)



SEO:
Fix FireFox 89, 90, 91 Tabs Look
Fix FireFox 89, 90, 91 Tabs Look and Feel
Fix Firefox Tabs
Fix FireFox Proton Tabs
Revert Firefox Tabs



Please consider crypto tipping:
  

December 05, 2017

LastPass Firefox Extension Repeatedly Asking for Two-Factor Authentication at Every Login

With the recent Firefox 57 release, I had experienced an annoying requirement with my LastPass add-on that required me to two-factor authenticate (2FA) each and every time I restarted Firefox.

At first, I saved a little effort by installing the Two-Factor Authenticator add-on so as to not require pulling my phone out constantly.
https://addons.mozilla.org/en-US/firefox/addon/two-factor-authenticator/

But really, i wanted this solved.

LastPass.com support suggested I purge my ~/.lastpass folder. I did so, but without resolve.

Other sources recommended purging two lastpass folders contained in the user profile:
~/.mozilla/firefox/YOURPROFILE/storage/permanent/indexeddb+++support-at-lastpass-dot-com/ , and
~/.mozilla/firefox/YOURPROFILE/jetpack/support@lastpass.com/
So i did; also without resolve.

More sources reported what I already suspected: The cookies that lastpass uses should not be deleted. So I made sure to whitelist lastpass.com and *.lastpass.com in my cookies cleaner.   In addition to Privacy > History > Keep Until they Expire.

This didn’t work immediately, so I dug into my FireFox preferences and found that un-checking “Offline WebSite Data” seemed to resolve my issue.  I had already unchecked "Cookies" and used "Cookies Auto delete" add-on to control cookies.
https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/?src=userprofile

So in hindsight, I believe the combination of saving the lastpass.com cookies and Edit(Tools) > Preferences(Options) > Privacy > History > Settings >
 [UN-CHECK] Offline Website data
 [UN-CHECK] Cookies
is the final solution.

Note: Upon removal/re-installation or auto-update of the add-on, you will likely be required to 2FA again. But otherwise, the 30-day 2FA memory should be retained with the above solution.

Good Luck!
~~~
  

Setting Email Links to Open Gmail in Firefox

gmail icon

Associate email links in Firefox 57 to GMail or Yahoo Webmail (WebUI):

(In Linux):
Firefox > Edit > Preferences > General > Applications Section > mailto >
- Use GMail.
- Use Yahoo! Mail
- Use Other…





~~~

November 24, 2017

Firefox 57 Open Bookmarks in New Tab

icon

about:config –> browser.tabs.loadBookmarksInTabs = true




~~~
  

November 15, 2017

Emergency Downgrade to Firefox 56

rewind firefox

Firefox 57 is out!!! Oh sh*t, half my plugins are gone and i can’t work!
I had previously automated daily firefox upgrades on my Debian 9 with a root cronjob:

@daily cd /home/USERNAME/Downloads && /usr/bin/curl -L -o firefox-latest-linux64.tar.bz2 "https://download.mozilla.org/?product=firefox-latest&os=linux64&lang=en-US" && tar xvf firefox-latest-linux64.tar.bz2 -C /opt/ && rm firefox-latest-linux64.tar.bz2 && ln -sf /opt/firefox/firefox /usr/bin/firefox

Today When i opened my favorite browser, “Hooray, FF 57!” … “CRAP, I can’t get my work done” because half my plugins are not compatible.
Here is the emergency downgrade to 56.0.2:

cd ~/Downloads
curl -L -o firefox-56.0.2.tar.bz2 "https://download.mozilla.org/?product=firefox-56.0.2-ssl&os=linux64&lang=en-US"
sudo tar xvf firefox-56.0.2.tar.bz2 -C /opt/ && sudo ln -sf /opt/firefox/firefox /usr/bin/firefox



~~~
Written with StackEdit.

March 13, 2016

Debian replaces Iceweasel with Firefox on March 10, 2016

Today I ran my regular debian full-update only to find this crazy message:

W: Failed to fetch http://mozilla.debian.net/dists/jessie-backports/Release: Unable to find expected entry 'iceweasel-release/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

And surprisingly, the news reported that Debian has replaced Iceweasel (unbranded-Firefox) with officially branded Firefox.

Reference: http://news.softpedia.com/news/debian-is-switching-to-mozilla-firefox-after-a-decade-of-using-iceweasel-501647.shtml

Reference: https://glandium.org/blog/?p=3622

What did this mean? It means that what we’ve come to be accustomed to was suddenly different, but not all that much. I re-located the “Debian Mozilla team” web-page (http://mozilla.debian.net/) and proceded to make changes.

I chose the “release” version of Firefox. I considered the “Extended Support Release” (ESR), which I’d normally opt for, but figured what the heck – I try to live with Mozilla’s continuous “improvements”. For this, I sudo edited my /etc/apt/sources.list (or /etc/apt/sources.d/*.list) and and was sure to remove any references to the old iceweasel packages. I added deb http://mozilla.debian.net/ jessie-backports firefox-release as instructed by the “Debian Mozilla team” page.

I then ran sudo aptitude update && sudo aptitude -t jessie-backports install firefox to install.

After fixing my xfce4-panel launcher, replacing Iceweasel with Firefox, and verifying browser configs were in-tact, I chose to uninstall iceweasel with sudo aptitude remove iceweasel because it will no longer be updated as such. You will find it also wants to uninstall any xul-ext-* packages you may have installed. I tend to install add-ons manually anyway, so this was okay for me.

You might test the the apt-get/aptitude -t option for testing, unstable, or jessie-backports repositories for updated versions of the add-ons, but i’ll leave that to you. For more information on backports, please reference the instructions link from http://backports.debian.org/. (For testing and unstable, you also need to add such repositories, but you know that already, right.)

When all is done, you will of course find Firefox all the exact same as your Iceweasel except now it is branded with Firefox Icons and such. Big woop.

As always, good luck.


Please consider crypto tipping:
  

September 02, 2015

VMWare vCenter vSphere Web Client Chrome 45 ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY


VMWare vCenter vSphere Web Client + Chrome 45
Server has a weak ephemeral Diffie-Hellman public key
ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY
a.k.a Forward Secrecy

I patched this together rather quickly, but i think it's all here!  Today we had issue with Chrome 45 failing to connect to VMWare 5.1 vCenter vSphere Web Server (vSphere Web Client).  This is how I fixed it. (Also seems to work in Firefox.)

create new self-signed certificate (in linux):
openssl genrsa 2048 > rui.key
openssl req -new -key rui.key > rui.csr
#openssl x509 -in rui.cer -out rui.crt
openssl x509 -req -days 1825 -in rui.csr -signkey rui.key -out rui.crt
openssl pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:testpassword -out rui.pfx
you must use testpassword if you retain the default tomcat keystorePass setting in the xml mentioned below.

backup and replace files in C:\Program Files\VMware\Infrastructure\vSphereWebClient\DMServer\config\ssl\ with the files just created.  *** my other vCenter did not have this folder. It was C:\Program Files\VMware\Infrastructure\vSphereWebClient\logbrowser\conf\ instead. (upgrade vs. fresh install?)

edit C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\config\tomcat-server.xml
was
        <Connector port="9443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="500" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" ciphers="SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" keystoreFile="C:\ProgramData\vmware\vSphere Web Client\ssl\rui.pfx" keystorePass="testpassword" keystoreType="PKCS12"></Connector>
changed to (removed RC4 and DHE-only ciphers)
        <Connector port="9443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="500" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" ciphers="TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" keystoreFile="C:\ProgramData\vmware\vSphere Web Client\ssl\rui.pfx" keystorePass="testpassword" keystoreType="PKCS12"></Connector>
restart both vspherewebclientsvc and vctomcat services. Be patient, it will take a few minutes for the services to be ready to serve the web-pages correctly.


---
As Always, Good Luck! 
Please comment or tip me or use any/all of my affiliate links; Thank YOU!
If I saved your ass, you can thank me with bitcoin.    


December 16, 2014

PepperFlash in Firefox (Debian)


UPDATE MAY 2017 : Apparently Adobe is updating NPAPI flash player for firefox again.  Erase all this specialized stuff and sudo aptitude install flashplayer-mozilla instead.

https://steronius.blogspot.com/2017/05/latest-adobe-flash-player-in-firefox.html

~~~~~~~~~~~

Linux aficionados know that Adobe suspended further development of Flash for Linux. Only updates to version 11 will be provided through 2017.

Google Chrome does however continue to update and support a special embedded version of Flash called PepperFlash which is currently at version 16.

I just discovered that PepperFlash can be used with FireFox, albeit in a circumventual way.

"Fresh Player Plugin" is the PepperFlash wrapper for Firefox by i-rinat on github. I originally found this information on Web Upd8.

It was easy to install without issue. I found that my Debian distro had a pepperflash installer in it's repo; however, installing Google Chrome will work just as well.
sudo aptitude install pepperflashplugin-nonfree
sudo update-pepperflashplugin-nonfree --install

Then I was able to install Fresh Player Plugin as per documentation:
sudo apt-get install cmake gcc g++ pkg-config ragel libasound2-dev libssl-dev libglib2.0-dev libpango1.0-dev libgl1-mesa-dev libevent-dev libgtk2.0-dev libxrandr-dev libxrender-dev libxcursor-dev libv4l-dev libgles2-mesa-dev libavcodec-dev libva-dev libvdpau-dev libdrm-dev libicu-dev

#optional:
sudo apt-get install libpulse-dev libjack-jackd2-dev libsoxr-dev

cd ~/Downloads #(or your preferred folder)
git clone https://github.com/i-rinat/freshplayerplugin.git
cd freshplayerplugin
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
make

cp libfreshwrapper-flashplayer.so ~/.mozilla/plugins/

Restart your firefox and take it for a test-run.

My FireFox reported the following using the Adobe About version check.  


To make it easier to update, I've scripted the make/install process which can be run manually on occasion, or as cronjob. If the build ever fails, i've found it best to delete the folder freshplayerplugin and re-clone it.
#!/bin/bash
cd ~/Downloads/freshplayerplugin/
git pull
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..

make && cp libfreshwrapper-flashplayer.so ~/.mozilla/plugins/ && firefox "https://www.adobe.com/software/flash/about/"&


As always, Good luck!
---



Please consider crypto tipping:
  

January 05, 2013

Open .URL files in Linux


EDIT:  Comments to this post have very nice solutions, honorable mention goes to Trogdor's 3rd post using bash -c "cat %f | grep URL | cut -d'=' -f2 | xargs firefox &" but first place goes to Christian Schmidt for his grep 'URL=' < "$1" | cut -d'=' -f2 | xargs -n1 xdg-open .

That said, here is my original post (which may be worth it just for the gnome association circus):
-----------------------

I've a ton of .URL files, created by drag-and-drop from Mozilla Firefox within MS-Windows.  These files are not automatically usable in Linux, which really sucks.  Googling did provide the solution though, and here I'll share my notes:

Create a script named open-url.sh (i like to store my scripts in ~/scripts/) containing the following:
#!/bin/sh
# opens Windows .URL files in your default browser
# requires: xdg-open sed grep xargs
sed 's/^BASEURL=/URL=/' "$1" | grep -m 1 '^URL=' | sed 's/^URL=//' | sed 's/\r//' | xargs xdg-open

Now make it executable with chmod +x open-url.sh

Now you can associate .URL files with the script.  This might be the hard part, as I did fight with it in gnome; however, XFCE was straight forward.

If you are having particular problems in gnome, my notes report the following:
Duplicate the file /usr/share/applications/firefox.desktop into /usr/share/applications/web-link.desktop, and edit the latter to point to the script you created.

Edit: You may consider using ~/.local/share/applications/ instead. I've found it's easier for gnome to find the new .desktop here.

Edit: be sure to give it an appropriate Name= and GenericName=

Then associate the .URL files with the web-link.desktop file.

Edit: Possibly the best way to associate in gnome3 is right-click the file and "Open Other" choosing the new name you've given with the Name= from the .desktop previously edited. THEN, most importantly, right click the file again, then choose properties, and highlight the new name and click "Set as Default".

Additionally, even though Firefox was my default browser, my environment insisted on opening with Chromium.  I was forced to manipulate the xdg-open command.  Below are commands that may help you: xdg-open
xdg-settings get default-web-browser
xdg-settings set default-web-browser firefox.desktop
There is some chance, you may need to look into gnome-open or gvfs-open.

Edit: You can do OSX .webloc files too with the following script:
#!/bin/sh
# opens OSX .webloc files in your favourite browser
# requires: grep awk xdg-open
# or edit for similar like gnome-open
grep string "$1" | awk -F\> '{print $2}' | awk -F\< '{print $1}' | xargs xdg-open


You may wish to read http://steronius.blogspot.com/search/label/xdg-mime%20default for setting mime-types.

Good luck.
~~~

Please consider crypto tipping: