From majordomo-announce-owner Fri Jan 13 01:21:12 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id AAA14597 for majordomo-announce-outgoing; Fri, 13 Jan 1995 00:40:20 -0800 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id OAA14478 for ; Wed, 11 Jan 1995 14:32:34 -0800 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA06535 (5.65c/IDA-1.4.4 for ); Wed, 11 Jan 1995 17:30:24 -0500 Message-Id: <199501112230.AA06535@cs.umb.edu> To: majordomo-announce@greatcircle.com Subject: Majordomo version 1.93 released Date: Wed, 11 Jan 1995 17:30:21 -0500 From: "John P. Rouillard" Sender: majordomo-announce-owner@GreatCircle.COM Precedence: bulk This is primarily a security patch release. While I was at it, I also fixed a few of the bugs that were really annoying in 1.92 and added a real license. The release is available from: ftp.greatcircle.com:/pub/majordomo/majordomo-1.93.tar.Z This release fixes a nasty security bug in archive2.pl and a few race conditions with security implications in resend and digest. The top of the README follows. 1) a coding error in archive2.pl that allowed people to write any files owned by majordomo are fixed. The archive file that was opened could have been replaced with a symbolic link during the time period between the link check and the open. Now we check the inode and device numbers of the file using its name and the open file descriptor. We abort if they do not match. Because of this, there is a new array in majordomo.cf (or sample.cf in the distribution) called @archive_dirs. This is an array of the fully qualified pathnames to all of the archive directories. The perl conisent may want to set the array using a glob style assignment to avoid having to set hundreds of elements in the array. 2) a race condition with consequences the same as in #1 was solved in digest and resend. No additional actions are necessary to make use of these fixes. In cases 1 and 2 the following assumptions were made: 1) Only written files are subject to the problems Opens on pipes, or to read files are not a problem. 2) Any file in $listdir can never have a race condition. If the mode on that directory is world writable, then anybody can write the list files and give themselves whatever access they want anyway. This means that all of the lopen calls were able to remain the same. However, I did replace the lock file open call inside of the shlock.pl package with a safer version. This is to permit a future version of the lopen and shlock calls to have an extra argument that is the name of the lock file to create. 3) the unlink of the /tmp/resend files is fixed 4) Perl 5 syntax errors have been cleaned up by quoting @, and $ where they occur. NOTE: majordomo hasn't yet been validadated under perl 5, perl 4.036 is now the primary development perl version. Also a glob operation in approve has been fixed to work under perl 5. 5) When running under posix systems (e.g. solaris), setgroups() is called to clear out any other groups that may be inherited from the parent sendmail. When the wrapper is compiled using setgroups, strings(1) will show the string "setgroups_was_included". Setgroups may not work if the euid is not root, and this case is silenty accepted. Otherwise the wrapper will exit if setgroups fails for some other reason. 6) A test script (called test) is provided to list the groups that the wrapper is imposing. To use it, copy it to $W_BIN and fire up the wrapper: /path/to/wrapper test 7) A new majordomo license has been provided in the file LICENSE. This replaces the previous copyright, so you should read it. You should not be using this software without reading the LICENSE and agreeing to it. 8) The characters @ and ! are allowed in advertize/noadvertize strings. 9) The administrivia chacks in resend have been improved 10) The which and lists commands now use opendir/readdir instead of globbing the directory which should permit them to still work with thousands of lists. 11) A bug in approve that stopped an error message from being displayed has been fixed. 12) Experimental code to permit X.400 and other addresses with '/' in them has been included. It must be enabled in majordomo.cf. 13) The null argument added to sendmail invocations has been eliminated. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x103 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-announce-owner Tue Oct 17 17:00:54 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA01989 for majordomo-announce-outgoing; Tue, 17 Oct 1995 16:56:51 -0700 Received: (mcb@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA01390 for majordomo-announce; Tue, 17 Oct 1995 16:33:36 -0700 Message-Id: <199510172333.QAA01390@miles.greatcircle.com> From: mcb@greatcircle.com (Michael C. Berch) Date: Tue, 17 Oct 1995 16:33:36 +0000 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: majordomo-announce Subject: ADMIN: majordomo-users list crashed; please re-subscribe Sender: majordomo-announce-owner@GreatCircle.COM Precedence: bulk It appears that the majordomo-users list hosted at GreatCircle.COM was truncated in a system problem about a week or so ago. (We keep list backups to help alleviate this, but it doesn't go back far enough in this case.) I'm sending this to the majordomo-announce list in the hope of finding most of the people who were subscribed; if you are not interested in the majordomo-users list, please ignore this. If you were on majordomo-users (majordomo-announce and majordomo-workers are fine, no problem with those) and have not recently (in the last few days) re-subscribed, please subscribe again by sending the appropriate subscribe message to majordomo@greatcircle.com. (You can use the Majordomo "which" command first if you like, to make sure you aren't already on the list.) We apologize for the inconvenience. -- Michael C. Berch Postmaster and List Manager, Great Circle Associates mcb@greatcircle.com