guys here's a section of my program written in perl. This part is used to create directories with 777 mode. Now i know about 777 being a security hole. Could anyone provide me a possible solution to this using suexec?????????
Segment
system mkdir ".$file_folder", 0777 or die "Can't make dir: $!";
system "chmod 777 .$file_folder";
well its just that I'm a total noob in everything related to Unix.
What i meant there was , in the code segment as u can see directories are created with 777, i was wondering how suexec can be used to overcome that problem in the code???
i did ask about that , my superior told me that apache logged in differently on the server i am working on and it needs apache to have all permissions(dont ask me about that ) and boss says he wud appreciate it if the soln was an suexec one
Umm dont get me wrong buddy, but me being a newbie to all this just dont get the significance of that. ok if suexec is the problem mind telling me a diff scenario in which i cud change that 777 hole
ok just a quick question Neo, Did i bump my thread on the same day multiple times?? or just a few hours apart? I dont think so. I checked and I saw that the threads above mine had been well attended to and thats why i decided to bump. Look i wudnt have done it if I was'nt desperate for help here. This being a Unix forum and all I thought would be the right place to get all the help. Neo no offence to you but if you had said that you didnt have an answer , I would have gladly stopped bumping. As it is I wont post in this thread again , so no worries about that, Thanx for ur time. When you say its a forum for all newbies, alteast be less harsh on them. They come in here looking for help and if cold silence warnings are all they receive then maybe this forum should be renamed without the newbie in it
It doesn't matter when and how you bumped the post, you did bump all the same, which is against the rules of the forums. If you had read the rules before posting you would have realised that it is not accepted regardless of whether you're a newbie or a guru.
Also; it isn't "cold silence". What would be the point of people posting to say "I don't have a solution"? - We'd end up with long pointless threads with no answers in them. If people have a solution to your problem, then they will respond to your post. People did give you plenty of advice, assistance and links to resources containing information that might help.
As Neo indicates, please review the rules. The rules and guidelines are there to keep the standard of technical discussion high, rather than people just having conversations about how they can't help one another.
I'll leave the thread open for now, but I'm sure either Neo, myself or another mod will close it if a pointless argument ensues.
Ok. let me first say that I really dont know much about suExec other than what I just read. However, the links that I posted provide ample information regarding compiling, testing, and using suExec. It would be much more helpful if you would post information back as you encounter issues with your installation. I think then you may get a better experience from this message board (by the way, it really is a great board with lots of talented individuals. Have some patience and follow a step wise approach to your problem and you will be able to overcome it) Based on that however, before anyone can really help you, you must first provide some more information. Such as:
What have you done so far other than write the Perl program you posted? What can you tell us about your Apache configuration?
Has suExec been compiled with the correct configuration options? If not, see the link that I posted above and it will provide information regarding how to configure suExec.
suExec works from user/group/virtual host directives that you define when you compile suExec. You must have compiled these options into your suExec binary.