[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Setuid/gid Error in CVS

From: Gagneet Singh
Subject: RE: Setuid/gid Error in CVS
Date: Fri, 12 Mar 2004 12:46:40 +0530


Thank you for the reply.

I got the problem. I had set the permissions to 2775 for the CVSROOT
folder of the reositories. Now, when I tried to Update , there was no
problem, but CVS sets the permissions except for the history and the
val-tags files in CVSROOT to read-only. Thus, when the above was set, I
got the error message on my GUI window. I think, CVS is not taking the
CVSROOT permissions to be set for the group sticky and that is why it is
giving the problem.

Also, the script had the first line as

This wqs for running the script as a perl script, but this format was
not being considered valid and the valid format being taken is:

#! /usr/bin/perl

I am still trying to mfind the reason, might just be something to do
with the local achine installation.. :-((

Thank you for all the help.

>-----Original Message-----
>From: Larry Jones [mailto:address@hidden
>Sent: Friday, 12 March, 2004 9:32 AM
>To: address@hidden
>Cc: address@hidden
>Subject: Re: Setuid/gid Error in CVS
>Gagneet Singh writes:
>> Can't do setuid
>Standard CVS has no such message.
>> cvs server: Pre-commit check failed
>That implies that you have a commitinfo script that's failing
>-- my guess is that the above error message is comming from the script.
>> When I changed the permissions of the 'cvs_acls' script from 2775 to
>> 2777, the follwoing message is coming, and the loginfo script is not
>> sending the mails, but commits are going through:
>> Setuid/gid script is writable by world.
>That implies that the script is setuid, probably to the wrong
>UID now that you've changed them.  (And note that a
>world-writable setuid script is a gaping security hole.)
>-Larry Jones
>Something COULD happen today.  And if anything DOES,
>by golly, I'm going to be ready for it! -- Calvin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]