too verbose syslogging (when autounmount disabled)

Bug #1468435 reported by PoMo
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ecryptfs-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I opted to not have my home unmounted on log off (by deleting ~/.ecryptfs/auto-umount).

Since then, my syslog has the following entry every 15 minutes:
CRON[24481]: pam_ecryptfs: Skipping automatic eCryptfs unmount

(I notice it always follows one of my cronjobs that runs every 15 minutes. disabling that confirms it's what triggers it)

Now this may not be a bug, but when I search the web for that string, I find this in pam_ecryptfs.c:

/* User does not want to auto-mount */
syslog(LOG_DEBUG, "pam_ecryptfs: Skipping automatic eCryptfs mount");

The fact that it says LOG_DEBUG is what makes me wonder if I'm meant to see this on a regular install.

I'm also wondering if this is related to the verbose option of ecryptfs, which states:
verbose
              Log ecryptfs information to /var/log/messages. Do not run
              eCryptfs in verbose-mode unless you are doing so for the sole
              purpose of development, since secret values will be written out
              to the system log in that case.

If related, that could mean a default install writes secret values to the system log.

Note:
If this is not a bug (works as intended), I'd be interested to know how to get rid of this message,because it's flooding my logwatch emails.

$ lsb_release -rd
Description: Ubuntu 14.04.2 LTS
Release: 14.04

$ apt-cache policy ecryptfs-utils
ecryptfs-utils:
  Installed: 104-0ubuntu1.14.04.3
  Candidate: 104-0ubuntu1.14.04.3
[..]

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ecryptfs-utils (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.