Re: SM 2.0.10 - Google images problem
chicagofan wrote: Philip TAYLOR (Webmaster, Ret'd) wrote: What does it mean to use images on the search page ? There is a background picture/image [you have chosen], with the Google search box in the middle of it. :) Like Windows wallpaper, if you will. ;) Ah, thank you, understood. Well, it worked for me using Seamonkey 2.3.1 under Win/XP PRO;SP3. However, as a vaguely related aside, after being driven to distraction by Google's most recent attempt to infuriate (the so-called Google Instant), I followed the advice of a fellow distractee and changed my home page to http://www.google.co.uk/webhp?complete=0 Result : instant bliss. No more single-character interactions, no more guessing, and no more half-baked suggestions. Sanity has been restored : long may it reign. Philip Taylor ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Seamonkey 2.3.1 : can I turn off Seamonkey Instant
Having finally succeeded in turning off Google Instant and Google Autocomplete by setting my home page to : http://www.google.co.uk/webhp?complete=0 I am now being driven to distraction by Seamonkey's Find behaviour (from Ctrl-F) seeking to emulate the abominable Google Instant. Is there any of reverting Find's behaviour to its former line- oriented behaviour whereby it used to wait to be told what to search for (by hitting return) rather than trying to be über-clever and guess from the characters already typed ? Philip Taylor ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
SeaMonkey 2.3.2 is now available as free downloads for Windows, Mac, and Linux from http://www.seamonkey-project.org. As always, we recommend that users keep up to date with the latest stability and support versions of SeaMonkey, and encourage all our users to upgrade to the very latest version. We strongly recommend that all SeaMonkey users upgrade to this latest releases. If you already have SeaMonkey, you will receive an automated update notification within 24 to 48 hours. SeaMonkey 2.3.2 revokes the root certificate for DigiNotar due to fraudulent SSL certificate issuance. For additional details, see http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate. Note: All SeaMonkey users are strongly encouraged to upgrade to the latest SeaMonkey by downloading it from our website or by selecting “Check for Updates…” from the Help menu and clicking on “Update SeaMonkey”. Full news article: http://www.seamonkey-project.org/news#2011-08-31 Release notes: http://www.seamonkey-project.org/releases/seamonkey2.3 System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] -- Justin Wood (Callek) SeaMonkey Council member, and Release Engineer ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
The About SeaMonkey shows the old version 2.3.1 instead 2.3.2 Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/ 20110830 Firefox/6.0.1 SeaMonkey/2.3.1 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
The About SeaMonkey shows the old version 2.3.1 instead 2.3.2 Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/ 20110830 Firefox/6.0.1 SeaMonkey/2.3.1 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
Am 31.08.2011 11:31, schrieb Justin Wood (Callek): System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] That gives a 404 error, http://www.seamonkey-project.org/doc/system-requirements works. Philipp ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.1 Upgrade
On Tue, 30 Aug 2011 16:10:42 -0700, Michael Gordon wrote: Almost all the familiar tools I used on a daily basis are missing because they are not compatible with this newer version of SeaMonkey. Most notably the “Google Search Bar” is missing, but still available with Internet Explorer. When I need to perform research and development on the Web I can still open Internet Explorer and perform the research I need for a project. Google has EOLed it's Google Search Bar for Firefox which I guess is also for SeaMonkey. Therefore there won't be an updated version. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.1 Upgrade
On Tue, 30 Aug 2011 17:16:11 -0700, Michael Gordon wrote: Mike wrote: Michael Gordon wrote: Most notably the “Google Search Bar” is missing Right-click the toolbar and choose customize. You can add a native Google Search box to the right of the address bar (ala Firefox) from there. True, but you cannot add the old search options as found in the previous Google Search Bar. Someone might be able to adapt Googlebar Lite for SeaMonkey. https://addons.mozilla.org/en-US/firefox/addon/googlebar-lite/ That should give you much but not all the functionality of the official googlebar. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: A plea for a return to sanity in new version release scheduling
Michael Gordon wrote: Daniel wrote: Michael Gordon wrote: Daniel wrote: Ron Hunter wrote: On 8/29/2011 8:16 AM, Daniel wrote: John wrote: I use SeaMonkey most of the time and Firefox occasionally. I try never to use IE. The web browser and email client are critically important to me, and I think the majority of users would agree. Since Firefox and SeaMonkey embarked on their accelerated release schedule, we've seen several updates incorporating many significant behavioral changes which are causing grief to many users. Along with this we are being encouraged to upgrade promptly because that's the only way to get the latest security patches. Why the big hurry all of a sudden? Changes in program behavior should be fully documented in advance of an upgrade. Users who prefer the behavior of the old version should be given the option to retain it. If it ain't broke, don't fix it! The end user should not be forced to be the guinea pig whose feedback becomes the quality control for these programs. Please return to the former more careful release strategy. I worked as an electrical engineer for Motorola for many years. All too often, we had products being sold before they were designed and unrelenting pressure to push them out the door. There's never time to do it right, but there's always time to do it over was the cynical opinion of many of my colleagues. It seems like the software industry is the same way. Is it really rapid-release?? SeaMonkey 1.0 alpha through to SeaMonkey 1.0.9 - twelve releases over twenty months. SeaMonkey 1.1 alpha through to SeaMonkey 1.1.19 - twenty two releases over forty three months. SeaMonkey 2.0 alpha through to SeaMonkey to SeaMonkey 2.0.14 - twenty two releases over thirty months. Should the question really be *What's the difference??* There are a lot of differences, but the primary one is that the new release system includes NOT just bug and security fixes, but NEW FEATURES. There is also an ongoing User Interface redesign that is taking place slowly since FF4. I can't see that just how they choose to number releases affects any aspect of either use, or utility, of a release. Getting new features, and other 'non-bug/security' fixes to the user-base as quickly as possible means the FF can remain competitive in a rather difficult market. I, for one, think the new system is fantastic, and makes the product more useful, and more 'current'. What numbers are applied, I will let others discuss because it doesn't matter to me. The point, which I apparently failed to make, is that SM updates have always happened fairly often, so I don't see what the problem with six weekly updates is?? Daniel, There should not be any problem with the weekly updates as long as the first in the series contains fully documented changes to how important user tools and option perform. Example: When upgrading from SM 2.0 to 2.1 all user tools and options that have been improved from the previous version need to be fully documented within the application Help Files. Major security fixes need to be fully documented where those fixes may change the behavior over the older version. When making a minor version change (2.0.1 to 2.0.2) or (2.2.1 to 2.2.2) for security patches those changes must not change any user tools or operations. If a security patch is required that will affect user options then a new version level needs to be created with full documentation. Full documentation does not mean disclosing the code base in question, but dose mean how the changes will affect user experience with the new upgrade. Failure to perform these simple tasks will drive more users back to MS Internet Explorer and Outlook. Conclusion: The number of security patches is very important to keep our applications secure from the nasty world of Hackers and Crackers trying to infect our computers. At the same time the new and improved updates/upgrades must document the changes and how they may affect user experience. I don't mind having one, two, or three security upgrades a week if those upgrades do not affect how I use SM, and if they may affect my use of SM how do the changes affect how I use SM. Michael G Michael, back a bit I reported that I was having a problem so, after upgrading, when I clicked on the Browser Icon (I normally just start in Mail News), I was being taken to a SeaMonkey-Project page which advised of the problems/improvements made in the upgrade rather than my Home Group. This was a desired situation (by the developers) which, I think, could be switched off in prefs.js Has this function been changed?? In an upgrade it may have changed some basic preferences. When you write the Browser Icon are you referring to the SeaMonkey icon on your desktop? As I typed above, I normally just start in Mail News, so when I typed Browser Icon, I mean the one in the bottom left of the Mail News screen. You can change how SM opens in the Edit/Preferences/Appearance by selecting the
2.3.2 .dmg file (for Mac) contains 2.3.1
FYI: After getting the you're running an older version message, downloading and installing the 2.3.2 .dmg file (Mac), I found that I was still getting the error message -- looking deeper, I found that the installed version announces itself as 2.3.1, and looking into the downloaded package, get info and the info.plist file revealed that it was, in fact, 2.3.1 --- looks like something in the distribution pipeline went wrong. Already filed a big report. -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
Justin Wood (Callek) wrote: SeaMonkey 2.3.2 is now available as free downloads for Windows, Mac, and Linux from http://www.seamonkey-project.org. As always, we recommend that users keep up to date with the latest stability and support versions of SeaMonkey, and encourage all our users to upgrade to the very latest version. We strongly recommend that all SeaMonkey users upgrade to this latest releases. If you already have SeaMonkey, you will receive an automated update notification within 24 to 48 hours. SeaMonkey 2.3.2 revokes the root certificate for DigiNotar due to fraudulent SSL certificate issuance. For additional details, see http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate. Note: All SeaMonkey users are strongly encouraged to upgrade to the latest SeaMonkey by downloading it from our website or by selecting “Check for Updates…” from the Help menu and clicking on “Update SeaMonkey”. Full news article: http://www.seamonkey-project.org/news#2011-08-31 Release notes: http://www.seamonkey-project.org/releases/seamonkey2.3 System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] After reading the other postings dealing with 2.3.2, I get the distinct impression that the botched 2.3.2 release was a *panic* Get it out the door quick, reaction to the recent security breach event. Will y'all fix 2.3.2 , and dot the ts and cross the is before re releasing? -- Rostyk ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Question about 2.0.14 - 2.3.1 upgrade.
Michael Gordon wrote: Rostyslaw Lewyckyj wrote: I'm on a 64bit WIN 7 Ultimate system. I just downloaded the SM 2.3.1 program binary from www.seamonky-project.org and ran the installer exe. (after a full backup of the profile and program folders) The installer ran in a flash, and now I'm supposedly at SM 2.3.1 But I'm curious and just a bit apprehensive. Did that upgrade installation carry out all those profile conversions that were discussed and argued about here, such as the bookmarks database conversion et.c. ? I need reassurance :-) It did for my Win XP SR3 computer. I noticed the same almost instant install process and came to the conclusion that if the previous installation used the default installation paths then the later upgrades would perform almost instantly. Reason: The installer new exactly where to find the older files to upgrade. Michael G ME, too. I am running 2.0.14 because of all the negative comments of the versions after that. I am running HP desktop, 6gb memory 750gb hard drive, Windows 7. I know there has been a great deal of be sure to do this/that before you upgrade so I have been hesitant to get away from 2.0.14. Am I getting left behind with security issues, better features, new options, etc? w. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Question about 2.0.14 - 2.3.1 upgrade.
Walter wrote: Michael Gordon wrote: Rostyslaw Lewyckyj wrote: I'm on a 64bit WIN 7 Ultimate system. I just downloaded the SM 2.3.1 program binary from www.seamonky-project.org and ran the installer exe. (after a full backup of the profile and program folders) The installer ran in a flash, and now I'm supposedly at SM 2.3.1 But I'm curious and just a bit apprehensive. Did that upgrade installation carry out all those profile conversions that were discussed and argued about here, such as the bookmarks database conversion et.c. ? I need reassurance :-) It did for my Win XP SR3 computer. I noticed the same almost instant install process and came to the conclusion that if the previous installation used the default installation paths then the later upgrades would perform almost instantly. Reason: The installer new exactly where to find the older files to upgrade. Michael G ME, too. I am running 2.0.14 because of all the negative comments of the versions after that. I am running HP desktop, 6gb memory 750gb hard drive, Windows 7. I know there has been a great deal of be sure to do this/that before you upgrade so I have been hesitant to get away from 2.0.14. Am I getting left behind with security issues, better features, new options, etc? w. As far as I know there are only two issues in where you will be lewft behind. 1. Security related issues. 2. Some plugins and Ad-ons may not function. Michael g ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 08/31/2011 02:31 AM, Justin Wood (Callek) wrote: SeaMonkey 2.3.2 is now available as free downloads for Windows, Mac, and Linux from http://www.seamonkey-project.org. As always, we recommend that users keep up to date with the latest stability and support versions of SeaMonkey, and encourage all our users to upgrade to the very latest version. We strongly recommend that all SeaMonkey users upgrade to this latest releases. If you already have SeaMonkey, you will receive an automated update notification within 24 to 48 hours. SeaMonkey 2.3.2 revokes the root certificate for DigiNotar due to fraudulent SSL certificate issuance. For additional details, see http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate. Note: All SeaMonkey users are strongly encouraged to upgrade to the latest SeaMonkey by downloading it from our website or by selecting “Check for Updates…” from the Help menu and clicking on “Update SeaMonkey”. Full news article: http://www.seamonkey-project.org/news#2011-08-31 Release notes: http://www.seamonkey-project.org/releases/seamonkey2.3 System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate/ Note: if you are unable to update until later for some reason, I *highly* recommend: Edit|Preferences|Privacy Security|Certificates|Manage Certificates|Authorities|click on 'DigiNotrar Root CA' and click 'Delete or Distrust' 'OK'. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 8/31/2011 6:11 AM, Philipp Wagner wrote: Am 31.08.2011 11:31, schrieb Justin Wood (Callek): System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] That gives a 404 error, http://www.seamonkey-project.org/doc/system-requirements works. Thanks (I forgot Jens updated the url for it, probably worth me/him creating a |301| for that url though, given my history listing it in these announcements) -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 8/31/2011 11:43 AM, Rostyslaw Lewyckyj wrote: Justin Wood (Callek) wrote: SeaMonkey 2.3.2 is now available as free downloads for Windows, Mac, and Linux from http://www.seamonkey-project.org. As always, we recommend that users keep up to date with the latest stability and support versions of SeaMonkey, and encourage all our users to upgrade to the very latest version. We strongly recommend that all SeaMonkey users upgrade to this latest releases. If you already have SeaMonkey, you will receive an automated update notification within 24 to 48 hours. SeaMonkey 2.3.2 revokes the root certificate for DigiNotar due to fraudulent SSL certificate issuance. For additional details, see http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate. Note: All SeaMonkey users are strongly encouraged to upgrade to the latest SeaMonkey by downloading it from our website or by selecting “Check for Updates…” from the Help menu and clicking on “Update SeaMonkey”. Full news article: http://www.seamonkey-project.org/news#2011-08-31 Release notes: http://www.seamonkey-project.org/releases/seamonkey2.3 System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] After reading the other postings dealing with 2.3.2, I get the distinct impression that the botched 2.3.2 release was a *panic* Get it out the door quick, reaction to the recent security breach event. Will y'all fix 2.3.2 , and dot the ts and cross the is before re releasing? 2.3.2 was a panic release, because it was an issue actively exploiting users in the wild, on that release day, and had been for a while :( . The only issue with SeaMonkey 2.3.2 that was not in Firefox 6.0.1 was our reported version string. Sadly, that had a few user facing what, why, do I have the right version feelings. Luckily (or unluckily depending on your POV) there is a new chemspill because they took the block slightly further than initially intended, that should be released within 48 hours, that will correct also our version number. I will be doing partial (small) updates for both 2.3.1 and 2.3.2 for that, so hopefully your impact is relatively small. Thank you for your patience. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.3.2 .dmg file (for Mac) contains 2.3.1
On Aug 31, 6:34 am, Miles Fidelman mfidel...@meetinghouse.net wrote: FYI: After getting the you're running an older version message, downloading and installing the 2.3.2 .dmg file (Mac), I found that I was still getting the error message -- looking deeper, I found that the installed version announces itself as 2.3.1, and looking into the downloaded package, get info and the info.plist file revealed that it was, in fact, 2.3.1 --- looks like something in the distribution pipeline went wrong. Already filed a big report. -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra Saw the same thing here. I also downloaded the SeaMonkey2.3.2.dmg from http://www.seamonkey-project.org/releases/#2.3.2 and got the disk image of what appears to be SeaMonkey version 2.3.2 but it actually is version 2.3.1 when I copied to my hard drive and opened it. Can someone check what happened to the real version 2.3.2? Thank you, Frank ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Question about 2.0.14 - 2.3.1 upgrade.
Interviewed by CNN on 31/08/2011 13:32, Walter told the world: ME, too. I am running 2.0.14 because of all the negative comments of the versions after that. I am running HP desktop, 6gb memory 750gb hard drive, Windows 7. I know there has been a great deal of be sure to do this/that before you upgrade so I have been hesitant to get away from 2.0.14. Am I getting left behind with security issues, better features, new options, etc? Yes, you are getting left behind. What you aren't getting: - Any security fixes in Gecko since Firefox 3.5.x was end-of-life'd in April 2011. - Any improvements in Gecko rendering since Firefox 3.6 was launched in January 2010. - Any user-interface and other fixes since Seamonkey 2.0.x was end-of-life'd in June 2011. - The Places bookmarks system (which dates from Firefox 3, but was kinda left behind in the Toolkit transition for Seamonkey 2.0) This includes, but is not limited to: - Faster Javascript - Personas - Full-screen playback of Theora video - WOFF web fonts - Improved support for HTML5, CSS3, WebM, and WebGL. - Numerous security enhancements -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Babcom. *Added by TagZilla 0.066.2 running on Seamonkey 2.3.1 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 08/31/2011 12:10 PM, Justin Wood (Callek) wrote: On 8/31/2011 11:43 AM, Rostyslaw Lewyckyj wrote: ... After reading the other postings dealing with 2.3.2, I get the distinct impression that the botched 2.3.2 release was a *panic* Get it out the door quick, reaction to the recent security breach event. Will y'all fix 2.3.2 , and dot the ts and cross the is before re releasing? 2.3.2 was a panic release, because it was an issue actively exploiting users in the wild, on that release day, and had been for a while :( . The only issue with SeaMonkey 2.3.2 that was not in Firefox 6.0.1 was our reported version string. Sadly, that had a few user facing what, why, do I have the right version feelings. Luckily (or unluckily depending on your POV) there is a new chemspill because they took the block slightly further than initially intended, that should be released within 48 hours, that will correct also our version number. I will be doing partial (small) updates for both 2.3.1 and 2.3.2 for that, so hopefully your impact is relatively small. Thank you for your patience. Linux versions are borked (both 32bit and 64bit). Both report 2.3.1. But *worse* is that they reenstate DigiNotar Root CA. Tested both ways: 1. 32bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. Build identifier: Mozilla/5.0 (X11; Linux i686; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 2. 64bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. So I downloaded the entire bz2, deleted the old, and extracted to a new folder; DigiNotar Root CA is now back on that version as well. Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 I've not tested any windows versions (yet). ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey for Mac not updated to version 2.32.
I attempted to update SeaMonkey on my Mac this morning using Check for Update and it got the update, however, when I checked the version using About SeaMonkey it showed version 2.3.1. Then I went to the www.seamonkey-project.org website to download the disk image and it showed SeaMonkey2.3.2.dmg and I downloaded on my system and then I copied SeaMonkey to my Applications Folder and then I open SeaMonkey and it showed version 2.3.1. Where is the real SeaMonkey version 2.3.2? Thank you, Frank ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 8/31/2011 5:39 PM, NoOp wrote: On 08/31/2011 12:10 PM, Justin Wood (Callek) wrote: On 8/31/2011 11:43 AM, Rostyslaw Lewyckyj wrote: ... After reading the other postings dealing with 2.3.2, I get the distinct impression that the botched 2.3.2 release was a *panic* Get it out the door quick, reaction to the recent security breach event. Will y'all fix 2.3.2 , and dot the ts and cross the is before re releasing? 2.3.2 was a panic release, because it was an issue actively exploiting users in the wild, on that release day, and had been for a while :( . The only issue with SeaMonkey 2.3.2 that was not in Firefox 6.0.1 was our reported version string. Sadly, that had a few user facing what, why, do I have the right version feelings. Luckily (or unluckily depending on your POV) there is a new chemspill because they took the block slightly further than initially intended, that should be released within 48 hours, that will correct also our version number. I will be doing partial (small) updates for both 2.3.1 and 2.3.2 for that, so hopefully your impact is relatively small. Thank you for your patience. Linux versions are borked (both 32bit and 64bit). Both report 2.3.1. But *worse* is that they reenstate DigiNotar Root CA. Tested both ways: 1. 32bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. Build identifier: Mozilla/5.0 (X11; Linux i686; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 2. 64bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. So I downloaded the entire bz2, deleted the old, and extracted to a new folder; DigiNotar Root CA is now back on that version as well. Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 I've not tested any windows versions (yet). The root CA will still appear in the cert list, but it is blocked, please test with a website. But its a factor of how this code works. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.3.2 .dmg file (for Mac) contains 2.3.1
On 8/31/2011 6:06 PM, Patrick Crumhorn wrote: Similar issue here but with WinXP. Updated to 2.3.2 for Windows but the About SeaMonkey page and the user agent both still show it as 2.3.1. Frank Chan wrote: On Aug 31, 6:34 am, Miles Fidelmanmfidel...@meetinghouse.net wrote: FYI: After getting the you're running an older version message, downloading and installing the 2.3.2 .dmg file (Mac), I found that I was still getting the error message -- looking deeper, I found that the installed version announces itself as 2.3.1, and looking into the downloaded package, get info and the info.plist file revealed that it was, in fact, 2.3.1 --- looks like something in the distribution pipeline went wrong. Already filed a big report. -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra Saw the same thing here. I also downloaded the SeaMonkey2.3.2.dmg from http://www.seamonkey-project.org/releases/#2.3.2 and got the disk image of what appears to be SeaMonkey version 2.3.2 but it actually is version 2.3.1 when I copied to my hard drive and opened it. Can someone check what happened to the real version 2.3.2? Thank you, Frank I created a blog post about this: http://blog.drapostles.org/archives/69 -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey for Mac not updated to version 2.32.
On 8/31/2011 6:06 PM, fchan wrote: I attempted to update SeaMonkey on my Mac this morning using Check for Update and it got the update, however, when I checked the version using About SeaMonkey it showed version 2.3.1. Then I went to the www.seamonkey-project.org website to download the disk image and it showed SeaMonkey2.3.2.dmg and I downloaded on my system and then I copied SeaMonkey to my Applications Folder and then I open SeaMonkey and it showed version 2.3.1. Where is the real SeaMonkey version 2.3.2? Thank you, Frank I created a blog post about this: http://blog.drapostles.org/archives/69 -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.3.2 .dmg file (for Mac) contains 2.3.1
Similar issue here but with WinXP. Updated to 2.3.2 for Windows but the About SeaMonkey page and the user agent both still show it as 2.3.1. Frank Chan wrote: On Aug 31, 6:34 am, Miles Fidelmanmfidel...@meetinghouse.net wrote: FYI: After getting the you're running an older version message, downloading and installing the 2.3.2 .dmg file (Mac), I found that I was still getting the error message -- looking deeper, I found that the installed version announces itself as 2.3.1, and looking into the downloaded package, get info and the info.plist file revealed that it was, in fact, 2.3.1 --- looks like something in the distribution pipeline went wrong. Already filed a big report. -- In theory, there is no difference between theory and practice. Infnordpractice, there is. Yogi Berra Saw the same thing here. I also downloaded the SeaMonkey2.3.2.dmg from http://www.seamonkey-project.org/releases/#2.3.2 and got the disk image of what appears to be SeaMonkey version 2.3.2 but it actually is version 2.3.1 when I copied to my hard drive and opened it. Can someone check what happened to the real version 2.3.2? Thank you, Frank ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: 2.3.2 .dmg file (for Mac) contains 2.3.1
Thanks! I figured that was the case, but just wanted that extra bit of assurance that the security issue was indeed fixed in this update. :) Justin Wood (Callek) wrote: On 8/31/2011 6:06 PM, Patrick Crumhorn wrote: Similar issue here but with WinXP. Updated to 2.3.2 for Windows but the About SeaMonkey page and the user agent both still show it as 2.3.1. Frank Chan wrote: On Aug 31, 6:34 am, Miles Fidelmanmfidel...@meetinghouse.net wrote: FYI: After getting the you're running an older version message, downloading and installing the 2.3.2 .dmg file (Mac), I found that I was still getting the error message -- looking deeper, I found that the installed version announces itself as 2.3.1, and looking into the downloaded package, get info and the info.plist file revealed that it was, in fact, 2.3.1 --- looks like something in the distribution pipeline went wrong. Already filed a big report. -- In theory, there is no difference between theory and practice. Infnord practice, there is. Yogi Berra Saw the same thing here. I also downloaded the SeaMonkey2.3.2.dmg from http://www.seamonkey-project.org/releases/#2.3.2 and got the disk image of what appears to be SeaMonkey version 2.3.2 but it actually is version 2.3.1 when I copied to my hard drive and opened it. Can someone check what happened to the real version 2.3.2? Thank you, Frank I created a blog post about this: http://blog.drapostles.org/archives/69 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0.10 - Google images problem
Philip TAYLOR (Webmaster, Ret'd) wrote: chicagofan wrote: Philip TAYLOR (Webmaster, Ret'd) wrote: What does it mean to use images on the search page ? There is a background picture/image [you have chosen], with the Google search box in the middle of it. :) Like Windows wallpaper, if you will. ;) Ah, thank you, understood. Well, it worked for me using Seamonkey 2.3.1 under Win/XP PRO;SP3. However, as a vaguely related aside, after being driven to distraction by Google's most recent attempt to infuriate (the so-called Google Instant), I followed the advice of a fellow distractee and changed my home page to http://www.google.co.uk/webhp?complete=0 Result : instant bliss. No more single-character interactions, no more guessing, and no more half-baked suggestions. Sanity has been restored : long may it reign. That's what my Google search page looks like now, except it has a BIG, multi-colored Google logo above the search field. I hate that new Google multi-colored logo, and that's one of the reasons I want to choose the background. :) bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 08/31/2011 03:07 PM, Justin Wood (Callek) wrote: On 8/31/2011 5:39 PM, NoOp wrote: On 08/31/2011 12:10 PM, Justin Wood (Callek) wrote: On 8/31/2011 11:43 AM, Rostyslaw Lewyckyj wrote: ... After reading the other postings dealing with 2.3.2, I get the distinct impression that the botched 2.3.2 release was a *panic* Get it out the door quick, reaction to the recent security breach event. Will y'all fix 2.3.2 , and dot the ts and cross the is before re releasing? 2.3.2 was a panic release, because it was an issue actively exploiting users in the wild, on that release day, and had been for a while :( . The only issue with SeaMonkey 2.3.2 that was not in Firefox 6.0.1 was our reported version string. Sadly, that had a few user facing what, why, do I have the right version feelings. Luckily (or unluckily depending on your POV) there is a new chemspill because they took the block slightly further than initially intended, that should be released within 48 hours, that will correct also our version number. I will be doing partial (small) updates for both 2.3.1 and 2.3.2 for that, so hopefully your impact is relatively small. Thank you for your patience. Linux versions are borked (both 32bit and 64bit). Both report 2.3.1. But *worse* is that they reenstate DigiNotar Root CA. Tested both ways: 1. 32bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. Build identifier: Mozilla/5.0 (X11; Linux i686; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 2. 64bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. So I downloaded the entire bz2, deleted the old, and extracted to a new folder; DigiNotar Root CA is now back on that version as well. Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 I've not tested any windows versions (yet). The root CA will still appear in the cert list, but it is blocked, please test with a website. But its a factor of how this code works. Reloaded 2.3.1 (the original) and DigiNotar Root CA shows with trust settings: - This certificate can identify web sites - This certificate can identify software makers https://zga-tag.zorggroep-almere.nl/ works 2.16.528.1.1001.1.1.1.10.1: Certification Practice Statement pointer: http://www.diginotar.nl/cps User Notice: Conditions, as mentioned on our website (www.diginotar.nl), are applicable to all our products and services. Reloaded 2.3.2 64bit (shows 2.3.1) and DigiNotar Root CA now is not showing at all https://zga-tag.zorggroep-almere.nl/ shows an invalid cert. Reloaded 2.3.2 (32bit) and DigiNotar Root CA shows with all trust settings unchecked (similar to Windows). https://zga-tag.zorggroep-almere.nl/ shows an invalid cert. Odd that the 32bit shows, but the 64bit has it removed completely. Not sure why I have different results (regarding showing not showing the cert) so I'll test on a few more machines. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 08/31/2011 04:26 PM, NoOp wrote: On 08/31/2011 03:07 PM, Justin Wood (Callek) wrote: On 8/31/2011 5:39 PM, NoOp wrote: On 08/31/2011 12:10 PM, Justin Wood (Callek) wrote: On 8/31/2011 11:43 AM, Rostyslaw Lewyckyj wrote: ... After reading the other postings dealing with 2.3.2, I get the distinct impression that the botched 2.3.2 release was a *panic* Get it out the door quick, reaction to the recent security breach event. Will y'all fix 2.3.2 , and dot the ts and cross the is before re releasing? 2.3.2 was a panic release, because it was an issue actively exploiting users in the wild, on that release day, and had been for a while :( . The only issue with SeaMonkey 2.3.2 that was not in Firefox 6.0.1 was our reported version string. Sadly, that had a few user facing what, why, do I have the right version feelings. Luckily (or unluckily depending on your POV) there is a new chemspill because they took the block slightly further than initially intended, that should be released within 48 hours, that will correct also our version number. I will be doing partial (small) updates for both 2.3.1 and 2.3.2 for that, so hopefully your impact is relatively small. Thank you for your patience. Linux versions are borked (both 32bit and 64bit). Both report 2.3.1. But *worse* is that they reenstate DigiNotar Root CA. Tested both ways: 1. 32bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. Build identifier: Mozilla/5.0 (X11; Linux i686; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 2. 64bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. So I downloaded the entire bz2, deleted the old, and extracted to a new folder; DigiNotar Root CA is now back on that version as well. Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 I've not tested any windows versions (yet). The root CA will still appear in the cert list, but it is blocked, please test with a website. But its a factor of how this code works. Reloaded 2.3.1 (the original) and DigiNotar Root CA shows with trust settings: - This certificate can identify web sites - This certificate can identify software makers https://zga-tag.zorggroep-almere.nl/ works 2.16.528.1.1001.1.1.1.10.1: Certification Practice Statement pointer: http://www.diginotar.nl/cps User Notice: Conditions, as mentioned on our website (www.diginotar.nl), are applicable to all our products and services. Reloaded 2.3.2 64bit (shows 2.3.1) and DigiNotar Root CA now is not showing at all https://zga-tag.zorggroep-almere.nl/ shows an invalid cert. Reloaded 2.3.2 (32bit) and DigiNotar Root CA shows with all trust settings unchecked (similar to Windows). https://zga-tag.zorggroep-almere.nl/ shows an invalid cert. Odd that the 32bit shows, but the 64bit has it removed completely. Not sure why I have different results (regarding showing not showing the cert) so I'll test on a few more machines. Just tested another 32bit: 2.3.1 (Gecko/20110820) shows DigiNotar Root CA with no trust settings ticked. https://zga-tag.zorggroep-almere.nl/ works. Now updating via Help|Check for Updates. Update complete 'Restart SeaMonkey'... SeaMonkey restarted... https://zga-tag.zorggroep-almere.nl/ shows an invalid cert. DigiNotar Root CA shows with all trust settings unchecked. So I reckon that it's working, but odd. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 08/31/2011 03:07 PM, Justin Wood (Callek) wrote: On 8/31/2011 5:39 PM, NoOp wrote: ... Linux versions are borked (both 32bit and 64bit). Both report 2.3.1. But *worse* is that they reenstate DigiNotar Root CA. Tested both ways: 1. 32bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. Build identifier: Mozilla/5.0 (X11; Linux i686; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 2. 64bit linux deleted DigiNotar Root CA and then did the update via Help|Check for Updates. DigiNotar Root CA is now back. So I downloaded the entire bz2, deleted the old, and extracted to a new folder; DigiNotar Root CA is now back on that version as well. Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 I've not tested any windows versions (yet). The root CA will still appear in the cert list, but it is blocked, please test with a website. Further to my other posts following this: If I delete the Root CA cert via: Edit|Preferences|Privacy Security|Certificates|Manage Certificates|Authorities|click on 'DigiNotrar Root CA' and click 'Delete or Distrust' 'OK'. The cert disappears. But the reappears when SeaMonkey is restarted (at least in several instances that I've tested). Why is that? Shouldn't the above _totally_ clear the cert from the database? But its a factor of how this code works. Not really IMO. See my questions above. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SeaMonkey 2.3.2/Mozilla DigiNotrar certs
Added info regarding Justin's 2.3.2 update thread. According to this Register article: quote By Dan Goodin in San Francisco • Get more from this author Posted in Enterprise Security, 31st August 2011 18:34 GMT The secure webpage hosting addons for Mozilla Firefox was targeted in the same attack that minted a fraudulent authentication credential for Google websites, the maker of the open-source browser said. ... /quote Full news article at: http://www.theregister.co.uk/2011/08/31/more_site_certificates_forged/ [Mozilla addons site targeted in same attack that hit Google] Anyone know if there is any truth to that? I now feel our past threads raising concerns regarding auto-update (core and add-ons) now have additional validity. All of the 'it's OK, just trust us' but actually isn't raises it's ugly head - again. Note: I realize this _isn't_ Mozilla's fault, however it does indeed again raise the issue of trusting autoupdates (core and add-ons) defaults. It seems that DigiNotar was aware of the hack some time ago: http://www.wired.com/threatlevel/2011/08/diginotar-breach/ [Google Certificate Hackers May Have Stolen 200 Others] http://www.computerworld.com/s/article/9219663/Hackers_may_have_stolen_over_200_SSL_certificates Gotta love the press release by Vasco/DigiNotar: http://www.vasco.com/company/press_room/news_archive/2011/news_diginotar_reports_security_incident.aspx quote VASCO expects the impact of the breach of DigiNotar’s SSL and EVSSL business to be minimal. Through the first six months of 2011, revenue from the SSL and EVSSL business was less than Euro 100,000. VASCO does not expect that the DigiNotar security incident will have a significant impact on the company’s future revenue or business plans. /quote Anyway; block these guys by upgrading and/or Edit|Preferences|Privacy Security|Certificates|Manage Certificates|Authorities|click on 'DigiNotrar Root CA' and click 'Delete or Distrust' 'OK'. if you can't immediately upgrade. And for more excitement reading, here is the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=682927 [Dis-trust DigiNotar root certificate] ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 8/31/11 2:31 AM, Justin Wood (Callek) wrote: SeaMonkey 2.3.2 is now available as free downloads for Windows, Mac, and Linux from http://www.seamonkey-project.org. As always, we recommend that users keep up to date with the latest stability and support versions of SeaMonkey, and encourage all our users to upgrade to the very latest version. We strongly recommend that all SeaMonkey users upgrade to this latest releases. If you already have SeaMonkey, you will receive an automated update notification within 24 to 48 hours. SeaMonkey 2.3.2 revokes the root certificate for DigiNotar due to fraudulent SSL certificate issuance. For additional details, see http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate. Note: All SeaMonkey users are strongly encouraged to upgrade to the latest SeaMonkey by downloading it from our website or by selecting “Check for Updates…” from the Help menu and clicking on “Update SeaMonkey”. Full news article: http://www.seamonkey-project.org/news#2011-08-31 Release notes: http://www.seamonkey-project.org/releases/seamonkey2.3 System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] Will there be a SeaMonkey 2.3.2 that says it is 2.3.2? What is the difference between installing 2.3.2 versus going to [Edit Preferences Privacy Security Certificates], selecting the Manage Certificates button, selecting the DigiNotar Root CA entry, and selecting the Delete or Distrust button? -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0.10 - Google images problem
chicagofan wrote: That's what my Google search page looks like now, except it has a BIG, multi-colored Google logo above the search field. I hate that new Google multi-colored logo, and that's one of the reasons I want to choose the background. :) Well, to paraphrase a common Midwestern saying, If you don't like Google's logo, wait a minute. They change them daily. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
Interviewed by CNN on 31/08/2011 23:08, David E. Ross told the world: Will there be a SeaMonkey 2.3.2 that says it is 2.3.2? I don't think so. But there will be a 2.3.3. that says it's 2.3.3 pretty soon. What is the difference between installing 2.3.2 versus going to [Edit Preferences Privacy Security Certificates], selecting the Manage Certificates button, selecting the DigiNotar Root CA entry, and selecting the Delete or Distrust button? Not much, I understand. But for many users, the second option is too complicated. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my orbital space station. *Added by TagZilla 0.066.2 running on Seamonkey 2.3.1 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
OK, I think I am ready to upgrade my old SeaMonkey v2.0.14 to the latest ...
... Can I do a separate installation of SM2, or does it have to be over v2.0.14? Thank you in advance. :) -- You're kissing an ant hill. --Mike Nelson /\___/\ Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: OK, I think I am ready to upgrade my old SeaMonkey v2.0.14 to the latest ...
My bloviated meandering follows what Ant graced us with on 8/31/2011 9:31 PM: Can I do a separate installation of SM2, or does it have to be over v2.0.14? Thank you in advance. :) You can have separation installation folders for SeaMonkey and it works just fine. I cannot say the same will be true for any extensions/themes you have in v2.0.14, though. -- Sailfish - Netscape Champion Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/ Rare Mozilla Stuff: https://www.projectit.com/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 8/31/2011 10:55 PM, JD wrote: Justin Wood (Callek) wrote: SeaMonkey 2.3.2 is now available as free downloads for Windows, Mac, and Linux from http://www.seamonkey-project.org. As always, we recommend that users keep up to date with the latest stability and support versions of SeaMonkey, and encourage all our users to upgrade to the very latest version. We strongly recommend that all SeaMonkey users upgrade to this latest releases. If you already have SeaMonkey, you will receive an automated update notification within 24 to 48 hours. SeaMonkey 2.3.2 revokes the root certificate for DigiNotar due to fraudulent SSL certificate issuance. For additional details, see http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate. Note: All SeaMonkey users are strongly encouraged to upgrade to the latest SeaMonkey by downloading it from our website or by selecting “Check for Updates…” from the Help menu and clicking on “Update SeaMonkey”. Full news article: http://www.seamonkey-project.org/news#2011-08-31 Release notes: http://www.seamonkey-project.org/releases/seamonkey2.3 System Requirements: http://www.seamonkey-project.org/doc/2.1/system-requirements [sic] I clicked on Help, Check For Updates and took the update to SM 2.3.1 to update to SM 2.3.2 and restarted SM when requested but when I click on Help, About SeaMonkey, it still says SM 2.3.1. Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 Yes that is a known issue, thank you for reporting it though. I'm not complaining, I've just curious as to what version I have? Has my major security flaw been corrected? It has, there is a followup fix that will be coming soon that will also correct the version # mistake, we'll label it as 2.3.3 You can see my [personal] blog post on this mistake as well: http://blog.drapostles.org/archives/69 -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey 2.3.2 Release -- Corrects Major Security Flaw
On 8/31/2011 10:45 PM, MCBastos wrote: Interviewed by CNN on 31/08/2011 23:08, David E. Ross told the world: Will there be a SeaMonkey 2.3.2 that says it is 2.3.2? I don't think so. But there will be a 2.3.3. that says it's 2.3.3 pretty soon. There will not, but as said there WILL be a 2.3.3 pretty darn soon (probably no later than friday) What is the difference between installing 2.3.2 versus going to [Edit Preferences Privacy Security Certificates], selecting the Manage Certificates button, selecting the DigiNotar Root CA entry, and selecting the Delete or Distrust button? Not much, I understand. But for many users, the second option is too complicated. Not too much, except 2.3.2/3 will make it much much harder to override (if you can even at all in some of these broken cases). Though realize that you do need *at least* 2.3.1 to continue being able to get updates from our update server coming very very soon. And its much much better to just use our .x update than muck with the cert magic yourself. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: OK, I think I am ready to upgrade my old SeaMonkey v2.0.14 to the latest ...
On 9/1/2011 12:31 AM, Ant wrote: ... Can I do a separate installation of SM2, or does it have to be over v2.0.14? Thank you in advance. :) Separate install is fine, you *cannot* reuse the same profile between both versions without corruption though. 2.0.14-later should work just fine (there have been some minor reports relating to bookmarks, but are easily fixable) its the other direction that does not work. So My recommendation (if you have ANY intent/chance you'll revert): * Backup your _profile_ folder * Use help-Check for updates... download/install any update offers, repeat. * You should now be on 2.3.2 (reports as 2.3.1 for now) with your working profile. Alternatively you can install over the old location, or uninstall/reinstall. But the profile backup is your most important step if you want to have the option of going back to (security flawed) 2.0.14 [I don't recommend it] -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
