Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Encrypting history?
- X-seq: zsh-users 14694
- From: Guido van Steen <gvsteen@xxxxxxxxx>
- To: Lloyd Zusman <ljz@xxxxxxxxxx>
- Subject: Re: Encrypting history?
- Date: Mon, 28 Dec 2009 15:00:55 -0800 (PST)
- Cc: zsh-users@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1262041255; bh=+ukpZ+oMqdaw0msslahID97+WsczLo4dJCGvF4C6jOk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=lj0uk1OluUnxRbnJo2OPKx423eb09woREvhErkI3v6W2uTaRrsbS87Drztg3oscKOwrt/LDj7nTn8F3pt2vekqHS7ySAFzhE/YLMEcf31wV3vdOQXaBNJuQ9T+NuQVkzRBhljX5moMD5D95VOEXPVvukfa5FT8Tj+Dkjxmc9Vr0=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1BKr1jl5AAgR2wPgWxnMz+6KKNnjlNi//BqXqdeToHHkL9ufxDsJZ7g/x5dLjJoyqaFUm87LNlK6yU53WPuwGxk5FiOxvWNJd7pUbv9PhYld6LHuSL0gatU2vV0WRkOrNtpyVwMgupRpwn0SY3hc8oS5NghfE2g/UgbmMDWgr8E=;
- In-reply-to: <m2y6ko6ya5.fsf@xxxxxxxxxx>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
Hi Lloyd,
With respect to the list of commands issued during
the current session, could you not use "fc -l" to detect the current history line at login?
Guido
--- On Mon, 28/12/09, Lloyd Zusman <ljz@xxxxxxxxxxx> wrote:
> From: Lloyd Zusman <ljz@xxxxxxxxxx>
> Subject: Re: Encrypting history?
> To: zsh-users@xxxxxxx
> Date: Monday, 28 December, 2009, 1:56 AM
> Guido van Steen <gvsteen@xxxxxxxxx>
> writes:
>
> > Hi Lloyd,
> >
> > Interesting idea indeed! You might miss a feature like
> sharing a history file across sessions.
> >
> > You could overcome this by seperately saving all your
> sessions' increments to your history file, and then
> incorporating them into the history file when you login
> again.
> >
> > This way the entries of your history file might get
> out of order, but you could probably handle this by also
> saving the time when your commands were issued.
> >
> > I would also be interested in a zsh extension like
> that.
> >
> > Best wishes,
> >
> > Guido
>
> Thank you for reminding me about sharing history across
> sessions.
>
> I've never written an extension for zsh, and so the first
> thing I plan
> to do is implement this via code in my .zlogin and .zlogout
> files. Then,
> once I get it working, I'll take the plunge and try to turn
> it into an
> extension.
>
> Concerning this session-specific history issue, is there a
> way to get a
> history list of the commands that were issued only during
> the current
> session? If so, I think I probably could do something like
> this upon
> logout:
>
> * Lock the current history file
> * Get the history list for the current session
> * Encrypt this history list and append it to the current
> history file
> * Unlock the current history file
>
> Would that work?
>
>
>
> > --- On Sun, 27/12/09, Lloyd Zusman <ljz@xxxxxxxxxx>
> wrote:
> >
> >> From: Lloyd Zusman <ljz@xxxxxxxxxx>
> >> Subject: Encrypting history?
> >> To: zsh-users@xxxxxxx
> >> Date: Sunday, 27 December, 2009, 5:55 AM
> >> I would like my command history to be
> >> stored in an encrypted file. I
> >> have read a few messages in this list from 2007
> which state
> >> that there
> >> isn't a straightforward way to do this within zsh,
> itself,
> >> and the use
> >> of an encrypted file system is suggested.
> >>
> >> However, I think that there might indeed be a way
> to
> >> accomplish this.
> >>
> >> Is it possible to do the following?
> >>
> >> Make sure that SAVEHIST is set to 0.
> >>
> >> Then, on login, prompt the user for a password.
> Remember
> >> this password
> >> for the duration of the shell session. Then, use
> this
> >> password along
> >> with a decryption program to read an encrypted
> history file
> >> called, for
> >> example, ~/.ehistory. Put the decrypted contents
> of this
> >> file into the
> >> current shell's history list via the repeated use
> of the
> >> "print -s"
> >> command.
> >>
> >> Finally, on logout, pipe the output of "fc -ln 1"
> through a
> >> program
> >> which uses the same password entered at login time
> to
> >> encrypt the
> >> history and write it to the ~/.ehistory file.
> >>
> >> Can any of you see any reason for why this would
> not work?
> >>
> >> Or alternatively, is there perhaps a better way to
> do this
> >> within zsh?
> >>
> >> Thanks in advance.
> >>
> >>
> >> --
> >> Lloyd Zusman
> >> ljz@xxxxxxxxxx
> >> God bless you.
> >>
> >>
> >
> >
> > Get your new Email
> address!
> > Grab the Email name you've always wanted before
> someone else does!
> > http://mail.promotions.yahoo.com/newdomains/aa/
> >
> >
>
> --
> Lloyd Zusman
> ljz@xxxxxxxxxx
> God bless you.
>
>
Get your preferred Email name!
Now you can @ymail.com and @rocketmail.com.
http://mail.promotions.yahoo.com/newdomains/aa/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author