Great Circle Associates Majordomo-Users
(February 1993)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: fyi majordomo on bsd/386
From: Barbara Dyker <barb @ locutus . cs . colorado . edu>
Date: Tue, 2 Feb 1993 16:32:54 -0700
To: majordomo-users @ GreatCircle . COM

--- forwarded message ---
Return-Path: polk@BSDI.COM
Received: from hilltop.BSDI.COM by Wire.COM (5.67/1.37)
	id AA06059; Tue, 2 Feb 93 15:22:11 -0700
Received: by hilltop.BSDI.COM (5.67/1.37)
	id AA09562; Tue, 2 Feb 93 15:21:09 -0700
Message-Id: <9302022221.AA09562@hilltop.BSDI.COM>
To: "Jason Ornstein - Under The Wire, Inc." <ornstein@Wire.COM>
Subject: Re: problems with majordomo 

In-Reply-To: Your message of Tue, 02 Feb 93 15:04:56.
Date: Tue, 02 Feb 93 15:21:09 MST
From: Jeff Polk <polk@BSDI.COM>

> I am installing the latest version of majordomo and have run across a
> problem that I seem to be at a loss to solve.  I don't think that it
> is a majordomo problem, but it might be.  The system that this is
> being installed on is bsd/386 from bsdi.

> The problem is that if wrapper is as follows

> -rwsr-sr-x  1 daemon  mjrdomo  23287 Feb  2 14:55 wrapper*

> majordomo-owner gets the following mail when majordomo is sent a request


>   To:      owner-majordomo
>   From:    MAILER-DAEMON (Mail Delivery Subsystem)
>   Subject: Returned mail: unknown mailer error 2


>      ----- Transcript of session follows -----
>   Can't run setuid script with taint checks.
>   554 "|/usr/local/mail/majordomo/wrapper majordomo"... unknown mailer  
error 2
>   

>      ----- Unsent message follows -----
>   Received: by Wire.COM (5.67/1.37)
>   	id AA05778; Tue, 2 Feb 93 14:55:53 -0700
>   Date: Tue, 2 Feb 93 14:55:53 -0700
>   From: ornstein (Jason Ornstein)
>   Message-Id: <9302022155.AA05778@Wire.COM>
>   To: majordomo
>   

>   help

> If I change the ownership of wrapper to root, everything works like it
> should.

> If anyone has any helpful hints concerning this I would love to hear
> them.  Also, if there aren't any hints, maybe what the possible risks
> of leaving wrapper owned by root are.

> Thanks.

> -jason
> -----
> Cogwheel Incorporated, Boulder  ***  Producers of low-cost dialup IP  
routers
>                         Boulder-Denver/Hong Kong

This is a problem with setuid scripts in BSD/386.  There just isn't
any way to do it at the moment (the majordomo server on BSDI.COM is down
right now for this very reason).  I'll let you know as soon as I
get the fixed exec.c for the kernel.

Jeff

 ==========================================================================
          /\      Jeff Polk             Berkeley Software Design, Inc. 

       /\/  \     polk@BSDI.COM         7759 Delmonico Drive
      /  \   \    719-260-8114          Colorado Springs, CO  80919
 ==========================================================================


------- End of Forwarded Message




Indexed By Date Previous: problems with majordomo
From: "Jason Ornstein - Under The Wire, Inc." <ornstein@Wire.COM>
Next: MajorDomo services?
From: Bruce_Hamilton.LAX1B@xerox.com
Indexed By Thread Previous: problems with majordomo
From: "Jason Ornstein - Under The Wire, Inc." <ornstein@Wire.COM>
Next: Re: fyi majordomo on bsd/386
From: Brent Chapman <brent@GreatCircle.COM>

Google
 
Search Internet Search www.greatcircle.com