Thank you very much for your detailled insights, I will try to read those looking at mod_wsgi source code. As for setting 'private file' ownership directly to the application user, I am not sure this allow to meaningfully enhance application security. Main risk we are trying to mitigate, is the one of an 'exploit' on application, at the end of which the attacker will have gained the privileges of application effective user. If 'private file' is directly owned by this user, the attacker would be in position to read it. I need to brush up my knowledges of Unix file security, but keeping on the pragmatic approach of manually setting 'private file' permission on something that can be handled by the modwsgi processes, maybe something along this road could fly : * private file is owned by user1, groupuser1 ... * application is run as user2 where user2 is a member of groupuser1 * when instantiating the wsgi application (process startup), we parse private file and somehow drop membership of groupuser1 I am unsure python allow us to do that.
-- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
