Please don't reply on top (top post). Reply at the bottom so the
conversation can be followed easier.


On Tue, Dec 24, 2013 at 1:18 AM, saravanan p
<[email protected]>wrote:

>
> I am using the below command and now its not asking password but i think
> its not a secure way...
>
>       system("echo systempassword | sudo -S ruby example.rb")
>       example.rb:
>        in this .rb file i am opening my apache2 file and editing
> successfully using ruby File class.
>
>
>
> On Monday, December 23, 2013 12:58:04 PM UTC+5:30, tamouse wrote:
>
>> On Mon, Dec 23, 2013 at 12:59 AM, saravanan p <[email protected]>wrote:
>>
>>> I am trying to edit apache2 https.config file which require sudo
>>> permission through my ruby scripting.
>>>
>>>
>> Be very very careful with this. It can easily leave you wide open to a
>> hack.
>>
>> Assuming you do really mean a ruby script, and nothing in your Rails app,
>> you can set the setuid bit with chmod and chown the script to root. When it
>> executes, it will execute with root persmissions.
>>
>> Given you've not been able to find this information yourself, I'd again
>> caution you not to do this.
>>
>>  --
>

That is insecure, yes.

It is possible to use sudo in situations like this, where you don't really
have user access to type in the password securely.

Sudo can be configured to allow a user to execute a command or a class of
commands with elevated privileges.

Read the sudoers man page for more information on how to set this up.

Nevertheless, I caution you to avoid this situation. I am unclear *why* you
need to do this from inside an application.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/CAHUC_t8oif90%3D3bB6s8hSUDFHH4db6xACKAPSKM_5sg1jidTMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to