Firefox 17.0.2 for Solaris 10 (sparc) (contrib) not available
There is a security finding on Firefox 17.0.1 (CVE-2013-0759), and we need to install Firefox 17.0.2 for Solaris 10/sparc. We have to use the 17.x series. For some reason the "ftp://ftp.mozilla.org/pub/firefox/releases/17.0.2esr/contrib/" directory is empty.
Alla svar (8)
There is a version 18 build: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/contrib/
I also found something in the build2 folder here, but no idea whether it tested out okay. Maybe something went wrong??
http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/17.0.2esr-candidates/
Why do you need version 17 -- to stay on the ESR track?
Firefox 10.x ESR and 17.x ESR are the only ones that our security has approved. We are going to Firefox 17.0.2 for Windows, and would like the same version for Solaris.
Oracle has Firefox 10.0.12 ESR for Solaris 10 SPARC/x86. I just downloaded it from MOS as a package (not public yet). Patch 145080-12 (SPARC) and 145080-11 (x86) can get you to Firefox 10.0.7. Link to patch http://www.oracle.com/technetwork/topics/security/thirdparty-patch-map-1482893.html
Oracle said they will have 17 ESR soon
Ändrad
The current 17.0.4esr contrib builds for Solaris is at
ftp://ftp.mozilla.org/pub/firefox/releases/17.0.4esr/contrib/solaris_tarball/ ftp://ftp.mozilla.org/pub/firefox/releases/17.0.4esr/contrib/solaris_pkgadd/
Ändrad
Or a link to always get the latest version:
I suppose I could have linked to that for in case somebody sees this thread in future.
Ändrad
Has there been any additional info from Oracle as to when they might update Firefox for Solaris 10 SPARC beyond 10.0.7 ESR (aka Patch ID #145080-12)? I have not been able to find the referenced package for 10.0.12 ESR within MOS. Realistically, I really need 17.0.5 ESR or later -- the contributed versions are not an option due to their questionable source (i.e., Beijing).
Does anyone know how we could get a copy of the source tree for the contributed build for Solaris so that we could build it ourself? How involved is that process? The unattributed build source is an issue for many.
Thanks, rcs