Custom Query (332 matches)

hi bas,

when i create a ticket, i always have an attachment file basje.txt with two lines in (test123 and test1234).

where does it come from ? how can i remove it ?

hi,

i really need your help. i know there is explanations on the wiki but
i
didn't understood them well.
postfix has is own user (for example titi).
one another user run apache and can launch trac-admin(for example
toto).
root can launch trac-admin too(for example tutu).
i created an alias in /etc/aliases for toto to launch email2trac
directly por the project toto. this file is owned by tutu in 644
rights
when i launch the test in tutu user and give the project toto in
argument, with the example mail it works.
when in user tutu i send the example by mail to toto, it doesnt work
and
i have this error in syslog :

Aug 28 17:52:34 crewhub email2trac: IOError: [Errno 13] Permission
denied: '/home/toto/www/trac/VERSION'
Aug 28 17:53:45 crewhub email2trac: Traceback (most recent call last):
Aug 28 17:53:45 crewhub email2trac:   File "/usr/bin/email2trac", line
1060, in ?     env = Environment(settings['project'], create=0)
Aug 28 17:53:45 crewhub email2trac:   File
"/var/lib/python-support/python2.4/trac/env.py", line 126, in
__init__     self.verify()
Aug 28 17:53:45 crewhub email2trac:   File
"/var/lib/python-support/python2.4/trac/env.py", line 174, in verify
fd = open(os.path.join(self.path, 'VERSION'), 'r')


Do you have an idea of misconfiguration ?
Can you give me a procedure to make it works ?

i wait for your answer. thanx a lot.

Denis ROY

Hi Bas,

We are now using a more secure approach to group ownership and file permissions that supports 1) webserver r/w access, 2) r/w access by selected users who are logged in via ssh, and 3) no other r/w access.

The idea is to create a supplementary group whose only members are the webserver user, and the selected ssh users. World access is then removed from all dual-access files (i.e., files writable via webserver and ssh). Thus, with a umask of 007 and the gid bit set, all created dual-access files are group-writable by users belonging to the special supplementary group, and to no one else.

Currently, besides the uid, run_email2trac sets only the gid associated with the trac user. This patch will cause it to also set the supplementary groups associated with the trac user, thus supporting a "best practices" approach to dual-access.

Let me know if you have any questions.

Dennis McRitchie?