[SM-CVS] CVS: squirrelmail/doc/ReleaseNotes/1.4 Notes-1.4.8.txt, NONE, 1.1.2.1

[Thijs K. <ki...@us...>]

Update of /cvsroot/squirrelmail/squirrelmail/doc/ReleaseNotes/1.4
In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv1904/doc/ReleaseNotes/1.4

Added Files:
      Tag: SM-1_4-STABLE
	Notes-1.4.8.txt 
Log Message:
cvs now defrosted and ready for continued development


--- NEW FILE ---
/*****************************************************************
 * Release Notes: SquirrelMail 1.4.8                             *
 * The "F is for Furry Friends" Release                          *
 * 11th August 2006                                              *
 *****************************************************************/

In this edition of SquirrelMail Release Notes:
   * All about this Release!
   * Locales / Translations / Charsets
   * Security issues
   * Major updates
   * A note on plugins
   * Reporting my favorite SquirrelMail 1.4 bug


All about this release
======================

This version, 1.4.8 is a maintenance release, addressing
the following problems since 1.4.7:
- A security fix (see below)
- A collection of bugfixes
(see ChangeLog for a full list)


Locales / Translations / Charsets
=================================

Since the release of 1.4.4, the the translations for SquirrelMail are
no longer part of the main package but have to be downloaded separately;
either in one large file or an individual language. You can find these
packages through our homepage. They also contain instructions on how
to install.

That release also introduced a backport of the new Character set
decoding functions from the development branch, vastly increasing the
number of supported character sets and decoding performance.


Security issues
===============

This release addresses a security issue found since the release of 1.4.7:

compose.php allowed a logged in attacker to overwrite random variables
in that script. This could possibly be used to modify or read the preferences
of other users or write arbitrary files. It must be noted that the requirement
of being logged in mitigates the attack possibilities, unless your users have
weak passwords. This was found by James Bercegay of Gulftech Security, thanks!
This is CVE-2006-4019.

Also, in 1.4.7 we put code to address CVE-2006-3174. On further investigation,
we've further tightened that code in 1.4.7 to close off some rare corner cases.
We do not believe this to be anything more than a minor fix.


Major updates
==============

The 1.4.x series (as a result of 1.3 developent series) brings:

* A complete rewrite of the way we send mail (Deliver-class),
  and of the way we parse mail (MIME-bodystructure parsing).
  This makes SquirrelMail more reliable and more efficient
  at the same time!
* Support for IMAP UID which makes SquirrelMail more reliable.
* Optimizations to code and the number of IMAP calls; SquirrelMail
  is now a very scalable webmail solution.
* Support for a wider range of authentication mechanisms.
* Lots of bugfixes, some new features and a couple of UI-tweaks.


A note on plugins
=================

There have been major plugin architecture improvements since 1.2.x. Lots
of plugins have not yet been adapted to this. Plugins which are
distributed with this release (eg. in the same .tar.gz file) should work.
Plugin authors will need some time to adapt their plugins, so quite a few
plugins that did work with 1.2.x might not work with 1.4.x.

So if you have ANY problem at all, first try turning off all plugins.
If one plugin seems to be the culprit, contact the author to see if
a 1.4.x version is underway.

Plugins that worked with previous 1.4.x versions should continue to work
without changes with this version.


Reporting my favorite SquirrelMail 1.4 bug
==========================================

We constantly aim to make SquirrelMail even better. So we need you to
submit any bug you come across! Also, please mention that the bug is
in this 1.4.8 release, and list your IMAP server and webserver details.

   http://www.squirrelmail.org/bugs

Thanks for your cooperation with this. That helps us to make
sure nothing slips through the cracks. Also, it would help if
people would check existing tracker items for a bug before reporting
it again. This would help to eliminate duplicate reports, and
increase the time we can spend CODING by DECREASING the time we
spend sorting through bug reports. And remember, check not only OPEN
bug reports, but also closed ones as a bug that you report MAY have
been fixed in CVS already.

Any questions about installing or using SquirrelMail can be directed
to our user support list:

    squ...@li...

If you want to join us in coding SquirrelMail, or have other
things to share with the developers, join the development mailinglist:

   squ...@li...

                  Happy SquirrelMailing!
                    - The SquirrelMail Project Team