Re: Encrypted bashrc?

[Clark J. Wang]

On Fri, Nov 11, 2011 at 9:09 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> > > On Fri, Nov 11, 2011 at 01:48:59PM +0800, Clark J. Wang wrote:
> > > > In my company all the people share a few of Solaris servers which use
> > > > NIS to manage user accounts. The bad thing is that some servers' root
> > > > passwords are well known so anybody can easily su to my account to
> > > > access my files.  To protect some private info in my bashrc I want to
> > > > encrypt it. Any one has a good solution for that?
>
> The private information should be in a separate file, not in ~/.bashrc
> itself.
>

Sounds like this is the correct way to go.


> > I've ever tried openssl and it worked fine overall. The big problem is
> that
> > every time I log in or create a new shell window in screen I have to
> enter
> > my key to decrypt the rc file. I usually open 10 shell windows in screen
> so
> > it's really annoying. More elegant solution?
>
> This is pretty off-topic for bug-bash, since it's not about bash or about
> a bug.  It would REALLY help to know what you are doing, without all the
> vagueness and obfuscation.
>

I'm talking about my bashrc so I think it's bash related. :)


> You could write something that works like ssh-agent and ssh-add.  Run the
> agent at login time and run the adder when you have interactive capability,
> so that the agent can be given your passphrase to unlock the private file.
>
> Maybe you actually ARE talking about an ssh key.  God only knows, since
> you couldn't be bothered to tell us.
>
> In any case, it's not a bash bug.
>

I did not tell it's a bash bug. Just want to know if any one has done
similar things and how.