can't write zsh_history

can't write zsh_history

[Michael Hernandez]

Hi all,

Every now and then I need to su on some servers that I work on  
(mostly old freebsd systems that don't have sudo installed and have  
no outbound net connections, i.e. installing sudo is not an option).  
The problem, which is really more of an annoyance than a problem, is  
that if I su to run some command and I don't cd first,  
my .zsh_history file becomes owned by root. After I exit from # and  
run a command as my regular user, zsh tells me that it can't write  
the history file, which of course it can't because it's now owned by  
root. Is there something I can do to alter the way zsh writes to my  
history file when I am root? Something like "if uid is 0 then write  
the history to root's history file and leave .zsh_history alone"?  It  
should be noted that on these machines root's shell is tcsh, except  
in one case where it's ksh (not my idea I promise!) so I'm not sure  
why .zsh_history is touched at all when I'm root. Another oddity is  
that if I chown the file to my user, the file becomes corrupt, which  
is even more frustrating. The version of zsh for each of these  
machines is 4.2.6.

As I said, this is a minor annoyance, but I figured I'd ask in case  
someone else has experienced this before and has a remedy.

Thanks!

Mike H


PS. I just tested this on an openbsd 3.9 firewall that I have, with  
zsh version 4.2.6, and where root's shell is ksh. Same thing happens.

Re: can't write zsh_history

[Peter Stephenson]

Michael Hernandez wrote:
> The problem, which is really more of an annoyance than a problem, is  
> that if I su to run some command and I don't cd first,  
> my .zsh_history file becomes owned by root. After I exit from # and  
> run a command as my regular user, zsh tells me that it can't write  
> the history file, which of course it can't because it's now owned by  
> root. Is there something I can do to alter the way zsh writes to my  
> history file when I am root?

if (( ! EUID )); then
  HISTFILE=~/.history_root
else
  HISTFILE=~/.history
fi

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

Re: can't write zsh_history

[William Scott]

>> root. Is there something I can do to alter the way zsh writes to my
>> history file when I am root?
>
> if (( ! EUID )); then
>  HISTFILE=~/.history_root
> else
>  HISTFILE=~/.history
> fi

You got my hopes up with this, but unfortunately I can't get this
to work, using my favorite security hole:

luser-%  sudo zsh
root-#   (various nefarious evildoing)
root-#   exit
zsh: can't write history file /Users/luser/.zsh_history

(I call it .zsh_history, BTW).

Even "sudo zsh -l" doesn't help.  $HISTFILE never changes.
I thought about having it update dynamically like $PWD,
but it seems like a lot of overhead for an occasional
irritation.  In addition, in my case at least the
ownership of ~/.zsh_history remains with luser.

Re: can't write zsh_history

[William Scott]

On Fri, 13 Oct 2006, William Scott wrote:

>>> root. Is there something I can do to alter the way zsh writes to my
>>> history file when I am root?
>> 
>> if (( ! EUID )); then
>>  HISTFILE=~/.history_root
>> else
>>  HISTFILE=~/.history
>> fi
>
> You got my hopes up with this, but unfortunately I can't get this
> to work, using my favorite security hole:
>
> luser-%  sudo zsh
> root-#   (various nefarious evildoing)
> root-#   exit
> zsh: can't write history file /Users/luser/.zsh_history
>
> (I call it .zsh_history, BTW).
>
> Even "sudo zsh -l" doesn't help.  $HISTFILE never changes.
> I thought about having it update dynamically like $PWD,
> but it seems like a lot of overhead for an occasional
> irritation.  In addition, in my case at least the
> ownership of ~/.zsh_history remains with luser.
>
>

I should never post before morning coffee.  sudo /bin/zsh -l
corrects the problem; I had a differently behaving zsh at
the head of the $PATH.

So a slightly different question:

is there a way to alias

"sudo zsh"  to "sudo /bin/zsh -l" ?

Re: can't write zsh_history

[Michael Hernandez]

On Oct 13, 2006, at 10:30 AM, William Scott wrote:

>
>
> On Fri, 13 Oct 2006, William Scott wrote:
>
>>>> root. Is there something I can do to alter the way zsh writes to my
>>>> history file when I am root?
>>> if (( ! EUID )); then
>>>  HISTFILE=~/.history_root
>>> else
>>>  HISTFILE=~/.history
>>> fi
>>
>> You got my hopes up with this, but unfortunately I can't get this
>> to work, using my favorite security hole:
>>
>> luser-%  sudo zsh
>> root-#   (various nefarious evildoing)
>> root-#   exit
>> zsh: can't write history file /Users/luser/.zsh_history
>>
>> (I call it .zsh_history, BTW).
>>
>> Even "sudo zsh -l" doesn't help.  $HISTFILE never changes.
>> I thought about having it update dynamically like $PWD,
>> but it seems like a lot of overhead for an occasional
>> irritation.  In addition, in my case at least the
>> ownership of ~/.zsh_history remains with luser.
>>
>>
>
> I should never post before morning coffee.  sudo /bin/zsh -l
> corrects the problem; I had a differently behaving zsh at
> the head of the $PATH.
>
> So a slightly different question:
>
> is there a way to alias
>
> "sudo zsh"  to "sudo /bin/zsh -l" ?
>
>

I'd like to mention that I decided to  "su -" and not just "su"f, and  
this way I can use root's startup files and not have to worry about  
my files being touched.  It works .... for now ;)

Mike

Re: can't write zsh_history

[Stanislaw Halik]

On Fri, Oct 13, 2006, William Scott wrote:
> luser-%  sudo zsh
> root-#   (various nefarious evildoing)
> root-#   exit
> zsh: can't write history file /Users/luser/.zsh_history

> (I call it .zsh_history, BTW).

> Even "sudo zsh -l" doesn't help.  $HISTFILE never changes.
> I thought about having it update dynamically like $PWD,
> but it seems like a lot of overhead for an occasional
> irritation.  In addition, in my case at least the
> ownership of ~/.zsh_history remains with luser.

If zsh is your root shell, `sudo -i' will do.

Re: can't write zsh_history

[Roman Neuhauser]

# wgscott@chemistry.ucsc.edu / 2006-10-13 07:30:52 -0700:
> is there a way to alias
> 
> "sudo zsh"  to "sudo /bin/zsh -l" ?

    sudo()
    {
      if [ $# -eq 1 -a "x$1" = "xzsh" ]; then
        command sudo /bin/zsh -l
      else
        command sudo "$@"
      fi
    }

-- 
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991

Re: can't write zsh_history

[Jeremy Hankins]

William Scott <wgscott@chemistry.ucsc.edu> writes:

>> if (( ! EUID )); then
>>  HISTFILE=~/.history_root
>> else
>>  HISTFILE=~/.history
>> fi
>
> You got my hopes up with this, but unfortunately I can't get this
> to work, using my favorite security hole:

Where'd you put it?  Without 'su -' or 'zsh -l' or whatever, it's not a
login shell, so dot-files are read appropriately.  Did you try zshrc?

-- 
Jeremy Hankins <nowan@nowan.org>
PGP fingerprint: 748F 4D16 538E 75D6 8333  9E10 D212 B5ED 37D0 0A03

Re: can't write zsh_history

[Phil Pennock]

On 2006-10-13 at 07:27 -0700, William Scott wrote:
> luser-%  sudo zsh
> root-#   (various nefarious evildoing)
> root-#   exit
> zsh: can't write history file /Users/luser/.zsh_history
> 
> (I call it .zsh_history, BTW).
> 
> Even "sudo zsh -l" doesn't help.  $HISTFILE never changes.

I strongly suspect that somewhere in your zsh startup files, you're
exporting HISTFILE to the environment.  The variable is used by tcsh
too, so tcsh will then be seeing the value and writing data in its own
format.  zsh later does sanity checks when writing its history, so
complains.

HISTFILE should be set, but not exported, being an internal control
variable.

In zsh:
% env | grep '^HISTFILE='

Regards,
-Phil

Re: can't write zsh_history

[William Scott]

>
> I strongly suspect that somewhere in your zsh startup files, you're
> exporting HISTFILE to the environment.  The variable is used by tcsh

Yes, it turns out I was (naively) exporting the variable.

I still need a function along the lines of what Roman Neuhauser suggested 
(although mine uses [[]] ).

Thanks.