167062 - Wrong file owner set by checkconfig.pl

Status: RESOLVED INVALID

(Bugzilla :: Installation & Upgrading, defect)

Description

[Hans-Fredric Österlund]

After running checkconfig.pl (as root), root is set as the file owner of all
files in the buzilla folder (incl subfolders) and that results in that they
can't be reached by the web server.

Since I'm using an Apache web server, changing the file owner to apache solves
the problem. But if I run checkconfig.pl again, then I also have to change the
file owner again for all files (except for some files, ex localconfig where
owner root is quite OK).

Comment 1

[Zach Lipton [:zach]]

You mean checksetup.pl, right? Unless debian has something I don't know about, there 
isn't a checkconfig.pl.

Try setting 'webserveruser' and 'webservergroup' in localconfig to whatever user and 
group your webserver runs as. You will still need to run checksetup as root, but it should 
change the owner and group of files as needed to whatever you set webserveruser and 
webservergroup to. 

Comment 2

[Hans-Fredric Österlund]

Attachment: Re-hacked for use of webserveruser variable

Comment 3

[Hans-Fredric Österlund]

Jepp, I meant checksetup.pl, sorry for that.

There is no 'webserveruser' and neither any handling for such a variable in the
perl code. In checksetup.pl the sub fixPerms is called with "$<" as the
parameter for owner, actually the owners uid, and there are also a note in the
source code that says "there should be a $bugzillauid" parameter.

You also have to use getpwnam to convert the text based name to the uid number
needed by the fixPerms sub. I have attached my "re-hacked" checksetup.pl file,
that seems to do the job :-) (Current from cvs/HEAD (2002-09-09) +
$webserveruser fix).

Comment 4

[Shane H. W. Travis]

Max, I'm trying to triage old bugs, and you're the guy that's been pokind 
around in checksetup more than anyone else I know. From what I see, the problem 
described by this bug is either no longer a problem, or never was a problem. 
Can you confirm one way or the other please? Thanks!

Comment 5

[Max Kanat-Alexander]

Actually, you need to set webservergroup, which will allow apache to read the
files if it's in that group.

It is used, and it does work. It even works for non-root users.

The owner will always be you.

The web server should *not* be the owner, as the web server could then write to
the CGI files, which could be dangerous.