linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adam T. Bowen" <adamb@agitate.org.uk>
To: linux-admin@vger.kernel.org
Subject: Re: automount thru winscp
Date: Fri, 09 Sep 2005 11:01:13 +0100	[thread overview]
Message-ID: <43215D69.7030604@agitate.org.uk> (raw)
In-Reply-To: <4320775D.20602@infinito.it>

Hi,

Luca Ferrari wrote:
> Hi,
> I've got a linux server with samba shares behind a firewall. Since my 
> users want to see their shares from the outside network, I thought to 
> dynamically mount shares on the firewall (using, for example, automount) 
>  providing access thru winscp, that has a quite windows like look & 
> feel. The problem is that I cannot understand when the user connects, 
> that means automount does not work with a winscp session, and that I 
> cannot mount shares thru the ~/.bash_profile script, since it is not 
> executed (maybe .profile is executed?). Any idea on how to solve the 
> problem?

Allowing external sFTP connections for normal users to your firewall box
is not a good idea with regard to security, but if that is what you
want.  As far as I know, your SHELL is used to execute the sftp-server
process once you have authenticated via the ssh daemon (using OpenSSH
which is all I have experience of).  So you just need to work out which
of the numerous shell initialization scripts is actually read.  On our
systems with SHELL as bash, the ~/.bashrc is read so you could put the
smbmount commands in there.

I just tried doing this myself and it works ok.  One thing I had to do
was export PASSWD=mypassword before the smbmount command.  Very
insecure, but perhaps you have your shares/authentication configured to
do it without this step.

Cheers

Adam


> Thanks,
> Luca



  reply	other threads:[~2005-09-09 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 17:39 automount thru winscp Luca Ferrari
2005-09-09 10:01 ` Adam T. Bowen [this message]
2005-09-09 10:30   ` Luca Ferrari
2005-09-09 12:01     ` Adam T. Bowen
2005-09-09 13:04 ` Stephen Samuel
2005-09-10  3:33   ` linux-user

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43215D69.7030604@agitate.org.uk \
    --to=adamb@agitate.org.uk \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).