MainInclusionReportSshFs

Revision 11 as of 2008-08-04 13:38:50

Clear message

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
    • A sourcecode review was performed (the source actually consists only of three .c files), given that sshfs upstream is identical to fuse upstream no unexpected oddness was found.
  4. Quality assurance:

  5. Standards compliance:

  6. Dependencies:

    • fuse, libglib
    • All of these are in main (and on the CD already)
  7. Background information:

    • The general purpose and context of the package is clear and straightforward from the package description.
    • Upstream calls this software sshfs-fuse since the beginning.

Reviewers

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

Author: OliverGrawert