Re: protecting SQL login info

2005-09-06 Thread Dan Mahoney, System Admin
On Tue, 6 Sep 2005, Michael Parker wrote: Dan Mahoney, System Admin wrote: With spamc/spamd this is not a problem, as spamd runs on a machine that the shell users don't have access to (and reads the SQL login as root before dropping its privileges). However, for sa_learn, and things like spa

Re: protecting SQL login info

2005-09-06 Thread Michael Parker
Dan Mahoney, System Admin wrote: > > With spamc/spamd this is not a problem, as spamd runs on a machine > that the shell users don't have access to (and reads the SQL login as > root before dropping its privileges). > > However, for sa_learn, and things like spamassassin -r (which > essentially is

Re: protecting SQL login info

2005-09-06 Thread Dan Mahoney, System Admin
On Tue, 6 Sep 2005, Eric W. Bates wrote: This is perhaps a little elaborate; and I have not tried to hook this into SA; but we are quite happy with a little bit of misdirection we use for the tools we have reading/writing to the SQL. There is a specified directory (call it dbpasswords). In the

protecting SQL login info

2005-08-19 Thread Dan Mahoney, System Admin
Hey all, I'm doing everything (bayes, AWL, userprefs) in SQL. Is there some way to protect the values I've got in /etc/mail/spamassassin/local.cf such as my mysql username and password from casual snoopage? Only think I could think of was to make SA setGID, and have the file chmod 750. An