Bug 441822
Summary: | verbosity option of ecryptfs mount helper not recognized | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jan Tluka <jtluka> |
Component: | ecryptfs-utils | Assignee: | Karsten Hopp <karsten> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | mhalcrow, mnowak, pknirsch, syeghiay |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 21:59:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jan Tluka
2008-04-10 13:14:23 UTC
Sounds like another doable fix. Proposing for RHEL-5.3 and granting Devel ACK. Read ya, Phil Proposing bug for RHEL-5.3 FasTrack. Read ya, Phil Case 1: verbose isn't the same as verbosity. verbosity takes an argument, verbose always switches verbose output on and verbose=0 is the same as verbose=1 or verboseXXXX verbosity=1 isn't parsed anywhere in the sources Case 2: Here are several bugs: - verbosity isn't removed from the list of options passed to systems mount command. This causes the 'unrecognized option' error. - verbosity=0 apparently does the same as no_sig_cache, this looks like a cut¬paste error in the sources. I still need to look why and where it turns of the prompts, though approved comp, clearing fast flag I think I need to clarify this: mount.ecryptfs has two distinct parameters 'verbose' and 'verbosity={0,1}' 'verbose' enables a very verbose logging in /var/log/messages and shouldn't be used in production environments unless you're debugging something. 'verbosity=0' uses default values for required parameters which aren't specified on the commandline, p.e. it doesn't ask for 'plaintext passthrough (y/n)' anymore with the commandline from comment #7 and just uses plaintext passthrough. 'verbosity=1' asks for every required parameter which hasn't been specified on the commandline. That's the same as not using the verbosity option at all. Older versions had a bug which passed the verbosity option to /sbin/mount instead of keeping it in /sbin/mount.ecryptfs. This resulted in a message "ecryptfs_parse_options: eCryptfs: unrecognized option 'verbosity=0'" in the syslog. This is fixed in our current package. Nonetheless there's a bug in the current package which misinterpretes 'verbosity=1' to be the same as 'verbose'. This needs to be fixed and I already have a patch for that. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0203.html |