Jason Haar wrote:
On Sun, May 16, 2004 at 08:56:19PM -0500, Bookworm wrote:Okay - most people put the wrapper right next to the original (/var/qmail/bin/qmail-scanner-queue.pl). My "complaint" as such wasn't that it didn't do everything for me - it does only what it is supposed to do - it was that there wasn't anything obvious in there. Maybe just a line at the top of the script, saying "If you have a wrapper, run this script setuidgid." Other than that, I don't see a reason to change anything. Trying to go through and say "Okay, here's where the .pl file is, is the wrapper next to it, if the wrapper is there, let's try feeding through the wrapper.." - and so forth - would be too much work for too little benefit. Just because I like not having suid-perl doesn't mean it's normal behaviour. Running 'setuidgid qscand /<pathto the script>/contrib/test_installation.sh' isn't hard.
Problem #1 - the compile, rather than just saying "You don't have SUID Perl, do you want to continue, Y/N" (which, to me, would make sense), simply dies - as if, of course, everyone wants to have suid. (yes, I know about the --skip-setuid-test option - hard as it is to find in the documentation - but should it really be necessary?)
Way back it used to say that - but people kept complaining about setuid issues - i.e. the ignored the warning. So I made it stop.
You are right - a "hit enter to continue" would be better
Problem #2 - once you have run through the install, put in the wrapper, removed taint, and so forth, you then proceed to run test_installation.sh. This is too stupid to check to see if the wrapper exists, so it will ALWAYS die on you, unless you run it setuidgid qscand. (which isn't documented anywhere - and no, it's not that obvious)
Well it can't think of everything. As you have installed the C-based wrapper, where is it? People install that with many names. So the script defaults to qmail-scanner-queue.pl. However, if you set QMAILQUEUE appropriately before calling it - it'll use that instead.
I'll change the script from
echo "setting QMAILQUEUE to $QMAILQUEUE for this test..."
to
echo "QMAILQUEUE was not set, defaulting to $QMAILQUEUE for this test..."
That should give you an indication of what you need to do to make it work in your environment
Thus - 'added documentation' rather than 'change the code'. Minimal effort, maximum return.
It doesn't. I chown it to qscand.qscand. I can't figure out what in the install script is using root, instead of qscand.Oddball Issue - the /var/spool/qmailscan directory is, on the whole, created qscand. - For some odd reason, the /var/spool/qmailscan/tmp directory, however, is root.root - anyone seen a reason for that behaviour that I have missed?
That's plain wrong. Your system shouldn't even be working if that's the case!
Question - for the -g initialization option, I've seen qmaild, qmailq, and qscand. Which is right? Is it the same for -z? (conflicting documentation and examples)
They are all right. As it's setuid qscand, it doesn't matter what you run it as.
system like this. I can barely debug my own issues in trying to configure packages. I'm just trying to provide more information, as well as general feedback. I DEFINITELY appreciate the effort - Jason,
Fine by me! Anything to reduce the amount of confusion
What? No wish list? :)
Troy
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
