Re: add-on signing error, Adblock Plus from AMO [solved]
On Dec 18, 8:00 pm, »Q« wrote: > Do any of you know if Mozilla supplies source patches to NSS tarballs > when the certificate store is updated, or does it just wait for the > next NSS version number? If there are patches provided, I'll point the > Gentoo maintainer to them. That's mostly what 3.12.3.1 is. I checked, updated certificate store is almost the only difference between 3.12.3.1 and 3.12.3 - plus two or three minor fixes that are probably applied in Gentoo anyway. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: add-on signing error, Adblock Plus from AMO
On Dec 18, 11:38 pm, Paul Hartman wrote: > Try this link to see if the root certificate for StartSSL is installed > in your browser (and add it if it's not):http://www.startssl.com/?app=9 As I mentioned above, your certificate store must be very outdated as to not include StartCom root certificate. However, until recently it wasn't allowed for code signing. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: add-on signing error, Adblock Plus from AMO [solved]
On Dec 18, 11:00 am, Wladimir Palant wrote: > From the look of it, Gentoo simply gets the source code from the FTP > server - version 3.12.3 there comes with ckbi 1.73, only version > 3.12.3.1 has ckbi 1.75. Looking further into this, I see why I've seen only two reports on this issue so far. Official builds for both Firefox and SeaMonkey come with their own NSS library, those always work correctly. Only vendor- supplied builds rely on an independent NSS package which could be outdated (but not always is, at least some distributions already use NSS 3.12.4). ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: add-on signing error, Adblock Plus from AMO [solved]
On Dec 17, 10:35 pm, »Q« wrote: > I've got nss-3.12.3-r1, which isn't the latest from Mozilla but which > is well after StartCom certs were added. StartCom certs were added long ago but they were only allowed for signing code relatively recently. The version of NSS isn't important here, it's the version of the certificate store (ckbi library) that is relevant. Mozilla used NSS_3_12_2_WITH_CKBI_1_75_RTM in Firefox 3.0.12, that's the first version to support StartCom's code signing. >From the look of it, Gentoo simply gets the source code from the FTP server - version 3.12.3 there comes with ckbi 1.73, only version 3.12.3.1 has ckbi 1.75. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: add-on signing error, Adblock Plus from AMO
On Dec 17, 9:50 am, Philip Chee wrote: > The AdblockPlus Blog has a recent post about signing problems with some > ABP builds, but the latest version from their website should have fixed > the signing problem. No, David above is right - the Adblock Plus build is not the issue (and never was, don't know which blog post you refer to). StartCom Certification Authority should be trusted to identify software makers, this is the case for all supported applications including SeaMonkey 2.0. Unless SeaMonkey on Gentoo is special of course :-( ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Adblock Plus Corrupting Browser Window/Uninstall Add-Ons?
On Jul 11, 3:03 am, Jim J wrote: > I just upgraded to SM 1.1.17 and installed Adblock Plus. It seemed to > work fine until I installed a couple other add-ons. Now, ABP (I think) > causes a non-interactive (can't even copy the text) error/debug message > to take up the bottom third of the browser window, and the ABP button & > menu entry are missing. Yep, that's SeaMonkey messing up extension registry. Adblock Plus 1.0.2 tries to work around these issues as much as possible - but really, there isn't so much you can do. Adblock Plus 1.1 (coming out today) will no longer support SeaMonkey 1.1. I sincerely recommend installing SeaMonkey 2.0b1 when it comes out (hopefully in a week) and giving it a try - despite the beta status. It should have far less issues than the current release, especially if you are using extensions. -- Wladimir Palant, Adblock Plus developer http://adblockplus.org/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: AdBlock Plus will be dropping Gecko v1.8 soon.
On May 22, 10:42 pm, Ant wrote: > How about forking it? Split into two different Adblock Pluses? I am not sure I can follow. You mean branching Adblock Plus development - so that for example Adblock Plus 1.0.3 is released in parallel with Adblock Plus 1.1? And Adblock Plus 1.0.3 would support both the new filter syntax and SeaMonkey 1.1? This is theoretically a possibility, a 1.0.x branch exists already. But I don't have the time to do it like this, the effort is considerable and there will be too few people to beta-test this release properly. So if you have volunteers who would backport the relevant patches to 1.0.x branch - sure, we can talk about it. If not - sorry. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: AdBlock Plus will be dropping Gecko v1.8 soon.
On May 22, 12:35 am, »Q« wrote: > It's not clear what's won't be supported in future versions. > SeaMonkey 1.1.x uses Mozilla 1.8.1.x, not 1.8.0. I think it is clear in my post here: http://adblockplus.org/forum/viewtopic.php?t=3828 Adblock Plus dropped support for Gecko 1.8.0 long ago. Now it is time to stop supporting Gecko 1.8.1. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: AdBlock Plus will be dropping Gecko v1.8 soon.
On May 20, 10:38 pm, Ant wrote: > According to Ares' forum reply in my forum > thread:http://forums.lanik.us/viewtopic.php?f=64&t=3596&p=15719#p15718 > > "I didn't test it but I do think so. However, according > tohttps://addons.mozilla.org/statistics/addon/1865only ~5% of all Adblock > Plus users still use it, and the next Adblock Plus version will drop > Gecko 1.8.0 support anyway, ..." :( Better use this as source of information: http://adblockplus.org/forum/viewtopic.php?t=3828 Yes, I have been waiting to drop support for SeaMonkey 1.1.x for a very long time - most importantly because of the horribly outdated extension installer. I hoped to see SeaMonkey 2.0 released before that but this will take half a year longer from what I can tell (there is no real roadmap and I didn't even get an approximate answer when I nagged KaiRo about this). There was really tons of compatibility code in Adblock Plus that was blocking important code refactoring, I couldn't wait any longer. I hope that by the time I release Adblock Plus 1.1 SeaMonkey 2.0b1 will be out - I will recommend upgrading to this release. Stable or not, it will be much better than SeaMonkey 1.1. Of course, staying with Adblock Plus 1.0.2 will be another option. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
