MainInclusionReportSshFs

Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2008-08-04 10:53:08
Size: 3011
Editor: p5098ed03
Comment: initial submission
Revision 6 as of 2008-08-04 11:36:36
Size: 2887
Editor: p5098ed03
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Main Inclusion Report for sshfs = = Main Inclusion Report for sshfs-fuse =
Line 5: Line 5:
 0. ''Availability:'' [http://archive.ubuntu.com/ubuntu/pool/universe/s/sshfs]; is available for all supported architectures ?  0. ''Availability:'' [http://archive.ubuntu.com/ubuntu/pool/universe/s/sshfs-fuse]; is available for all supported architectures
Line 7: Line 7:
  * 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 has to move to main and onto the Ubuntu alternate CD.
  *
  * 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.
Line 10: Line 10:
  * [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=sshfs CVE entries]: ...
  * [http://secunia.com/search/?search=sshfs Secunia history]: ...
  * No [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=sshfs-fuse CVE entries]
  * No [http://secunia.com/search/?search=sshfs-fuse Secunia history]
Line 17: Line 17:
  * In what situations does the package not work out of the box without configuration ?
  * Does the package ask any debconf questions higher than priority 'medium' ?
  * [http://bugs.debian.org/src:SOURCE_PACKAGE_NAME Debian bugs]: (mention any that are particularly relevant, and any showstoppers)
  * [http://packages.qa.debian.org/S/SOURCE_PACKAGE_NAME.html Maintenance in Debian] is frenetic/vigorous/calm/dead ?
  * 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.
Line 23: Line 23:
  * Hardware: Does this package deal with hardware and if so how exotic is it ?   * Hardware: The package doe not deal with any specific hardware.
Line 40: Line 40:
''The author of this report should put their name here; reviewers will add comments etc. too'' ''Author: OliverGrawert''

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:// Upstream] is frenetic/vigorous/calm/dead ?

    • [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:

  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

MainInclusionReportSshFs (last edited 2008-08-06 16:27:08 by localhost)