Open GoogleCodeExporter opened 8 years ago
> I also tried "~" as my path, but no bones.
Eric, please: when you specify
~
then attempt to connect,
what messages are presented in MacFusion Log window?
Original comment by grahampe...@gmail.com
on 6 Jun 2007 at 9:41
Eric, please:
a) restart your computer
b) use an alternative SFTP client
c) make a successful connection to the server
d) take a hand written note of the path to the required directory
e) quit from that SFTP client
f) use MacFusion to attempt an SSH connection to the same server,
specify the same path -- it may be something different from
/home/username
What messages are presented in MacFusion Log window?
Original comment by grahampe...@gmail.com
on 6 Jun 2007 at 9:42
Apologies for taking your time. I was using MacFusion 1.0. Updating to 1.1
allows me
to connect to /home/username.
Connecting to "~" doesn't work but I'm not sure that it should. Here is the log
output:
---- MacFusion Started 2007-06-06 19:26:19 -0700
MacFusion Core: Loaded FTPFS filesystem from org.mgorbach.MacFusion.FTPFS
MacFusion Core: Loaded SSHFS filesystem from org.mgorbach.MacFusion.SSHFS
dreamhost: username@www.domain.com:~: No such file or directory
dreamhost: Mount Failed
It's working for me, now, though, so I have no complaints. Thank you very much
for
putting this piece of software out there.
Cheers,
Eric
Original comment by ericngu...@gmail.com
on 7 Jun 2007 at 2:29
> Apologies for taking your time.
No problem.
> Connecting to "~" doesn't work but I'm not sure that it should.
Agreed. The subject line of this MacFusion issue 175 is revised accordingly.
I see the same symptoms, or remarkably similar, with one server to which I have
access.
See for example MacFUSE issue_157
<http://code.google.com/p/macfuse/issues/detail?id=157#c7> but with this
particular server, there may be
other issues unrelated to MacFUSE, SSHFS or MacFusion -- so in general I'm
refraining from reporting issues
relating to this server until the bigger picture is clear.
For reference,
<http://pastie.textmate.org/68570>
<http://paste.lisp.org/display/42390>
<http://phpfi.com/240024>
<http://rafb.net/p/iP2oeY87.html>
(Four different views of the same paste, I was experimenting with paste sites.)
Original comment by grahampe...@gmail.com
on 7 Jun 2007 at 12:18
Eric, please:
If you make a verbose command line ssh connection to your server,
does it reveal any information that may be relevant?
In my case:
1) for the server that _does_ appear to work perfectly with
MacFUSE/SSHFS/MacFusion,
ssh gjp22@unix.central.sussex.ac.uk -v
reveals the version of OpenSSH that is running on the server
(I shan't disclose the versions here)
2) for the server that does _not_ lend itself to
MacFUSE/SSHFS/MacFusion,
ssh gjp22@ndrive.uscs.susx.ac.uk -v
reveals a different version of OpenSSH and
> Only users with supervisor rights to this server can access console screens.
Original comment by grahampe...@gmail.com
on 7 Jun 2007 at 12:52
I ran:
ssh gjp22@unix.central.sussex.ac.uk -v
and repeated the command for my server.
Both seem to have identical versions of OpenSSH and OpenSSL:
OpenSSH_4.5p1, OpenSSL 0.9.7l 28 Sep 2006
However, I also ran your second command, which you indicated had a different
version
of OpenSSH:
ssh gjp22@ndrive.uscs.susx.ac.uk -v
but it returns the same versions. I may be misunderstanding your question.
~e
Original comment by ericngu...@gmail.com
on 7 Jun 2007 at 5:46
in lieu of
gjp22
and
ndrive.uscs.susx.ac.uk or unix.central.sussex.ac.uk
you should enter
your own username
and the address of
your own ssh server.
The -v (verbose) option will cause the versions of your SSH client and SSH
server to be displayed during the
login routine.
> OpenSSH_4.5p1, OpenSSL 0.9.7l 28 Sep 2006
differs from my client and my servers, so the line you focused on was probably
the version of your client.
You should see something like,
> ...
> debug1: Remote protocol version 1.99, remote software version OpenSSH_4.3
> debug1: match: OpenSSH blah blah blah
> debug1: Enabling compatibility mode for protocol 2.0
> ...
and it's the "OpenSSH blah blah blah" line that may be of interest to us.
Regards
Graham
Original comment by grahampe...@gmail.com
on 8 Jun 2007 at 2:49
Eric, please:
1. quit from MacFusion
2. install version 0.4.0 of MacFUSE
3. follow the instructions at <http://paste.lisp.org/display/42412>
to create a symbolic link to the new location of MacFUSE
4. launch MacFusion
5. edit the affected SSHFS favourite, specify just one advanced option:
-odefer_auth
6. mount the volume, review permissions.
Let us know how you get on.
I, too, had a root connection to an SSH server that was not yielding proper
permissions.
Re <http://code.google.com/p/macfuse/wiki/CHANGELOG> the defer_auth option
resolved the issue for me.
Original comment by grahampe...@gmail.com
on 17 Jun 2007 at 11:10
Original issue reported on code.google.com by
grahampe...@gmail.com
on 6 Jun 2007 at 9:36