From: Tyler Hicks <tyhicks@canonical.com>
To: Jaroslav Fojtik <jafojtik@seznam.cz>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Please patch key_mod.c
Date: Tue, 27 May 2014 11:06:09 +0200 [thread overview]
Message-ID: <20140527090609.GA26330@boyd> (raw)
In-Reply-To: <536E62DD.8156.E36EA@jafojtik.seznam.cz>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
Sorry for missing this patch, I've been traveling.
On 2014-05-10 19:33:17, Jaroslav Fojtik wrote:
> Dears,
>
> Please patch key_mod.c.
This change looks good to me. I've pushed it to lp:ecryptfs. Thanks!
Tyler
>
> If you receive following message, it is totally frustrating because you do not know which
> directory attempted to open. The path at least gives some info about it.
>
> ======================================================================================
>
> mount.ecryptfs /DATA/.BACKUP /DATA/BACKUP -o
> key=passphrase,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_passthrough=no,ecryptfs_
> enable_filename_crypto=yes,ecryptfs_fnek_sig=87f8f52c6f46cfca
> Error attempting to evaluate mount options: [-1] Operation not permitted
> Check your system logs for details on why this happened.
> Try updating your ecryptfs-utils package, and/or
> submit a bug report on https://bugs.launchpad.net/ecryptfs
>
> 2 keys in keyring:
> 620524981: --alswrv 0 0 user: 87f8f52C6f46cfcA
> 1017206571: --alswrv 0 0 user: 87f8f52c6f46cfca
>
> Mar 30 18:40:39 ESC_router mount.ecryptfs: ERROR: Could not open key_mod directory
> Mar 30 18:40:39 ESC_router mount.ecryptfs: Error attempting to get key module list; rc =
> [-1]
>
>
> best regards
> Jara
>
> ---------------------------------------------------
>
> *** key_mod.c.old Sat May 10 17:57:51 2014
> --- key_mod.c Sat May 10 17:58:31 2014
> ***************
> *** 252,258 ****
> }
> if (!(dp = opendir(dir_name))) {
> syslog(LOG_WARNING,
> ! "ERROR: Could not open key_mod directory\n");
> rc = -EPERM;
> goto out;
> }
> --- 252,258 ----
> }
> if (!(dp = opendir(dir_name))) {
> syslog(LOG_WARNING,
> ! "ERROR: Could not open key_mod directory [%s]\n", dir_name);
> rc = -EPERM;
> goto out;
> }
>
>
>
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-05-27 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 17:33 Please patch key_mod.c Jaroslav Fojtik
2014-05-27 9:06 ` Tyler Hicks [this message]
[not found] ` <53970CB4.5050004@cmos.net>
[not found] ` <5397116B.2040502@cmos.net>
[not found] ` <539711F6.4040804@cmos.net>
2014-06-10 14:13 ` kernel crash after enable ecryptfs under abnormal power off Hanks Wang
2014-06-12 19:21 ` Tyler Hicks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140527090609.GA26330@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=jafojtik@seznam.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).