read any file on web server.
- Minor port changes
PR: ports/77364
Submitted by: Vivek Khera <vivek@khera.org> (maintainer)
Security: CVE number CAN-2005-0202
- Start using DIST_SUBDIR because of the funkyness of the patch names
- Tweak pkg-plist (duplicate @dirrm/@unexec rmdir, use DOCSDIR, etc.)
- Do not bump PORTREVISION: The default built binaries are unchanged
PR: 57877
Submitted by: Scott Lambert <lambert@lambertfam.org>
Approved by: maintainer
o The recommended GID for postfix is updated.
o Change MAINTAINERship as new address.
PR: ports/56014
Submitted by: Vivek Khera <vivek@khera.org> (maintainer)
vulnerability.
- Add a file, installed to $DOCSDIR, with more explicit post-installation
instructions.
- Update $PKGMESSAGE to point to this new file.
- Add more explicit warnings in various places that MAIL_GID *must* be set at
build time if Mailman is to be used with an alternate (non-Sendmail) MTA.
- Bring port in line with other similar ports by NOT explicitly depending on
Apache. This is both more maintainable and allows the user greater scope
in setting up a custom configuration, including the use of an alternative
web server. (Also, Mailman _can_ be used without a web server.)
- Clean up which documentation files get installed to $DOCSDIR.
- Update $PKGREQ to depend explicitly on Python >= 2.1.3, and not just >= 2.1
- Document required value of $MAIL_GID for Exim4.
- Substantial rewrite of $PKGINSTALL:
- Simplified layout.
- More extensive error checking.
- More expressive and user-friendly output.
- Substantial rewrite of $PKGDEINSTALL:
- Simplified layout.
- More expressive and user-friendly output.
- Delete %%MAILMANDIR%%/data/last_mailman_version in DEINSTALL, and restore
it in POST-DEINSTALL if the entire Mailman installation has not been
removed. This file is required by Mailman's update script (run as part
of the installation procedure) to update active mailing lists.
- Delete the errorlog if it is the only existing logfile. This will
finally allow the mailman port/package to be completely and cleanly
deinstalled when there are no active lists or updated configuration.
- Bump $PORTREVISION, with apologies to those tracking the port.
It should now finally be possible to update a Mailman installation with
active mailing lists simply by deinstalling the port/package, and
reinstalling a later version (or by using portupgrade(1)). There are still
no guarantees, though, and a backup is thorouhly recommended.
- Add patch to Mailman/Defaults.py.in, to correct path to lynx and various
MTAs.
- Change default $MAIL_GID and $CGI_GID values from numerical GIDs to group
names.
- Minor change to $PLIST to ensure clean deinstallation.
- Bump $PORTREVISION
Submitted by: Jan Siml <jsi@jules.de> (Lynx dependency)
- Refrain from invoking ${PERL}
- Call Mailman's distributed check_perms script post-installation to fix file
permissions instead of doing so manually. This is more modular and will
greatly ease maintenance of the port. It implies a level of trust in
check_perms... but then, installing and running any 3rd party software
implies a level of trust.
Should a user...
- use su(1) or sudo to gain root privileges in such a way that his own
environment is maintained, and
- should that user have the variable USERNAME defined in his environment to
point to his own username (not entirely unlikely), and
- should the user install the Mailman port and immediately deinstall it,
... his own userid will be deleted by $PKGDEINSTALL.
The short-term fix implemented here is to munge the names of the variables
used by the port's Makefile.
- Correctly list image directory in $PLIST, even if the user changes it from
the default.
- Add a WITH_APACHE2 knob and document it.
- Bump PORTREVISION
Submitted by: Volker Stolz <vs@lambda.foldr.org> (security issue)
- Actually install the images for Mailman's web front-end to
${PREFIX}/www/icons, instead of depending on the user to do this in a
post-installation step. Add a new build-time variable to control the
location where these images are intstalled.
- Gratuitous change: Change the GNU logo and link in the footer of most
pages in Mailman's web front-end to a "Powered by FreeBSD" logo, and a link
to the FreeBSD home page. This was accomplished by:
- Patching the source to allow for multiple footer bars based on a new
configuration variable LOGO_OS. If LOGO_OS is set to 'FreeBSD', the
FreeBSD footer will be displayed; otherwise, it reverts to the default
GNU footer.
- Set LOGO_OS to 'FreeBSD' in the installed Defaults.py (The user may
override this in mm_cfg.py)
- Bump $PORTREVISION again. (Sorry guys.)
- Add a (non-standard) $PKGOPTS file (currently $FILESDIR/pkg-opts) to
document the user configurable build time variables supported by the port.
Add a target "options" to Makefile to display build time options in a human
readable format. Remove reams of comments from Makefile - superseded by
$PKGOPTS.
- Clean up the killing of running qrunner processes in $PKGDEINSTALL.
- Bump the $PORTREVISION. (Yes, again.)
- Move creation of user/group from $FILESDIR/config.sh to $PKGINSTALL to
ensure they are created if installed from package.
- Switch to using uid/gid which are not yet registered in section 15.15 of
Porter's Handbook.
- Add @exec statements to $PLIST to ensure all necessary directories are
created with the correct modes if installed from package.
- Bump PORTREVISION.
- More to follow...
Partially stolen from: net/cvsup-mirror (PKGINSTALL)
PR: 34654 (uid/gid change)
Submitted by: Sean Chittenden <sean@chittenden.org> (uid/gid change)
maintaining most of the port's existing structure. A more comprehensive
restructuring of this port is in the works.
- Assume maintainership, pending any objections from -ports.
Mailman is software to help manage email discussion lists, much like Majordomo
and Smartmail. Unlike most similar products, Mailman gives each mailing list a
web page, and allows users to subscribe, unsubscribe, etc. over the web. Even
the list manager can administer his or her list entirely from the web. Mailman
also integrates most things people want to do with mailing lists, including
archiving, mail-to-news gateways, integrated bounce handling, spam prevention,
email-based admin commands, direct SMTP delivery (with fast bulk mailing),
support for virtual domains, and more.
PR: 19400
Submitted by: Nick Hibma <n_hibma@calcaphon.com>
