SSHFS: Difference between revisions
No edit summary |
|||
Line 44: | Line 44: | ||
* [[Files transferred over shell protocol]] (FISH) |
* [[Files transferred over shell protocol]] (FISH) |
||
* [[FTPFS]] |
* [[FTPFS]] |
||
* [[ExpanDrive]] |
|||
* [[WebDrive]] |
|||
== External links == |
== External links == |
Revision as of 12:52, 31 October 2011
This article needs additional citations for verification. (June 2009) |
Developer(s) | Miklos Szeredi |
---|---|
Stable release | 2.2
/ 20 October 2008 |
Repository | |
Operating system | UNIX-like |
Type | Remote access |
Website | http://fuse.sourceforge.net/sshfs.html |
In computing, SSHFS (SSH Filesystem) is a filesystem client to mount and interact with directories and files located on a remote server or workstation.[1] The client interacts with the remote file system via the SSH File Transfer Protocol (SFTP),[2] a network protocol providing file access, file transfer, and file management functionality over any reliable data stream that was designed as an extension of the Secure Shell protocol (SSH) version 2.0.
The current implementation of SSHFS using FUSE is a rewrite of an earlier version. The rewrite was done by Miklos Szeredi, who also wrote FUSE.[3]
Features
SFTP provides secure file transfer and a secure remote file system. Whilst SFTP clients may transfer files and directories, the related file system may not be mounted locally using SFTP alone. Using SSHFS, a locally-mounted file system may be treated in the same way as other volumes (such as CDs, DVDs, USB flash drives and shared disks).[citation needed]
If the remote environment matches the requirements of the local application, then the end user may work with remote files and directories as if they are on a local volume. If the remote environment is a less than perfect match — if the server cannot respond appropriately — then applications may respond in ways that are unpredictable or misleading.[citation needed]
Using ls with sshfs will sometimes not list the owner of a file correctly, although it is possible to map them manually.[4][5]
For greater security the system can be configured by the service administrator to run inside a chroot jail or in a FreeBSD jail, allowing the client to only see part of the file system.[citation needed]
For distributed remote file systems with multiple users, protocols such as Apple Filing Protocol, Network File System and Server Message Block are more often used. SSHFS is an alternative to those protocols only in situations where users are confident that files and directories will not be targeted for writing by another user, at the same time.[citation needed]
The advantage of SSHFS when compared to other network file system protocols is that, given that a user already has SSH access to a host, it does not require any additional configuration work, or the opening of additional entry ports in a firewall.[citation needed]
References
- ^ "SSHFS manpage". undated. Retrieved 2010-02-26.
{{cite web}}
: Check date values in:|year=
(help)CS1 maint: year (link) - ^ "SSHFS security". Retrieved 26 February 2010.
- ^ "SSHFS homepage". Retrieved 5 June 2009.
- ^ Canonical Ltd. (2009). "SSHFS - Community Ubuntu Documentation". Retrieved 5 June 2009.
{{cite web}}
: Unknown parameter|month=
ignored (help) - ^ Szeredi, Miklos (2008). "SSHFS FAQ: What options does sshfs support?". Retrieved 5 June 2009.
{{cite web}}
: Unknown parameter|month=
ignored (help)
See also
- Gvfs
- SSH file transfer protocol (SFTP)
- Secure copy (SCP)
- FileZilla, a Free Software utility for multiple platforms.
- Files transferred over shell protocol (FISH)
- FTPFS
- ExpanDrive
- WebDrive
External links
- SSH Filesystem - official webpage.
- SSH File Transfer Protocol
- URI Scheme for SSH and SFTP
- Google Releases FUSE for Mac OS X: MacFUSE
- Macfusion: a GUI for MacFUSE
- Dokan SSHFS for Windows
- SSH(SFTP) filesystem for Windows
- NTFS-3G: Extended Attributes (highlights)
- sshfs for MAC OS X