sudo ... -u <user> ...  runs as user.  Unless your user is root...

Perhaps I'm missing something.

Oh!  Wait!  Are you using %python ?  User_impersonate only works with %sh.

And that brings me to this:

After all of this, I find that user_impersonate is not very useful.  Yes,
it does what is says, but only for %sh.
So, in a mixed language notebook, if I have user_impersonation enabled in
%sh, then I get this: (See attached screenshot)
I started to write up a Jira request, but I probably don't understand the
culture well enough.

I'm back to running all zeppelin processes as zeppelin, and I'm going to
get 0.8 running from source to compare.


On Thu, May 10, 2018 at 5:29 PM, Jhon Anderson Cardenas Diaz <
jhonderson2...@gmail.com> wrote:

> Yes I did the sudoers configuration and i am using zeppelin user (not
> root) to execute that command, the problem is that the command is executed
> using sudo (*sudo* -E -H -u <user> bash -c "...") so it will be executed
> as root user anyways as i show you in ps aux results.
> Regards.
>
> 2018-05-10 14:48 GMT-05:00 Sam Nicholson <sam...@ogt11.com>:
>
>> Well, I don't recommend running as root.
>> That's why I went to the trouble to set up zeppelin as a sudoer.
>>
>> If you don't make this adjustment, yes, you have to run as root,
>> or you have to do the ssh key method.
>>
>> It's always the case that something has to run with elevated
>> privilege to allow userID changes at runtime.
>>
>> With JEE, the best that can be done, today, is to isolate executable
>> userIDs
>> from the main process user ID.
>>
>> In general, exposing shells to the web is problematic vis-a-vis security.
>>
>> Cheers!
>> -sam
>>
>
>

Reply via email to