[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#610949: marked as done (ecryptfs: second ls lists empty directory)

Your message dated Fri, 23 Apr 2021 10:22:03 +0200
with message-id <[🔎] YIKDqyAzjY+1YgXn@eldamar.lan>
and subject line Re: Bug#610949: second ls lists empty directory
has caused the Debian Bug report #610949,
regarding ecryptfs: second ls lists empty directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
610949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610949
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ecryptfs-utils
Version: 83-4
Severity: important

* Create ~/Private with ecryptfs-setup-private.
* Touch ~/Private/x.
* ls ~/Private/ -> x is listed.
* ls ~/Private/ -> x is NOT listed anymore.
* cat ~/Private/x -> x is still accessible.  (Also spits out the right
  content on real files.)

~ > ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [449389e85fc0b564] into the user session keyring
~ > ls Private
x
~ > ls Private
~ > cat Private/x
~ > cat Private/y
cat: Private/y: No such file or directory

So you have one readdir() you can make, the second one will be empty.  (Also
happening with nautilus etc.)

-- System Information:
Debian Release: 6.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (500, 'stable'), (100, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ecryptfs-utils depends on:
ii  gettext-base                  0.18.1.1-3 GNU Internationalization utilities
ii  keyutils                      1.4-1      Linux Key Management Utilities
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib
ii  libecryptfs0                  83-4       ecryptfs cryptographic filesystem 
ii  libgpg-error0                 1.6-1      library for common error values an
ii  libgpgme11                    1.2.0-1.2  GPGME - GnuPG Made Easy
ii  libkeyutils1                  1.4-1      Linux Key Management Utilities (li
hi  libnss3-1d                    3.12.8-1   Network Security Service libraries
ii  libpam-runtime                1.1.1-6.1  Runtime support for the PAM librar
ii  libpam0g                      1.1.1-6.1  Pluggable Authentication Modules l

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
ii  cryptsetup                    2:1.1.3-4  configures encrypted block devices
pn  opencryptoki                  <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
Control: tags -1 + moreinfo

Hi Philipp,

On Mon, Jan 24, 2011 at 11:32:52AM +0100, Philipp Kern wrote:
> Package: ecryptfs-utils
> Version: 83-4
> Severity: important
> 
> * Create ~/Private with ecryptfs-setup-private.
> * Touch ~/Private/x.
> * ls ~/Private/ -> x is listed.
> * ls ~/Private/ -> x is NOT listed anymore.
> * cat ~/Private/x -> x is still accessible.  (Also spits out the right
>   content on real files.)
> 
> ~ > ecryptfs-mount-private
> Enter your login passphrase:
> Inserted auth tok with sig [449389e85fc0b564] into the user session keyring
> ~ > ls Private
> x
> ~ > ls Private
> ~ > cat Private/x
> ~ > cat Private/y
> cat: Private/y: No such file or directory
> 
> So you have one readdir() you can make, the second one will be empty.  (Also
> happening with nautilus etc.)

Doing some cleanup on src:linux filled bugs. I guess this issue is
after serveal years not anymore reproducible? I'm closing the
bugreport for now, but feel free to reopen in case the issue still can
be triggered.

Regards,
Salvatore

--- End Message ---
Reply to: