Yep. 0's didn't work, but null password did. Thanx.
Can you help me understand why this would be an expected, or even
acceptable behaviour? Or for that matter why the tools have the
'known password' options. Seems like setting the passwords to widely
known ones runs counter to the whole point
On Mon, 9 Jun 2008, Dietmar Lippold wrote:
-> I have tested ecryptfs on Fedora 9 and I don't understand, why the
-> files of a crypted diretory are readable when the directory is mounted
-> with a wrong passphrase.
-> [EMAIL PROTECTED]: 1
-> > Passphrase:
-> [EMAIL PROTECTED]: test
-> > Verify P
Hmm, ecryptfs_generate_tpm_key may rely on a known SRK password. Try
setting it to all zero's or a hash of zero bytes using tpm-tools and
try again...
Kent
On Tue, Jun 10, 2008 at 11:59 AM, Steve Ensley <[EMAIL PROTECTED]> wrote:
> trying to test tpm support on a new motherboard we are evaluatin
trying to test tpm support on a new motherboard we are evaluating.
I've been able to install trousers and test it by using tpm_sealdata
to encrypt a test file but after configuring ecryptfs with the
--enable-tspi option and making and installing it, when I try to
generate a key using ecrypt-generat
On Tue, Jun 10, 2008 at 10:27:04AM +0200, Dietmar Lippold wrote:
> Michael Halcrow wrote:
> > On Thu, Jun 05, 2008 at 12:45:55PM +0200, Dietmar Lippold wrote:
> > > Why is the file /tmp/test/Test readable although root gave the wrong
> > > passphrase?
> >
> > If you run ``keyctl show'', you will s
Michael Halcrow wrote:
> On Thu, Jun 05, 2008 at 12:45:55PM +0200, Dietmar Lippold wrote:
> > Why is the file /tmp/test/Test readable although root gave the wrong
> > passphrase?
>
> If you run ``keyctl show'', you will see that the key you used in the
> previous mount is still available in your k
