Package: tomb Version: 2.5+dfsg1-2 Severity: normal Tags: upstream Dear Maintainer,
creating, opening and closing a new tomb by tomb dig -s 20 x.tomb tomb forge --unsafe --use-urandom --tomb-pwd x x.key tomb lock --unsafe --tomb-pwd x -k x.key -o aes-xts-plain64 x.tomb tomb open --unsafe --tomb-pwd x -k x.key x.tomb tomb close x results in error messages between the ultimate lines of output: [...] tomb (*) Success opening x.tomb on /media/x _update_control_file:7: permission denied: /media/x/.uid chown: cannot access '/media/x/.uid': No such file or directory _update_control_file:7: permission denied: /media/x/.tty chown: cannot access '/media/x/.tty': No such file or directory _update_control_file:7: permission denied: /media/x/.host chown: cannot access '/media/x/.host': No such file or directory _update_control_file:7: permission denied: /media/x/.last chown: cannot access '/media/x/.last': No such file or directory tomb . Closing tomb [x] mounted on /media/x tomb (*) Tomb [x] closed: your bones will rest in peace. These error messages show up on each 'tomb open' when done with the -p option tomb open --unsafe --tomb-pwd x -k x.key -p x.tomb The opened tomb is usable despite all that. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tomb depends on: ii cryptsetup-bin 2:2.1.0-5 ii e2fsprogs 1.44.5-1 ii gnupg 2.2.12-1 ii pinentry-gnome3 [pinentry] 1.1.0-2 ii sudo 1.8.27-1 ii zsh 5.7.1-1 tomb recommends no packages. tomb suggests no packages. -- no debconf information
