Thanks for the education!
I am planning a workaround. If I hit success, I will write again - hoping you
guys won't mind...
-Original Message-
From: Pierre Gaston [mailto:pierre.gas...@gmail.com]
Sent: Thursday, January 12, 2012 4:30 PM
To: Sarnath K - ERS, HCLTech
Cc: bug-bash@gnu.org; b
On Thu, Jan 12, 2012 at 12:51 PM, Sarnath K - ERS, HCLTech
wrote:
> Oops.. It actually works! That's a great catch!
>
> I thought "redirection" is not supported in restricted mode though..!
> I just checked... It is mostly related to "output" re-direction.
>
> Hmm..I think I am going to tinker
Oops.. It actually works! That's a great catch!
I thought "redirection" is not supported in restricted mode though..!
I just checked... It is mostly related to "output" re-direction.
Hmm..I think I am going to tinker "bash" source code to disable the "echo"
builtin. :-)
Any ideas?
-Ori
On Thu, Jan 12, 2012 at 12:26 PM, Sarnath K - ERS, HCLTech
wrote:
> Hello Jonathan,
>
> Thanks for your inputs. I was able to created a super-restricted login.
> Here are a few things that I learnt during this process:
>
> 1. "vim" has a restricted mode called "rvim (or) vim -Z". This way, I can
Hello Jonathan,
Thanks for your inputs. I was able to created a super-restricted login.
Here are a few things that I learnt during this process:
1. "vim" has a restricted mode called "rvim (or) vim -Z". This way, I can
restrict the user from running shell commands from vim and peep into the
Fil
