In message <_A3495@delegate-en.ML_> on 09/15/06(18:27:33)
you "Gsandtner Michael" <firstname.lastname@example.org> wrote:
|> |Moreover, is it possible to use public key authentication ?
|> Yes. If you can do it with the sftp command directly invoked on your
|> terminal, it is also available when the sftp command is
|> indirectly invoked
|> on a pty (pseudo terminal) via DeleGate.
|Something must be different.
|When I call sftp interactively the connection succeeds with public-key
|Within delegate, called from exactly the terminal where sftp is
|successful, there seems still password authentication to be used:
|Could not create directory '/.ssh'.^M
|sftp called from delegate seems to look in /.ssh for user configuration
|files, e.g. known_hosts. But the correct location is /root/.ssh .
|So it seems not to recognize the /root/.ssh/config containing the
|IdentityFile directive, resulting in password instead of public-key
|09/15 11:04:03.38  0+0: OWNER=nobody => OWNER=nobody/nobody(nobody/nobody)
You invoked your DeleGate under the ownership of "nobody" thus the sftp
is also invoked as of nobody.
The simplest way to escape the problem is specfying OWNER=root, though I
don't recommend it.
You shold use another real user as the owner of your DeleGate. Creating
a user like "delegate" just to run DeleGate is recommended.
9 9 Yutaka Sato <email@example.com> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller