Main Inclusion Report for sshfs-fuse

Requirements

1. Availability: [http://archive.ubuntu.com/ubuntu/pool/universe/s/sshfs-fuse]; is available for all supported architectures

2. Rationale:

   • With the support for local applications on thin clients in LTSP a way was needed to make the ltsp login manager (LDM) mount the homedir of the logged in user on the client. Since LDM uses ssh to connect to the server and already puts an ssh communication socket in place, the natural choice was to re-use this socket to establish an sshfs mount. To provide the localapps functionality out of the box as planned the ltsp-client package will have to depend on sshfs which means sshfs-fuse has to move to main and onto the Ubuntu alternate CD.

3. Security:

   • No [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=sshfs-fuse CVE entries]

   • No [http://secunia.com/search/?search=sshfs-fuse Secunia history]

   • No binaries are running as root or suid/sgid, sshfs wraps around the fuse filesystem and sftp.
   • Network activity: sshfs establishes a fuse network mount on top of a ssh connection. It is a client application, does not run any daemons and operates on the ssh standard ports.
   • Sshfs does not process binary (video, audio, etc) or structured (PDF, etc) data ?
   • Any source code review performed ? (The approver will do a quick and shallow check.)

4. Quality assurance:

   • In Ubuntu the package will always work out of the box without configuration.
   • The package does not ask any debconf questions.

   • [http://bugs.debian.org/src:sshfs-fuse Debian bugs]: one tagged "important" on powerpc that is rather fuse related, 8 outstanding bugs

   • [http://packages.qa.debian.org/s/sshfs-fuse.html Maintenance in Debian] is moderate.

   • [http://fuse.sourceforge.net/sshfs.html] is calm.

   • [http:// Upstream bug tracker]: (mention any particularly relevant or critical)

   • Hardware: The package doe not deal with any specific hardware.
   • Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ?

5. Standards compliance:

   • [http://www.pathname.com/fhs/ FHS], [http://www.de.debian.org/doc/debian-policy/ Debian Policy] compliance ?

   • [http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html Debian library packaging guide] standards compliance ?

   • Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?

6. Dependencies:

   • ...
   • Are these all in main ?

7. Background information:

   • The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain.
   • What do upstream call this software ? Has it had different names in the past ?

Reviewers

MIR bug: [https://launchpad.net/bugs/BUGNUMBER]

Author: OliverGrawert