mount_smbfs and non-interactively passing a password to it

[Zane C.B.]

On Mon, 21 May 2007 02:39:17 +0900
Hiroharu Tamaru <tamaru at myn.rcast.u-tokyo.ac.jp> wrote:

> At Sun, 20 May 2007 13:10:42 -0400, Zane C.B. wrote:
> > 
> > On Mon, 21 May 2007 01:58:58 +0900
> > Hiroharu Tamaru <tamaru at myn.rcast.u-tokyo.ac.jp> wrote:
> > 
> > > At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote:
> > > > 
> > > > On Mon, 21 May 2007 01:19:58 +0900
> > > > Hiroharu Tamaru <tamaru at myn.rcast.u-tokyo.ac.jp> wrote:
> > > > 
> > > > > 
> > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote:
> > > > > > Is passing a password to mount_smbfs non-interactively
> > > > > > possible? I know it can't accept it on STDIN by piping it
> > > > > > into it.
> > > > > 
> > > > > mount_smbfs(8) :
> > > > >      -N      Do not ask for a password.  At run time,
> > > > > mount_smbfs reads the ~/.nsmbrc file for additional
> > > > > configuration parameters and a password.  If no password is
> > > > > found, mount_smbfs prompts for it.
> > > > > 
> > > > > /usr/share/examples/smbfs/dot.nsmbrc :
> > > > > [FSERVER:JOE]
> > > > > # use persistent password cache for user 'joe'
> > > > > password=$$1767877DF
> > > > > 
> > > > > I'm using -N for shares w/o passwords; I've never
> > > > > tried .nsmbrc password myself
> > > > 
> > > > This is not useful if ~/ is not mounted and you are planning
> > > > of mounting it using mount_smbfs.
> > > 
> > > You never said that.
> > > Who's mounting ~user in that case? root?
> > 
> > Yeah, looking at doing it through PAM.
> 
> OK. finally, I see your picture and why you said ENV;
> 
> For a hack:
> With the root creds in effect, /root/.nsmbrc is consulted
> and /etc/nsmb.conf is always consulted (as written in that file).
> Write the password in either of it, mount, and wipe it out.

Not useful since that would require passwords being in that file.

> Other than that, I've no idea.
> You'd need to wipe out the environment vars if you use it too.

Decided against that since D.E.S. pointed out that it would be
exposed in /proc.