MainInclusionReportEcryptfsUtils

Differences between revisions 1 and 20 (spanning 19 versions)
Revision 1 as of 2008-06-10 00:23:27
Size: 3146
Editor: cpe-66-68-158-133
Comment: initial creation, dupe of template
Revision 20 as of 2008-06-12 03:25:23
Size: 3646
Editor: cpe-66-68-158-133
Comment: added dependencies section
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

'''Note''': when writing a report this template should be vigorously edited; as a rule of thumb, every individual point should be replaced with a description of the actual situation in the package in question. The purpose of the report is to convey information to the reviewer, so there is no problem with varying the text in the bullet items, or with adding additional information.

Please be informative, and in particular be thorough in investigating and explaining any weaknesses and problems with the package. The purpose of the report is to show to the reviewer that the package has been properly investigated, and to give the reviewer the information from that investigation, for their decision.
Line 9: Line 5:
 0. ''Availability:'' [http://archive.ubuntu.com/ubuntu/pool/universe/s/sourcepackage]; available for all supported architectures or some subset ?  0. ''Availability:''    * [http://archive.ubuntu.com/ubuntu/pool/universe/e/ecryptfs-utils/]
  *
available for all supported architectures.
Line 11: Line 9:
  * Build dependency of ...
  *
  * encryptfs-utils is the key package for implementing a ~/Private/ encrypted directory as talked at UDS-Intrepid
  * EncryptedPrivateDirectory
  * [https://blueprints.edge.launchpad.net/ubuntu/+spec/encrypted-private-directories].
Line 14: Line 13:
  * [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=PRODUCT_NAME CVE entries]: ...
  * [http://secunia.com/search/?search=PRODUCT_NAME Secunia history]: ...
  * Any binaries runn
ing as root or suid/sgid ? Any daemons ?
  * N
etwork activity: does it open any port ? Does it handle incoming network data ?
  * Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ?
  * Any source code review performed ? (The approver will do a quick and shallow check.)
  * [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ecryptfs-utils CVE entries] - '''none'''
  * [http
://secunia.com/search/?search=ecryptfs-utils Secunia history] - '''none'''
  * Any binaries running as root or suid/sgid? - '''no''', but script makes sudo calls
  * Any daemons? - '''yes, /usr/bin/ecryptfsd'''
  * Network activity
: does it open any port? - '''no'''
  * Does it handle in
coming network data? - '''no'''
  * Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data? - '''no'''
  * Any source code review performed? (The approver will do a quick and shallow check.)
Line 23: Line 24:
  * [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 ?
  * [http:// Upstream] is frenetic/vigorous/calm/dead ?
  * [http:// Upstream bug tracker]: (mention any particularly relevant or critical)
  * Hardware: Does this package deal with hardware and if so how exotic is it ?
  * Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ?
  * [http://bugs.debian.org/src:ecryptfs-utils Debian bugs]: '''none'''
  * [http://packages.qa.debian.org/e/ecryptfs-utils.html Maintenance in Debian] is '''vigorous'''
  * [http://ecryptfs.sourceforge.net/ Upstream] is '''vigorous'''
  * [http://sourceforge.net/tracker/?group_id=133988&atid=728799 Upstream bug tracker]
   * [http://sourceforge.net/tracker/index.php?func=detail&aid=1639562&group_id=133988&atid=728799 ecryptfs over NFS kernel bug]
   * [http://sourceforge.net/tracker/index.php?func=detail&aid=1618254&group_id=133988&atid=728799 bind/chroots don't work right in ecryptfs]
  * Hardware: Does this package deal with hardware? - '''no'''
  * Is there a test suite in the upstream source or packaging? Is it enabled to run in the build? - '''yes - simple test.c in source, compiled but not run in debuild'''
Line 32: Line 35:
  * Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?   * Packaging system (debhelper/cdbs/dbs)? - '''debhelper'''
  *
Patch system? - '''dpatch'''
  *
Any packaging oddities? - '''no'''
Line 34: Line 39:
  * ...
  * Are these all in main ?
  * Runtime
   * libecryptfs0 (= ${binary:Version}), libgcrypt11-dev, libgpg-error-dev, libgpgme11-dev, libgtk2.0-dev, libkeyutils-dev, libopencryptoki-dev [i386], libpam0g-dev, libpkcs11-helper1-dev, libssl-dev, libtspi-dev [i386]
  * Build
   * debhelper (>= 7), dpatch, autotools-dev, autoconf, automake, libtool, libgcrypt11-dev, libgpg-error-dev, libgpgme11-dev, libgtk2.0-dev, libkeyutils-dev, libopencryptoki-dev [i386], libpam0g-dev, libpkcs11-helper1-dev, libssl-dev, libtspi-dev [i386]
  * Are these all in main? - '''no, see'''
   * MainInclusionReportPkcs11Helper
   * MainInclusionReportTrousers

Main Inclusion Report for ecryptfs-utils

Requirements

  1. Availability:

  2. Rationale:

  3. Security:

    • [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ecryptfs-utils CVE entries] - none

    • [http://secunia.com/search/?search=ecryptfs-utils Secunia history] - none

    • Any binaries running as root or suid/sgid? - no, but script makes sudo calls

    • Any daemons? - yes, /usr/bin/ecryptfsd

    • Network activity: does it open any port? - no

    • Does it handle incoming network data? - no

    • Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data? - no

    • Any source code review performed? (The approver will do a quick and shallow check.)
  4. Quality assurance:

  5. Standards compliance:

  6. Dependencies:

    • Runtime
      • libecryptfs0 (= ${binary:Version}), libgcrypt11-dev, libgpg-error-dev, libgpgme11-dev, libgtk2.0-dev, libkeyutils-dev, libopencryptoki-dev [i386], libpam0g-dev, libpkcs11-helper1-dev, libssl-dev, libtspi-dev [i386]
    • Build
      • debhelper (>= 7), dpatch, autotools-dev, autoconf, automake, libtool, libgcrypt11-dev, libgpg-error-dev, libgpgme11-dev, libgtk2.0-dev, libkeyutils-dev, libopencryptoki-dev [i386], libpam0g-dev, libpkcs11-helper1-dev, libssl-dev, libtspi-dev [i386]

    • Are these all in main? - no, see

  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://bugs.launchpad.net/BUGNUMBER]

The author of this report should put their name here; reviewers will add comments etc. too

MainInclusionReportEcryptfsUtils (last edited 2008-08-06 16:17:11 by localhost)