On Thu, 12 Aug 2010 14:08:12 -0700
Gary Funck <g...@intrepid.com> wrote:

> On 08/12/10 01:42:57, Stevan Bajić wrote:
> > btw: dspam_stats works perfectly if you call it as a normal user.
> > 
> > I took now the time to test it. First I called it with just a normal user:
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> > someu...@theia / $ dspam_stats
> > Unable to read dspam.conf
> > Okay. It can not read dspam.conf. Let me give the user
> > the right to read dspam.conf (dangerous since passwords
> > for the storage and such are there but anyway... for the
> > test it's okay) [...]
> 
> As installed in the rpm, dspam_stats is owner/group = root/root.
> If that were changed to root.mail, setgid, then dspam_stats
> would have access to /etc/dspam.conf which is owner/group = root.mail
> already.
> 
> I'm using the version packaged with FC13: dspam-3.9.0-7.fc13.x86_64
> 
> I have it configured to use the hash storage engine
> and I have install the dspam-hash paackage.
> 
> As my user-id (gary):
> $ dspam_stats
> <no output>
> $ dspam_stats gary
> <no output>
> 
> As super-user:
> $ sudo dspam_stats
> gary
>     TP:  6536 TN:  8351 FP:    38 FN:   120 SC:     0 NC:     0
> 
> [...]
> > Try again the same but this time using another username than my own:
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> > someu...@theia / $ dspam_stats -S -H anotheruser
> > Program mode requires special privileges, e.g., root or Trusted User
> 
> Is this something that you have recently implemented
> in the git repository?
>
Yes. I implemented it because of your feedback.


> Because, that isn't the behavior
> that I'm seeing.
> 
Checkout the GIT version.

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to