HylaFAX 4.1.3 Release
The HylaFAX development team is pleased to announce our 4.1.3
patch-level release! The release represents many hours of work and
testing by developers and contributors, and our thanks goes to all who
participate and provide feedback.
The source code for the 4.1.3 release can be downloaded from:
(md5: b3e95810a7fc99685f92faa8ff59114e 1,269,098 bytes)
* * *
This document is intended to describe the significant differences
between hylafax-4.1.3 and older releases, point out any known
incompatibilites and issues, and provide the reader with directions to
further resources regarding HylaFAX.
* NEW FEATURES *
Please refer to CHANGES for a detailed list of code changes
- support for MultiTech Real-Time Fax Compression Conversion via new Class2RTFCC option
- support for Class 2.1 and V.34-fax (Super G3) modems
- gcc version 3 support
- new 'sendfax -z' option to read destinations from a file
- support for Solaris DSOs
- additional modem support for various MultiTech, Eicon, Sedlbauer, Comtrol, and Davicom modems
- new Class2PTSQueryCmd and Class1TCFRecvHack config options
- job archival support
* KNOWN ISSUES *
Please refer to HylaFAX Bugzilla for a detailed list of issues.
- HylaFAX corrupts images received in 2D-MMR.
- Specific support for fax class 1.0 is not yet implemented.
- NSF can be parsed incorrectly if the modem doesn't report it in hex.
- sendfax use of ~/.hylarc differs from its use of hyla.conf
* INCOMPATIBILITIES *
- faxinfo from older installations of HylaFAX will not give correct output when run against newly received fax image files. faxinfo from 4.1.3 can read both newly received and older fax image files.
- The popular faxrcvd-mail scripts have been deprecated by FILETYPE use in FaxDispatch, and unchanged, will not work with faxgetty in 4.1.3. See 'man faxrcvd' for details.
- Failed faxes now have status "F" instead of "D". Most client programs which display/report job status will need some alteration to accomodate this.
* WHO SHOULD UPGRADE? *
4.1.3 includes fixes for a remote format string vulnerability which could be abused in a denial of service attack. Also fixed is a buffer overflow condition when receiving fax image data which potentially could be exploited to execute arbitrary code as root. Also present in 4.1.3 are fixes for several other local remote format string vulnerabilities which, in some installations, could lead to elevated privileges by abuse. Everyone is advised to upgrade.
* HYLAFAX BINARY PACKAGES *
Binary packages for some operating systems and platforms are available. Please see ftp://ftp.hylafax.org/binary/ and http://www.hylafax.org/howto/install.html#ss2.3.3 If you are able and willing to produce a binary package of HylaFAX for general distribution, then you are invited to join firstname.lastname@example.org and solicit your binary package.
* COMMERCIAL SUPPORT *
HylaFAX.org has partnered with iFax Solutions, Inc. to provide commercial support to HylaFAX users. Single-incident and annual support options are available, as well as a variety of consulting services. Contact HylaFAX Sales for more information.
* FREE SUPPORT *
HylaFAX has numerous support resources available. The user is encouraged to utilize the manpage documentation before turning to other support arenas. However, if other support is desired, or if you would like to actively take part in the HylaFAX community, you are invited to:
* join and participate in a HylaFAX mailing list
When corresponding about this software, please always specify:
- what version of HylaFAX you have,
- what system you're running on (if it is Linux please name the
- if the problem is modem-related, identify it and the firmware rev
For example: "HylaFAX v4.0pl2 under RedHat Linux 4.2 with gcc 2.7.2;
ZyXEL 1496E with 6.11a firmware."
* read the on-line documentation and resources
See: http://www.hylafax.org and http://www.hylafax.org/howto
* review HylaFAX CVS
* report confirmed bugs, feature requests, and submit patches
The HylaFAX development team
And now, a note from HylaFAX's original author ;-)
Silicon Graphics has seen fit to allow me to give this work away. It
is free. There is no support or guarantee of any sort as to its
operations, correctness, or whatever. If you do anything useful with
all or parts of it you need to honor the copyright notices. I would
also be interested in knowing about it and, hopefully, be acknowledged.
Finally, note that this software is called ``HylaFAX'', not ``Hylafax'',
``hylafax'', and certainly not ``FlexFAX'' (the old name which someone
else has a copyright on). If you want to refer to this software use
``HylaFAX (tm)'' and be sure to honor the Silicon Graphics trademark.
Use and Copyright
Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.
HylaFAX is a trademark of Silicon Graphics
Permission to use, copy, modify, distribute, and sell this software and
its documentation for any purpose is hereby granted without fee, provided
that (i) the above copyright notices and this permission notice appear in
all copies of the software and related documentation, and (ii) the names of
Sam Leffler and Silicon Graphics may not be used in any advertising or
publicity relating to the software without the specific, prior written
permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
OF THIS SOFTWARE.
Last updated $Date: 2002/07/29 18:36:10 $.