All I did was chmod o+r /root. This allowed CVS to look into /root to see if
a .cvsignore file existed, found that there wasn't and carried on.

What changes did you make to inetd.conf regarding env as this would seem
more secure than giving all read access to /root?

Regards,

John Scott

-----Original Message-----
From: Hennink Tijmen 44541 [mailto:[EMAIL PROTECTED]]
Sent: 04 July 2000 20:38
To: Marinalva Dias Soares
Cc: [EMAIL PROTECTED]
Subject: Re: cvsignore problem.


This is not a very secure solutions cause you're creating root-access for
normal users.
I've already found the solution with env in inetd.cond

Tijmen

On Tue, 4 Jul 2000, Marinalva Dias Soares wrote:

> On Tue, 4 Jul 2000, Hennink Tijmen 44541 wrote:
> 
> The root directory must be with permissions 755. I had this problem
> because my root directory didn't have correct permission.
> 
> Marinalva.
> 
> > Hello,
> > 
> > I have a problem with using CVS with it's pserver.
> > When connecting I get the following error.
> > [hennink@patrijs test]$ wesp cvs -d
:pserver:hennink@localhost:/home/henn
> > ink/cvsroot checkout project
> > cvs server: cannot open /root/.cvsignore: Permission denied
> > cvs [server aborted]: can't chdir(/root): Permission denied  
> > 
> > According to the manual I have a file cvsignore in
> > /home/hennink/cvsroot/CVSROOT but cvs doesn't use it.
> > 
> > What's wrong?
> > 
> > with regards,
> > 
> > Tijmen
> > 
> > 
> 
> 


********************************************************************
The information contained in this message or any of its
attachments may be privileged and confidential, and is
intended exclusively for the addressee.

The views expressed may not be official policy, but the
personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution,
dissemination or use of this communication is not authorised.

If you have received this message in error, please advise
the sender by using the reply facility in your e-mail software.

All messages sent and received by Argos Ltd. are checked
for malicious content.
********************************************************************

application/ms-tnef

Reply via email to