It is a terminal, and this will be implemented.
I agree with all of your comments, but not for long.
All of the other code will be used
agreed, BUT! there is a but
if your system is properly secured from the network (firewalls/nats) and OS (good passwords, sshd patched and not on weird demo keys), then adding current directory to the end of the path doesn't do much in the way of security since all other system directories are searched anyway.
in either case, you should be using any priveledged commands under some logged super user utility (sesudo, sudo?, sudoscript, etc.)
I am infallible, you should know that by now.
"My favorite language is call STAR. It's extremely concise. It has exactly one verb '*', which does exactly what I want at the moment." --Larry Wall
(02:15:31 PM) ***TimToady and snake oil go way back...
42 lines of Perl - SHI - Home Site
Understood but in his example it was implied he wanted a sudo. I was demonstrating my way around when I forget to run something I need as root. I do understand the issue of changing permissions that was used in that example. I am just pointing out an alternative if and when you need to fix a missing sudo or anything you may have missed in the previous command.
opps I misread he was not implying a sudo.
Last edited by xsinsx; July 5th, 2010 at 05:09 AM.
Code:SELECT * FROM users WHERE clue > 0; 0 rows returned
I was wondering what was the security risk with adding the . to the Path.
I know that it could be dangerous for running the script as root, but the installation doesn't run it as root.
Last edited by lkjoel; July 5th, 2010 at 07:04 PM.
Posting code? Use the [code] or [php] tags.
I don't care, I'm still free. You can't take the sky from me.
Bookmarks