Ecryptfs

• Thread Index

• [PATCH] eCryptfs: Replace deactivated email address
  • From: Tyler Hicks <code@xxxxxxxxxxx>
• [PATCH] MAINTAINERS: eCryptfs: Update maintainer address and downgrade status
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: add mount option for specifying cipher driver.
  • From: Brian Kubisiak <brian.kubisiak@xxxxxxxxx>
• Debian package
  • From: René Schmidt <remasch@xxxxxx>
• Re: [PATCH] ecryptfs: replace BUG_ON with error handling code
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• [PATCH] ecryptfs: replace BUG_ON with error handling code
  • From: Aditya Pakki <pakki001@xxxxxxx>
• Re: [PATCH v4] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH v6] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Gao Xiang <hsiangkao@xxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Gao Xiang <gaoxiang25@xxxxxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v4] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v4] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v4] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH v4] fs: introduce is_dot_or_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
  • From: John Stoffel <john@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v2] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH v2] fs: introduce is_dot_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v2] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: Jean-Louis Biasini <jl.biasini@xxxxxxxxxxx>
• Re: [PATCH v2] fs: introduce is_dot_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH v2] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH] fs: introduce is_dot_dotdot helper for cleanup
  • From: Tiezhu Yang <yangtiezhu@xxxxxxxxxxx>
• Re: [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  • From: Jean-Louis Biasini <jl.biasini@xxxxxxxxxxx>
• Re: [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v14 1/5] Add flags option to get xattr method paired to __vfs_getxattr
  • From: Mark Salyzyn <salyzyn@xxxxxxxxxxx>
• Re: Decrypt/decode file names without mounting
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Decrypt/decode file names without mounting
  • From: Vinícius Ávila Eichenberg <vinieich@xxxxxxxxx>
• [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH][RFC] ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [RFC] lookup_one_len_unlocked() lousy calling conventions
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH][RFC] ecryptfs unlink/rmdir breakage (similar to caught in ecryptfs rename last year)
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 1/5] Add flags option to get xattr method paired to __vfs_getxattr
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] ecryptfs: fix a memory leak bug
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: fix a memory leak bug
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: fix a memory leak bug
  • From: Wenwen Wang <wenwen@xxxxxxxxxx>
• [PATCH] ecryptfs: fix a memory leak bug
  • From: Wenwen Wang <wenwen@xxxxxxxxxx>
• [PATCH v5 04/18] fs: compat_ioctl: move FITRIM emulation into file systems
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH v5 00/18] compat_ioctl.c removal, part 2/3
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [GIT PULL] eCryptfs fixes for 5.3-rc1
  • From: pr-tracker-bot@xxxxxxxxxx
• [GIT PULL] eCryptfs fixes for 5.3-rc1
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] fs: ecryptfs: crypto: Change return type of ecryptfs_process_flags
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] fs: ecryptfs: crypto: Change return type of ecryptfs_process_flags
  • From: Hariprasad Kelam <hariprasad.kelam@xxxxxxxxx>
• Re: [PATCH] ecryptfs: use print_hex_dump_bytes for hexdump
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH -next] ecryptfs: remove unnessesary null check in ecryptfs_keyring_auth_tok_for_sig
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH -next] ecryptfs: Make ecryptfs_xattr_handler static
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH -next] ecryptfs: Make ecryptfs_xattr_handler static
  • From: YueHaibing <yuehaibing@xxxxxxxxxx>
• [PATCH -next] ecryptfs: remove unnessesary null check in ecryptfs_keyring_auth_tok_for_sig
  • From: YueHaibing <yuehaibing@xxxxxxxxxx>
• Re: [PATCH 1/4] ecryptfs: remove unnessesary null check in ecryptfs_keyring_auth_tok_for_sig
  • From: YueHaibing <yuehaibing@xxxxxxxxxx>
• [PATCH 1/4] ecryptfs: remove unnessesary null check in ecryptfs_keyring_auth_tok_for_sig
  • From: YueHaibing <yuehaibing@xxxxxxxxxx>
• ecryptfs doesn't load with kernel > 5.0.8
  • From: daniel-mailinglists@xxxxxxxxxx
• [PATCH] ecryptfs: use print_hex_dump_bytes for hexdump
  • From: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>
• Re: [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
• Re: [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: James Bottomley <jejb@xxxxxxxxxxxxx>
• Re: [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 4/6] security/keys/ecryptfs: Drop direct dependency on key_type_encrypted
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 0/6] security/keys/encrypted: Break module dependency chain
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] eCryptfs: fix permission denied with ecryptfs_xattr mount option when create readonly file
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: re-order a condition for static checkers
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: re-order a condition for static checkers
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• combination of cifs and ecryptfs not working - readonly problems
  • From: Hans-Joachim Kliemeck <info@xxxxxxxxxxx>
• Re: combination of cifs and ecryptfs not working - readonly problems
  • From: Hans-Joachim Kliemeck <info@xxxxxxxxxxx>
• RE: combination of cifs and ecryptfs not working - readonly problems
  • From: "Alex Braunegg" <alex.braunegg@xxxxxxxxx>
• Re: How to avoid kern.log msg "Could not find key with description..."
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: combination of cifs and ecryptfs not working - readonly problems
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: How to avoid kern.log msg "Could not find key with description..."
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• How to avoid kern.log msg "Could not find key with description..."
  • From: cppljevans <cppljevans@xxxxxxxxxxxxxx>
• combination of cifs and ecryptfs not working - readonly problems
  • From: Hans-Joachim Kliemeck <info@xxxxxxxxxxx>
• [PATCH 4/4] ecryptfs: wire up nfs export operations
  • From: jaycelin <jaycelin@xxxxxxxxxxxx>
• [PATCH 3/4] ecryptfs: add export subtree_check support
  • From: jaycelin <jaycelin@xxxxxxxxxxxx>
• [PATCH 2/4] ecryptfs: add export_operations to ecryptfs
  • From: jaycelin <jaycelin@xxxxxxxxxxxx>
• [PATCH 1/4] ecryptfs: add ecryptfs_superblock_to_lower_mnt
  • From: jaycelin <jaycelin@xxxxxxxxxxxx>
• [PATCH 0/4] ecryptfs NFS export support
  • From: jaycelin <jaycelin@xxxxxxxxxxxx>
• [PATCH] ecryptfs: re-order a condition for static checkers
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] eCryptfs: fix permission denied with ecryptfs_xattr mount option when create readonly file
  • From: robbieko <robbieko@xxxxxxxxxxxx>
• RE: Dropbox dropping support for Ecryptfs!?!
  • From: "Soderquist, Erik" <Erik.Soderquist@xxxxxxxxxxxxx>
• Re: Dropbox dropping support for Ecryptfs!?!
  • From: Rich Wales <richw@xxxxxxxxx>
• RE: Dropbox dropping support for Ecryptfs!?!
  • From: "Soderquist, Erik" <Erik.Soderquist@xxxxxxxxxxxxx>
• Dropbox dropping support for Ecryptfs!?!
  • From: Rich Wales <richw@xxxxxxxxx>
• Re: [PATCH] eCryptfs: fix a couple type promotion bugs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: fix a couple type promotion bugs
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Python 3 compatibility
  • From: Lumir Balhar <lbalhar@xxxxxxxxxx>
• [GIT PULL] eCryptfs fixes for 4.17-rc2
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: fix spelling mistake: "cadidate" -> "candidate"
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: lookup: Don't check if mount_crypt_stat is NULL
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: don't pass up plaintext names when using filename encryption
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: fix spelling mistake: "cadidate" -> "candidate"
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• [PATCH] ecryptfs: Restore support for both encrypted and unencrypted file names
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• ecryptfs problems with encrypted/ unencrypted file names
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• [PATCH] ecryptfs: lookup: Don't check if mount_crypt_stat is NULL
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: bug: msm8998, ecryptfs, cannot create files due to invalid keysize
  • From: James Muir <james.muir@xxxxxxxxxxxxxxxxxxxx>
• Re: bug: msm8998, ecryptfs, cannot create files due to invalid keysize
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: bug: msm8998, ecryptfs, cannot create files due to invalid keysize
  • From: James Muir <james.muir@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] ecryptfs: sync before truncating lower inode
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [GIT PULL] eCryptfs fixes for 4.15-rc1
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH v2] ecryptfs: sync before truncating lower inode
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH] ecryptfs: Fix stat command displays wrong file size in xattr region
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: remove unnecessary i_version bump
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: remove unnecessary i_version bump
  • From: Jeff Layton <jlayton@xxxxxxxxxxxxxxx>
• [PATCH] ecryptfs: remove unnecessary i_version bump
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• bug: msm8998, ecryptfs, cannot create files due to invalid keysize
  • From: James Muir <james.muir@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] slab, slub, slob: convert slab_flags_t to 32-bit
  • From: Pekka Enberg <penberg@xxxxxx>
• Re: [PATCH 1/2] slab, slub, slob: add slab_flags_t
  • From: Pekka Enberg <penberg@xxxxxx>
• [PATCH 2/2] slab, slub, slob: convert slab_flags_t to 32-bit
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• [PATCH 1/2] slab, slub, slob: add slab_flags_t
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: [PATCH] ecryptfs: Fix stat command displays wrong file size in xattr region
  • From: Jason Xing <kerneljasonxing@xxxxxxxxx>
• Re: [PATCH 08/18] ecryptfs: use ARRAY_SIZE
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] eCryptfs: Adjustments for several function implementations
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: constify attribute_group structures.
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: use after free in ecryptfs_release_messaging()
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH v2 3/3] ecryptfs: move key payload accessor functions into keystore.c
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH v2 2/3] ecryptfs: fix out-of-bounds read of key payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH v2 1/3] ecryptfs: fix dereference of NULL user_key_payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: [PATCH 7/7] ecryptfs: move key payload accessor functions into keystore.c
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 6/7] ecryptfs: fix out-of-bounds read of key payload
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 5/7] ecryptfs: fix dereference of NULL user_key_payload
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 4/7] fscrypt: fix dereference of NULL user_key_payload
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 3/7] lib/digsig: fix dereference of NULL user_key_payload
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 2/7] FS-Cache: fix dereference of NULL user_key_payload
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 1/7] KEYS: encrypted: fix dereference of NULL user_key_payload
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: "Tobin C. Harding" <me@xxxxxxxx>
• [PATCH 08/18] ecryptfs: use ARRAY_SIZE
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• [PATCH 00/18] use ARRAY_SIZE macro
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• [PATCH 6/7] ecryptfs: fix out-of-bounds read of key payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 7/7] ecryptfs: move key payload accessor functions into keystore.c
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 4/7] fscrypt: fix dereference of NULL user_key_payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 5/7] ecryptfs: fix dereference of NULL user_key_payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 3/7] lib/digsig: fix dereference of NULL user_key_payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 2/7] FS-Cache: fix dereference of NULL user_key_payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 1/7] KEYS: encrypted: fix dereference of NULL user_key_payload
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• [PATCH 0/7] Fix dereferencing payload of revoked keys
  • From: Eric Biggers <ebiggers3@xxxxxxxxx>
• Re: Re-use SSD
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Re-use SSD
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: Re-use SSD
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Re-use SSD
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Re-use SSD
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re-use SSD
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: use after free in ecryptfs_release_messaging()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH 3/3] ecryptfs: Adjust four checks for null pointers
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] ecryptfs: Return an error code only as a constant in ecryptfs_add_global_auth_tok()
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] ecryptfs: Delete 21 error messages for a failed memory allocation
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/3] eCryptfs: Adjustments for several function implementations
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH] ecryptfs: convert to file_write_and_wait in ->fsync
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH] eCryptfs: constify attribute_group structures.
  • From: Arvind Yadav <arvind.yadav.cs@xxxxxxxxx>
• [PATCH] ecryptfs: Fix stat command displays wrong file size in xattr region
  • From: Jason Xing <kerneljasonxing@xxxxxxxxx>
• [PATCH v2] ecryptfs: sync before truncating lower inode
  • From: Andrey Pronin <apronin@xxxxxxxxxxxx>
• Re: [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode
  • From: Andrey Pronin <apronin@xxxxxxxxxxxx>
• Lots of errors "opening lower file for lower_dentry" and "ecryptfs_i_size_read: Error attempting to initialize the lower file", how to fix?
  • From: "Natanji ." <natanji@xxxxxxxxx>
• Re: [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode
  • From: Andrey Pronin <apronin@xxxxxxxxxxxx>
• Re: [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 0/25 v3] fs: Convert all embedded bdis into separate ones
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode
  • From: Andrey Pronin <apronin@xxxxxxxxxxxx>
• [PATCH 11/25] ecryptfs: Convert to separately allocated bdi
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 04/25] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 0/25 v3] fs: Convert all embedded bdis into separate ones
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 11/25] ecryptfs: Convert to separately allocated bdi
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 04/25] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 11/25] ecryptfs: Convert to separately allocated bdi
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 04/25] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 0/25 v2] fs: Convert all embedded bdis into separate ones
  • From: Jan Kara <jack@xxxxxxx>
• About hmac verification in eCryptfs
  • From: Wanli Xing <wlxing1996@xxxxxxxxx>
• [PATCH][RESEND] ecryptfs: fix spelling mistake: "cadidate" -> "candidate"
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: [lustre-devel] [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Jan Kara <jack@xxxxxxx>
• Re: [lustre-devel] [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: "Dilger, Andreas" <andreas.dilger@xxxxxxxxx>
• Re: [PATCH 11/24] ecryptfs: Convert to separately allocated bdi
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• [PATCH 0/24 RFC] fs: Convert all embedded bdis into separate ones
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 11/24] ecryptfs: Convert to separately allocated bdi
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH 04/24] fs: Provide infrastructure for dynamic BDIs in filesystems
  • From: Jan Kara <jack@xxxxxxx>
• [ecryptfs:seccomp-logging 1/5] include/linux/audit.h:511:20: error: '__audit_seccomp' declared 'static' but never defined
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [ecryptfs:seccomp-logging 2/5] include/linux/audit.h:528:20: warning: '__audit_seccomp' declared 'static' but never defined
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [ecryptfs:seccomp-logging 2/5] kernel/seccomp.c:580:3: error: implicit declaration of function 'audit_seccomp_errno'
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [ecryptfs:seccomp-logging 1/5] include/linux/audit.h:513:1: error: expected identifier or '(' before '{' token
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [PATCH] ecryptfs: fix non static symbol warning
  • From: Geliang Tang <geliangtang@xxxxxxxxx>
• strange(?) situation with ecryptfs
  • From: Felix Rubio <felix@xxxxxxxxx>
• [PATCH] ecryptfs: fix spelling mistake: "cadidate" -> "candidate"
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: Observed a ecryptFS crash
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: remove private bin2hex implementation
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: add missing \n to end of various error messages
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Observed a ecryptFS crash
  • From: xiakaixu <xiakaixu@xxxxxxxxxx>
• Re: [PATCH v6 00/16] Xattr inode operation removal
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v6 15/16] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v6 05/16] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH v6 05/16] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v6 16/16] vfs: Remove {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 15/16] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 14/16] vfs: Check for the IOP_XATTR flag in listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 13/16] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 12/16] libfs: Use IOP_XATTR flag for empty directory handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 11/16] vfs: Use IOP_XATTR flag for bad-inode handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 10/16] vfs: Add IOP_XATTR inode operations flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 09/16] vfs: Move xattr_resolve_name to the front of fs/xattr.c
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 08/16] lustre: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 07/16] ecryptfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 06/16] sockfs: Get rid of getxattr iop
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 05/16] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 04/16] kernfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 03/16] hfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 02/16] jffs2: Remove jffs2_{get,set,remove}xattr macros
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 01/16] xattr: Remove unnecessary NULL attribute name check
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v6 00/16] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Observed a ecryptFS crash
  • From: liushuoran <liushuoran@xxxxxxxxxx>
• Re: [PATCH v5 09/17] lustre: Switch to generic xattr handlers
  • From: "Dilger, Andreas" <andreas.dilger@xxxxxxxxx>
• [PATCH v5 17/17] vfs: Remove {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 16/17] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 15/17] vfs: Check for the IOP_XATTR flag in listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 14/17] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 13/17] libfs: Use IOP_XATTR flag for empty directory handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 12/17] vfs: Use IOP_XATTR flag for bad-inode handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 11/17] vfs: Add IOP_XATTR inode operations flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 10/17] vfs: Move xattr_resolve_name to the front of fs/xattr.c
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 09/17] lustre: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 08/17] fuse: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 07/17] ecryptfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 06/17] sockfs: Get rid of getxattr iop
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 05/17] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 04/17] kernfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 03/17] hfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 02/17] jffs2: Remove jffs2_{get,set,remove}xattr macros
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 01/17] xattr: Remove unnecessary NULL attribute name check
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v5 00/17] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH] ecryptfs: add missing \n to end of various error messages
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: remove private bin2hex implementation
  • From: Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx>
• question
  • From: марков сима <mar-sima@xxxxxxxxx>
• [PATCH] lustre: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH v4 20/20] vfs: Remove {get,set,remove}xattr inode operations
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH v4 13/20] vfs: Move xattr_resolve_name to the front of fs/xattr.c
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 07/20] hfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 14/20] vfs: Add IOP_XATTR inode operations flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 16/20] libfs: Use IOP_XATTR flag for empty directory handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 12/20] fuse: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 20/20] vfs: Remove {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 17/20] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 18/20] vfs: Check for the IOP_XATTR flag in listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 19/20] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 08/20] kernfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 09/20] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 10/20] sockfs: Get rid of getxattr iop
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 11/20] ecryptfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 15/20] vfs: Use IOP_XATTR flag for bad-inode handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 06/20] jffs2: Remove jffs2_{get,set,remove}xattr macros
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 05/20] xattr: Remove unnecessary NULL attribute name check
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 04/20] ovl: Switch to generic_getxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 03/20] ovl: Switch to generic_removexattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 02/20] ovl: Get rid of ovl_xattr_noacl_handlers array
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 01/20] ovl: Fix OVL_XATTR_PREFIX
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v4 00/20] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• encryptfs-utils porting on SailfishOS
  • From: Filin Ilya <ifilin88@xxxxxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Jeff Mahoney <jeffm@xxxxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Henry Jensen <hjensen@xxxxxx>
• [GIT PULL] eCryptfs fixes for 4.7-rc7
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Jeff Mahoney <jeffm@xxxxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: Fix directory open regression in linux-stable
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: Fix directory open regression in linux-stable
  • From: Jeff Mahoney <jeffm@xxxxxxxx>
• Re: [PATCH] eCryptfs: Fix directory open regression in linux-stable
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: Fix directory open regression in linux-stable
  • From: Henry Jensen <hjensen@xxxxxx>
• Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: Jann Horn <jann@xxxxxxxxx>
• [PATCH 1/2] Revert "ecryptfs: forbid opening files without mmap handler"
  • From: jeffm@xxxxxxxx
• [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
  • From: jeffm@xxxxxxxx
• Re: [PATCH] eCryptfs: Fix directory open regression in linux-stable
  • From: Jeff Mahoney <jeffm@xxxxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Henry Jensen <hjensen@xxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Henry Jensen <hjensen@xxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Henry Jensen <hjensen@xxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: Fix directory open regression in linux-stable
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Kenneth Tan <gmane@xxxxxxxxxxxxxxxxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Henry Jensen <hjensen@xxxxxx>
• Re: Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Can't list directories with kernel 4.4.14 and ecryptfs
  • From: Henry Jensen <hjensen@xxxxxx>
• Re: [PATCH] ecryptfs: fix spelling mistakes
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: fix spelling mistakes
  • From: Chris J Arges <chris.j.arges@xxxxxxxxxxxxx>
• Re: [PATCH v3 00/17] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH v3 00/17] Xattr inode operation removal
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH v3 00/17] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH v3 00/17] Xattr inode operation removal
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH v3 00/17] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 17/17] vfs: Remove {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 16/17] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 13/17] libfs: Use IOP_XATTR flag for empty directory handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 15/17] vfs: Check for the IOP_XATTR flag in listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 14/17] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 12/17] vfs: Use IOP_XATTR flag for bad-inode handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 11/17] vfs: Add IOP_XATTR inode operations flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 10/17] vfs: Move xattr_resolve_name to the front of fs/xattr.c
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 09/17] fuse: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 08/17] overlayfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 07/17] ecryptfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 06/17] sockfs: Get rid of getxattr iop
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 01/17] xattr: Remove unnecessary NULL attribute name check
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 05/17] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 04/17] kernfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 03/17] hfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 02/17] jffs2: Remove jffs2_{get,set,remove}xattr macros
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v3 00/17] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH v2 10/18] evm: Turn evm_update_evmxattr into void function
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 15/18] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v2 10/18] evm: Turn evm_update_evmxattr into void function
  • From: James Morris <jmorris@xxxxxxxxx>
• [PATCH v2 18/18] vfs: Remove {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 17/18] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 16/18] vfs: Check for the IOP_XATTR flag in listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 15/18] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 10/18] evm: Turn evm_update_evmxattr into void function
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 14/18] libfs: Use IOP_XATTR flag for empty directory handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 13/18] vfs: Use IOP_XATTR flag for bad-inode handling
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 12/18] vfs: Add IOP_XATTR inode operations flag
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 11/18] vfs: Move xattr_resolve_name to the front of fs/xattr.c
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 09/18] fuse: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 08/18] overlayfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 07/18] ecryptfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 06/18] sockfs: Get rid of getxattr iop
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 05/18] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 04/18] kernfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 03/18] hfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 02/18] jffs2: Remove jffs2_{get,set,remove}xattr macros
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 01/18] xattr: Remove unnecessary NULL attribute name check
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH v2 00/18] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH] xattr handlers: fixup generic_listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH] xattr handlers: fixup generic_listxattr
  • From: James Simmons <jsimmons@xxxxxxxxxxxxx>
• Re: [RFC 8/8] xattr: Remove generic xattr handlers
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [RFC 5/8] xattr: Add per-inode xattr handlers as a new inode operation
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] xattr handlers: fixup generic_listxattr
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [PATCH] xattr handlers: fixup generic_listxattr
  • From: James Simmons <jsimmons@xxxxxxxxxxxxx>
• Re: [RFC 0/8] Xattr inode operation removal
  • From: James Simmons <jsimmons@xxxxxxxxxxxxx>
• Re: [RFC 4/8] evm: Turn evm_update_evmxattr into void function
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [RFC 4/8] evm: Turn evm_update_evmxattr into void function
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [RFC 0/8] Xattr inode operation removal
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [RFC 0/8] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [RFC 0/8] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [RFC 0/8] Xattr inode operation removal
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [RFC 0/8] Xattr inode operation removal
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [RFC 8/8] xattr: Remove generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 7/8] xattr: Stop calling {get,set,remove}xattr inode operations
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 6/8] xattr: Add __vfs_{get,set,remove}xattr helpers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 5/8] xattr: Add per-inode xattr handlers as a new inode operation
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 4/8] evm: Turn evm_update_evmxattr into void function
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 3/8] fuse: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 2/8] overlayfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 1/8] ecryptfs: Switch to generic xattr handlers
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• [RFC 0/8] Xattr inode operation removal
  • From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
• Re: [PATCH v2] ecryptfs: open lower files using kernel creds
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: INFO: inconsistent lock state in ecryptfs_calculate_md5
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• INFO: inconsistent lock state in ecryptfs_calculate_md5
  • From: Nicolas Boichat <drinkcat@xxxxxxxxxxxx>
• [PATCH v2] ecryptfs: open lower files using kernel creds
  • From: Ricky Zhou <rickyz@xxxxxxxxxxxx>
• Re: [PATCH] ecryptfs: open lower files on kthread under SELinux
  • From: Ricky Zhou <rickyz@xxxxxxxxxxxx>
• Re: Max 26 concurrent ecryptfs mounts?
  • From: James Muir <muir.james.a@xxxxxxxxx>
• Re: [PATCH] ecryptfs: open lower files on kthread under SELinux
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: open lower files on kthread under SELinux
  • From: Ricky Zhou <rickyz@xxxxxxxxxxxx>
• RE: Practical use of ecryptfs, encrypted keys, and TPM: how to convert existing user key to encrypted key?
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• combination of cifs and ecryptfs
  • From: Hans-Joachim Kliemeck <info@xxxxxxxxxxx>
• Re: Practical use of ecryptfs, encrypted keys, and TPM: how to convert existing user key to encrypted key?
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• RE: Practical use of ecryptfs, encrypted keys, and TPM: how to convert existing user key to encrypted key?
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Re: Practical use of ecryptfs, encrypted keys, and TPM: how to convert existing user key to encrypted key?
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Practical use of ecryptfs, encrypted keys, and TPM: how to convert existing user key to encrypted key?
  • From: "James Johnston" <johnstonj.public@xxxxxxxxxxxx>
• Max 26 concurrent ecryptfs mounts?
  • From: Joe Lauer <joe@xxxxxxxxxxxxx>
• Re: eCryptfs: Use skcipher and shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• re: eCryptfs: Use skcipher and shash
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• re: eCryptfs: Use skcipher and shash
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] eCryptfs: fix typos in comment
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: fix typos in comment
  • From: Wei Yuan <weiyuan.wei@xxxxxxxxxx>
• File recovery via testdisk / photorec
  • From: tmg <t.m.gerlach@xxxxxxxxxx>
• [PATCH] eCryptfs: fix typos in comment
  • From: Wei Yuan <weiyuan.wei@xxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Re: Key derivation and passprhase wrapping
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: how to retrun different size to different process when I use ecryptfs
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [v2 PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: Clean up crypto initialization
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 17/26] mac802154: Use skcipher
  • From: Stefan Schmidt <stefan@xxxxxxxxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 22/26] iscsi_tcp: Use ahash
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [PATCH 16/26] libceph: Use skcipher
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• re: [PATCH] eCryptfs: Clean up crypto initialization
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 15/26] Bluetooth: Use skcipher and hash
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• Re: [PATCH 25/26] sctp: Use shash
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 26/26] tcp: Use ahash
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [v2 PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 6/26] staging: rtl8192u: Use skcipher and ahash
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 3/26] staging: rtl8192e: Replace uses of obsolete blkcipher and hash
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Julia Lawall <julia.lawall@xxxxxxx>
• Re: [PATCH 21/26] nfc: s3fwrn5: Use shash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 24/26] nfsd: Use shash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 4/26] dm crypt: Use skcipher and ahash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/26] block: cryptoloop - Use new skcipher interface
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 7/26] wusb: Use skcipher
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 15/26] Bluetooth: Use skcipher and hash
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/26] block: cryptoloop - Use new skcipher interface
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH 1/26] block: cryptoloop - Use new skcipher interface
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 3/26] staging: rtl8192e: Replace uses of obsolete blkcipher and hash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 4/26] dm crypt: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 6/26] staging: rtl8192u: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 7/26] wusb: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 8/26] cifs: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 9/26] eCryptfs: Use skcipher and shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 10/26] ext4: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 13/26] lib80211: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 15/26] Bluetooth: Use skcipher and hash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 17/26] mac802154: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 18/26] rxrpc: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 20/26] drbd: Use shash and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 21/26] nfc: s3fwrn5: Use shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 22/26] iscsi_tcp: Use ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 23/26] iscsi-target: Use shash and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 24/26] nfsd: Use shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 25/26] sctp: Use shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 26/26] tcp: Use ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 19/26] ipsec: Use skcipher and ahash when probing algorithms
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 16/26] libceph: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 14/26] KEYS: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 12/26] sunrpc: Use skcipher and ahash/shash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 11/26] f2fs: Use skcipher
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 5/26] orinoco: Use ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 2/26] ppp_mppe: Use skcipher and ahash
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH 0/26] crypto: Use skcipher and ahash/shash where possible
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• how to retrun different size to different process when I use ecryptfs
  • From: zhangzhilei <sdhzdmzzl@xxxxxxxx>
• Re: Key derivation and passprhase wrapping
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Re: Key derivation and passprhase wrapping
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Re: Key derivation and passprhase wrapping
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Re: bcrypt or other key derivation algorithm
  • From: Sylvain Pelissier <sylvain.pelissier@xxxxxxxxx>
• bcrypt or other key derivation algorithm
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Key derivation and passprhase wrapping
  • From: Wiebe Cazemier <wiebe@xxxxxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: An new, fast and "unbreakable" encryption algorithm
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• An new, fast and "unbreakable" encryption algorithm
  • From: Ismail Kizir <ikizir@xxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: andreym@xxxxxxxxxxxxxx
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Andrey Markovytch <andreym@xxxxxxxxxxxxxx>
• [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
  • From: Andrey Markovytch <andreym@xxxxxxxxxxxxxx>
• [PATCH 6/6] KEYS: Merge the type-specific data with the payload data
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 28/39] ecryptfs: drop null test before destroy functions
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 28/39] ecryptfs: drop null test before destroy functions
  • From: Julia Lawall <julia.lawall@xxxxxxx>
• Re: [PATCH 28/39] ecryptfs: drop null test before destroy functions
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 00/39] drop null test before destroy functions
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 00/39] drop null test before destroy functions
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 28/39] ecryptfs: drop null test before destroy functions
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [GIT PULL] eCryptfs fixes for 4.3-rc1
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH V1 Resend 07/10] fs: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH V1 Resend 07/10] fs: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Steve French <smfrench@xxxxxxxxx>
• [PATCH V1 Resend 07/10] fs: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• [PATCH V1 Resend 08/11] fs: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [PATCH] eCryptfs: Delete a check before the function call "key_put"
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: Invalidate dcache entries when lower i_nlink is zero
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [RFC][PATCH] ecryptfs: Allow only one instance per lower path
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH 12/15] fs: Drop unlikely before IS_ERR(_OR_NULL)
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 12/15] fs: Drop unlikely before IS_ERR(_OR_NULL)
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: Problem "cracking" a key_sig
  • From: Marc Peña Segarra <segarrra@xxxxxxxxx>
• Re: Problem "cracking" a key_sig
  • From: "Wiest, Damian" <damian.wiest@xxxxxxxxxxxx>
• Re: Problem "cracking" a key_sig
  • From: "Wiest, Damian" <damian.wiest@xxxxxxxxxxxx>
• Fwd: Problem "cracking" a key_sig
  • From: Marc Peña Segarra <segarrra@xxxxxxxxx>
• [PATCH] eCryptfs: Delete a check before the function call "key_put"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [f2fs-dev] [PATCH v2] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [f2fs-dev] [PATCH v2] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• ecryptfs access restrictions
  • From: otherthan company <otherthancompany@xxxxxxxxx>
• Re: Way to decrypt an encrypted /home
  • From: Pablo Castellano <pablo@xxxxxxxx>
• Re: Way to decrypt an encrypted /home
  • From: Marc de Verdelhan <mdeverdelhan@xxxxxxxxx>
• Re: Way to decrypt an encrypted /home
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Way to decrypt an encrypted /home
  • From: Marc de Verdelhan <mdeverdelhan@xxxxxxxxx>
• [GIT PULL] eCryptfs fixes for 4.0-rc3
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: don't pass fs-specific ioctl commands through
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: ensure copy to crypt_stat->cipher does not overrun
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: ensure copy to crypt_stat->cipher does not overrun
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: Changing salt value
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Changing salt value
  • From: Sylvain Pelissier <sylvain.pelissier@xxxxxxxxx>
• Re: Changing salt value
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Changing salt value
  • From: Sylvain Pelissier <sylvain.pelissier@xxxxxxxxx>
• small buffer overflow in ecryptfs_new_file_context()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: 32-byte encryption key for ecryptfs-setup-private ?
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• 32-byte encryption key for ecryptfs-setup-private ?
  • From: Eric Lan <tenoreamer@xxxxxxxxx>
• Feature Request: solving too long filenames
  • From: Eric Lan <tenoreamer@xxxxxxxxx>
• [GIT PULL] eCryptfs fixes for 3.19-rc1
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• ecryptfs & error opening lower file for lower_dentry on ZFS volumes with ZFS snapshots
  • From: "Alex Braunegg" <alex.braunegg@xxxxxxxxx>
• Re: [PATCH] eCryptfs: Allocate sufficient buffer space for encrypted filename decoding
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] eCryptfs: Remove buggy and unnecessary write in file name decode routine
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: Remove buggy and unnecessary write in file name decode routine
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• Re: [PATCH] eCryptfs: Allocate sufficient buffer space for encrypted filename decoding
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• Re: PROBLEM: apparent out-of-bounds memory write in fs/ecryptfs/crypto.c
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH] eCryptfs: Allocate sufficient buffer space for encrypted filename decoding
  • From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
• PROBLEM: apparent out-of-bounds memory write in fs/ecryptfs/crypto.c
  • From: Dmitry Chernenkov <dmitryc@xxxxxxxxxx>
• [PATCH 16/56] fs/encryptfs: support compiling out splice
  • From: Pieter Smith <pieter@xxxxxxxxxx>
• AW: BUG() in ecryptfs_send_miscdev()
  • From: Anna Fischer <a.fischer@xxxxxxxxxx>
• BUG() in ecryptfs_send_miscdev()
  • From: Anna Fischer <a.fischer@xxxxxxxxxx>
• [PATCH] eCryptfs: Remove unnecessary casts when parsing packet lengths
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: is size correct in ecryptfs_parse_packet_length()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: is size correct in ecryptfs_parse_packet_length()
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• is size correct in ecryptfs_parse_packet_length()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 3/4] ecryptfs: add fadvise/set_flags calbacks
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 3/4] ecryptfs: add fadvise/set_flags calbacks
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• [PATCH 3/3] ecryptfs: add fadvise/set_flags calbacks
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Re: [PATCH] ecryptfs: remove unneeded buggy code in ecryptfs_do_create()
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [GIT PULL] eCryptfs fixes for 3.18
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] eCryptfs: Force RO mount when encrypted view is enabled
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH] NULL pointer dereference in ecryptfs (ecryptfs_setxattr)
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• AW: Separating different ecryptfs mounts
  • From: Anna Fischer <a.fischer@xxxxxxxxxx>
• Re: Mount parameters
  • From: Wilson <wilson.ubuntu@xxxxxxxxx>
• Re: Mount parameters
  • From: Michael Chang <thenewme91@xxxxxxxxx>
• Re: Mount parameters
  • From: Wilson <wilson.ubuntu@xxxxxxxxx>
• Re: Mount parameters
  • From: Michael Chang <thenewme91@xxxxxxxxx>
• Mount parameters
  • From: Wilson <wilson.ubuntu@xxxxxxxxx>
• Re: Separating different ecryptfs mounts
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Separating different ecryptfs mounts
  • From: Christian Stüble <stueble@xxxxxxxxxx>
• Re: Separating different ecryptfs mounts
  • From: Christian Stüble <stueble@xxxxxxxxxx>
• Re: Separating different ecryptfs mounts
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Separating different ecryptfs mounts
  • From: Christian Stüble <stueble@xxxxxxxxxx>
• Re: Separating different ecryptfs mounts
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Separating different ecryptfs mounts
  • From: Christian Stüble <stueble@xxxxxxxxxx>
• [PATCH] NULL pointer dereference in ecryptfs (ecryptfs_setxattr)
  • From: Priya Bansal <p.bansal@xxxxxxxxxxx>
• Re: Practical questions about locking and re-encrypting
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: hardware acceleration
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• hardware acceleration
  • From: Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx>
• Re: Practical questions about locking and re-encrypting
  • From: Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx>
• [PATCH] ecryptfs: remove unneeded buggy code in ecryptfs_do_create()
  • From: Alexey Khoroshilov <khoroshilov@xxxxxxxxx>
• Re: Practical questions about locking and re-encrypting
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Practical questions about locking and re-encrypting
  • From: Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx>
• RE: [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
  • From: Chao Yu <chao2.yu@xxxxxxxxxxx>
• RE: [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
  • From: Chao Yu <chao2.yu@xxxxxxxxxxx>
• Re: [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH] ecryptfs: avoid to access NULL pointer when write metadata in xattr
  • From: Chao Yu <chao2.yu@xxxxxxxxxxx>
• Re: [PATCH 1/1] ecryptfs: remove unnecessary break after goto
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH 1/1] ecryptfs: remove unnecessary break after goto
  • From: Fabian Frederick <fabf@xxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] fs/ecryptfs/messaging.c: remove null test before kfree
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH v2] ecryptfs: Drop cast
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• [PATCH v2] ecryptfs: Drop cast
  • From: Himangi Saraogi <himangi774@xxxxxxxxx>
• Re: [PATCH] ecryptfs: Drop cast
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] ecryptfs: Drop cast
  • From: Himangi Saraogi <himangi774@xxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 1/1] fs/ecryptfs/messaging.c: remove null test before kfree
  • From: Fabian Frederick <fabf@xxxxxxxxx>
• Recovering Encrypted Directory
  • From: Tom Browder <tom.browder@xxxxxxxxx>
• Re: kernel crash after enable ecryptfs under abnormal power off
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• kernel crash after enable ecryptfs under abnormal power off
  • From: Hanks Wang <wangwenjie@xxxxxxxx>
• Re: Please patch key_mod.c
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: ecryptfs_privileged_open(): when kthread-ecryptfs is required ?
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• ecryptfs_privileged_open(): when kthread-ecryptfs is required ?
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• Please patch key_mod.c
  • From: "Jaroslav Fojtik" <jafojtik@xxxxxxxxx>
• Re: [PATCH 3/3] eCryptfs: Enable GCM support in eCryptfs
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• Erasing keys in ram
  • From: zero <zero923@xxxxxxxxx>
• NFS -> eCryptfs -> Samba = files disappearing
  • From: Jon Skarpeteig <jon.skarpeteig@xxxxxxxxx>
• Re: ecryptfs log spew from EINTR
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• ecryptfs log spew from EINTR
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• [PATCH 3/3] eCryptfs: Enable GCM support in eCryptfs
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• [PATCH 2/3] eCryptfs: Extend file headers to store cipher mode.
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• [PATCH 1/3] eCryptfs: Add mount option for cipher mode
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• PATCH [0/3] Integrity protection with GCM
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• Automated home encryption and noexec mount option
  • From: Wilson <wilson.ubuntu@xxxxxxxxx>
• Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
  • From: Lance Reed <reed.r.lance@xxxxxxxxx>
• Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
  • From: Lance Reed <reed.r.lance@xxxxxxxxx>
• Re: [RFC 3/3] Enable GCM support in eCryptfs
  • From: Taylor Hornby <havoc@xxxxxxxxx>
• Security Audit
  • From: Taylor Hornby <havoc@xxxxxxxxx>
• Re: How best to crack wrapped-passphrase?
  • From: Tom Vaughan <thomas.david.vaughan@xxxxxxxxx>
• Re: How best to crack wrapped-passphrase?
  • From: Artur Rataj <arturrataj@xxxxxxxxx>
• Re: How best to crack wrapped-passphrase?
  • From: Tom Vaughan <thomas.david.vaughan@xxxxxxxxx>
• Re: How best to crack wrapped-passphrase?
  • From: Artur Rataj <arturrataj@xxxxxxxxx>
• Fwd: How best to crack wrapped-passphrase?
  • From: Artur Rataj <arturrataj@xxxxxxxxx>
• [RFC 0/3] Enable GCM support
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• [RFC 3/3] Enable GCM support in eCryptfs
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• [RFC 2/3] eCryptfs: Extend file headers to store cipher mode.
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• [RFC 1/3] eCryptfs: Add mount option for cipher mode
  • From: Will Morrison <camocrazed@xxxxxxxxx>
• How best to crack wrapped-passphrase?
  • From: Tom Vaughan <thomas.david.vaughan@xxxxxxxxx>
• PROBLEM: Core dump in ecryptfs directory on ext4 crashes kernel if aesni_intel is used
  • From: Maarten Baert <maarten-baert@xxxxxxxxxxx>
• Re: eCryptfs using openssl encountered "Transport endpoint is not connected" when writting file into the mounted folder
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: [PATCH 5/9] Use %pd in eCryptFS
  • From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
• Re: Did I lost an encrypted folder?
  • From: Artur Rataj <arturrataj@xxxxxxxxx>
• Did I lost an encrypted folder?
  • From: Artur Rataj <arturrataj@xxxxxxxxx>
• Re: ecryptfs with an epehemeral key
  • From: Eric Tschetter <echeddar@xxxxxxxxx>
• Re: ecryptfs with an epehemeral key
  • From: Michael Chang <m9chang@xxxxxxxxxxxx>
• ecryptfs with an epehemeral key
  • From: Eric Tschetter <echeddar@xxxxxxxxx>
• [PATCH 5/9] Use %pd in eCryptFS
  • From: David Howells <dhowells@xxxxxxxxxx>