Firefox and ActiveX: Difference between revisions

mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 28: Line 28:
*Install: "Hamburger Menu", Addons, Plugins, Gear Menu towards the top middle, Install Addon from File, select the downloaded file, etc.  Then restart Firefox.
*Install: "Hamburger Menu", Addons, Plugins, Gear Menu towards the top middle, Install Addon from File, select the downloaded file, etc.  Then restart Firefox.


== The Result ==
==The Profiles==
And don't forget about making it so Firefox uses multiple Profiles.  IE, a current version and a "Legacy" version of Firefox shouldn't use the same profle.
 
Solution, one profile for the current Firefox and a second profile for the "Legacy" Firefox.  See the below example for the "Target" command line to start each instance of Firefox
 
*Legacy Firefox: "C:\Program Files (x86)\Mozilla Firefox 52.9.0esr 32-bit\firefox.exe" -P "Firefox - 53.9.0esr Legacy" -no-remote
*Current Firefox: "C:\Program Files\Mozilla Firefox\firefox.exe" -P "Firefox - Current" -no-remote
 
Note: The profile names (after the -P switch) are arbitrary and can be named / titled anything.
 
...from: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
 
==The Result==
You now have the ability to view / access / use any older device (via a web GUI interface) that uses ActiveX technology.
You now have the ability to view / access / use any older device (via a web GUI interface) that uses ActiveX technology.


Line 35: Line 47:
[[File:Surveillance.jpg|center|1266x1266px]]
[[File:Surveillance.jpg|center|1266x1266px]]
<br />
<br />
==Requiem==
==The Extra and Requiem==
And of course it should be pointed out, not that any intelligent person wouldn't understand, that Firefox version 53 should not be used for any public website access (and I'm not sure it can even deal with modern TLS certificates).
And on a sad note (for some of the effort), found a slightly updated version of the cameras 'web viewer' software that allowed for non ActiveX controls to be used, but still required the older XPCOM and XUL style Addin (IE, the 'pre WebAssembly' version of PlugIns) architecture for Firefox.  And from there, the version that one can use (at least for this camera) gets a bit murky.  As far as I can tell, the ESR (Extended Service Release) version(s) of Firefox, which are a requirement for any of this stuff to work, goes from 52.9 to 60.something, with 52.9 not having WebAssembly enabled.  And for the regular version, the 'XPInstall signed' thing is only available in the ESR version, so even though the older XPCOM and XUL style add-ins seem to be available through version 57 or 59 of 'regular' Firefox, the signing setting isn't available.  So in the end, to play it safe, picking 52.9.0esr was a good choice.
 
As with everything these days, there are choices.  Another choice for the above dilemma might be [https://www.seamonkey-project.org/ SeaMonkey] (tried, but couldn't get it to work)
 
And of course it should be pointed out, not that any intelligent person wouldn't understand, that Firefox version 52 should not be used for any public website access (and I'm not sure it can even deal with modern TLS certificates).  This entire article is about keeping older hardware viable (and cutting down on e-waste among other things).  Access to any 'website' with Firefox 52 requires that you be aware of what you're connecting to ahead of time (IE, nothing on the public internet).