On 03/28/2018 08:33 AM, Guenter Roeck wrote:
> On 03/27/2018 08:58 AM, Tyler Hicks wrote:
>> Hello Guenter
>>
>> On 02/13/2018 04:36 PM, Guenter Roeck wrote:
>>> Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or
>>> plaintext name") was supposed to fix a situation where two file
On 03/27/2018 08:58 AM, Tyler Hicks wrote:
Hello Guenter
On 02/13/2018 04:36 PM, Guenter Roeck wrote:
Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or
plaintext name") was supposed to fix a situation where two files with
the same name and same inode could be created in ecry
Hello Guenter
On 02/13/2018 04:36 PM, Guenter Roeck wrote:
> Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or
> plaintext name") was supposed to fix a situation where two files with
> the same name and same inode could be created in ecryptfs. One of those
> files had an encryp
ping
On Tue, Feb 13, 2018 at 02:36:08PM -0800, Guenter Roeck wrote:
> Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or
> plaintext name") was supposed to fix a situation where two files with
> the same name and same inode could be created in ecryptfs. One of those
> files had
Commit 88ae4ab9802e ("ecryptfs_lookup(): try either only encrypted or
plaintext name") was supposed to fix a situation where two files with
the same name and same inode could be created in ecryptfs. One of those
files had an encrypted file name, the other file name was unencrypted.
After commit 88
5 matches
Mail list logo