Main Inclusion Report for ecryptfs-utils

Requirements

1. Availability:

   • [http://archive.ubuntu.com/ubuntu/pool/universe/e/ecryptfs-utils/]

   • available for all supported architectures.

2. Rationale:

   • 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].

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:

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

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)? - debhelper

   • Patch system? - dpatch

   • Any packaging oddities? - no

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

     • MainInclusionReportPkcs11Helper

     • MainInclusionReportTrousers

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