Darley Ware <[EMAIL PROTECTED]> writes: > /usr/local/tmda/bin/tmda-address -n -c /home/dom/tmda/jdoe/.tmdarc -a > [EMAIL PROTECTED] -d 23h > > When I run this command manually as root I get the following error... > > > Traceback (most recent call last): > File "/usr/local/tmda/bin/tmda-address", line 104, in ? > from TMDA import Defaults > File "/usr/local/tmda/TMDA/Defaults.py", line 1418, in ? > raise Errors.ConfigError, "Can't find key file: " + CRYPT_KEY_FILE > TMDA.Errors.ConfigError: Can't find key file: /root/.tmda/crypt_key
TMDA looks for the cryptographic key in 'DATADIR/crypt_key'. This has been the case since crypt_key was introduced. DATADIR is '~/.tmda/'. So when you run as root, TMDA looks for /root/.tmda/crypt_key. The only ways I can think to change this are either to change DATADIR to point to the '.tmda' directory that contains the crypt_key you want to use, or to simply change CRYPT_KEY_FILE. Both of these can be set in your config (.tmdarc) file. Perhaps you had set one of those variables and then removed it? What you are seeing *is* TMDA's correct, default behavior. > I recently upgraded from tmda-0.65 to tmda-0.68. The script works fine in > tmda-0.65. I have no idea why this is. The crypt_key file was added in 0.56. It has always worked the way it does. > So my question is, what has changed, and how do I fix it? Well, I can't imagine what it was. The code for 0.65 that loads the crypt_key looks the same to me as the code for 0.68. Actually, I have something just a little bit past the 0.65 release, but looking at the ChangeLog, I can't see anything that would have affected this. Could you post your config file and your /etc/tmdarc, if you have one? Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
