All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Weber <marco-oweber@gmx.de>
To: autofs <autofs@linux.kernel.org>
Subject: sshfs and autofs
Date: Fri, 18 Dec 2009 05:08:29 +0100	[thread overview]
Message-ID: <1261107485-sup-320@nixos> (raw)

If you google for sshfs and autofs you'll find many howtos telling you
to create a private key without passwords because this works.
Most of of those Howtos tell you as well that you should not be doing
this for security reasons..

I've found another solution:
It tries connecting to each running ssh-agent. The first being able to
connect to the ssh location will be used. This way you can keep using
passwords and still use autofs.

  #!/bin/sh -e
  # PATH must contains openssh, sed, sshfs lsof and pgrep
  pids=`pgrep ssh-agent`
  if [ -z "$pids" ]; then
    # no ssh-agent found. Maybe there is a key without password ? You should not be using this!
    sshfs -o ssh_command="ssh -o NumberOfPasswordPrompts=0" "$@"
  else
  for p in $pids; do
    export SSH_AGENT_PID=$p
    export SSH_AUTH_SOCK=$(lsof -p $p -a -U  -Fn | sed -n 's/^n//p')
    echo "trying to connect using ssh-agent $p $SSH_AUTH_SOCK" 1>&2
      sshfs -o ssh_command="ssh -o NumberOfPasswordPrompts=0" "$@" && exit 0 || true
  done
  exit 1
  fi

Of course it is just a dirty script. However it does a much better job
than using no password.

Do you host such examples somewhere as well?

Marc Weber

             reply	other threads:[~2009-12-18  4:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  4:08 Marc Weber [this message]
2009-12-18 22:01 ` sshfs and autofs Marc Weber
2009-12-20 15:54   ` Stef Bon
2009-12-21 10:32     ` Marc Weber
2009-12-22 19:08       ` Stef Bon
2009-12-22 21:45         ` Marc Weber
2009-12-23 21:47           ` Stef Bon
2009-12-23 21:59             ` Stef Bon
2009-12-23 22:16               ` Marc Weber
2009-12-23 22:31                 ` Stef Bon
2009-12-23 22:53                   ` Marc Weber
2009-12-24 14:12                     ` Stef Bon
2009-12-24 23:52                       ` Marc Weber
2009-12-23 22:05             ` Marc Weber
2009-12-23 22:19               ` Stef Bon

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=1261107485-sup-320@nixos \
    --to=marco-oweber@gmx.de \
    --cc=autofs@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.