From: "Toralf Förster" <toralf.foerster@gmx.de>
To: linux-ext4@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: ext4 encrypted dir becomes sickish after 4-5 days
Date: Wed, 14 Sep 2016 11:44:02 +0200 [thread overview]
Message-ID: <0951cedc-fff1-682c-daca-b9a1734e43e2@gmx.de> (raw)
I do run a hardened stable Gentoo Linux server w/ kernel 4.7.3-ahrdened-r1 where I use an ext4fs directory /var/lib/tor in the following way :
scp ~/.cryptoSalt user@host:/tmp
cat /tmp/.cryptoPass | ssh user@host 'sudo -u tor e4crypt add_key -S $(cat /tmp/.cryptoSalt) /var/lib/tor && sudo /etc/init.d/tor start; rm /tmp/.cryptoSalt'
Works fine after reboot.
But after 4 days or so a restart of the service "tor" fails with messages like :
Sep 14 11:27:10.000 [warn] Could not open "/var/lib/tor/data/keys/secret_id_key": Required key not available
Sep 14 11:27:10.000 [warn] Error reading private key from "/var/lib/tor/data/keys/secret_id_key"
Sep 14 11:27:10.000 [err] Error loading private key.
Sep 14 11:27:10.000 [err] Error initializing keys; exiting
Sep 14 11:27:10.000 [warn] Couldn't open "/var/lib/tor/data/state.tmp" (/var/lib/tor/data/state) for writing: Required key not available
Sep 14 11:27:10.000 [warn] Unable to write state to file "/var/lib/tor/data/state"; will try again later
No way to get it repaired other than rebooting the machine.
Any hints ?
--
Toralf
PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7
next reply other threads:[~2016-09-14 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 9:44 Toralf Förster [this message]
2016-09-14 12:49 ` ext4 encrypted dir becomes sickish after 4-5 days Theodore Ts'o
2016-09-14 17:24 ` Toralf Förster
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=0951cedc-fff1-682c-daca-b9a1734e43e2@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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