Re: Find perls user account on windows

Shouldn't a process list on windows show which user runs apache and consequently the script? If that 'consequently' might not be the case, put in a sleep(20) into your script and look at it in the process list

(UPDATED)

Comment on Re: Find perls user account on windows

Replies are listed 'Best First'.
Re^2: Find perls user account on windows by Passenger (Initiate) on Aug 01, 2008 at 12:32 UTC
Problem with apache on the new server is, it uses a fuzzy CGI wrapper that impersonates the actions perl does with the account that is logged in on the content management system. I am not very into impersonation, but I think it does not only matter to whom the process is impersonated, I 'heard/read' its more important to know who impersonates. I don't know what account is used for the impersonating. In IIS its easier for me to determine what account is used, and that's a good point indeed. I'll have a go at that one. Thx! Besides all, I am just beginning with perl. If my issue is a security issue (I can't really think of something else) I would of expect to get a different message returned in $!, other then "No such file or directory" that is. Is this normal perl behavior when it can't open a folder due to security issues?	[reply]

Replies are listed 'Best First'.

Re^2: Find perls user account on windows
by Passenger (Initiate) on Aug 01, 2008 at 12:32 UTC

Problem with apache on the new server is, it uses a fuzzy CGI wrapper that impersonates the actions perl does with the account that is logged in on the content management system. I am not very into impersonation, but I think it does not only matter to whom the process is impersonated, I 'heard/read' its more important to know who impersonates. I don't know what account is used for the impersonating. In IIS its easier for me to determine what account is used, and that's a good point indeed. I'll have a go at that one. Thx! Besides all, I am just beginning with perl. If my issue is a security issue (I can't really think of something else) I would of expect to get a different message returned in $!, other then "No such file or directory" that is. Is this normal perl behavior when it can't open a folder due to security issues?

[reply]