tomb broke after last update

tomw_ · 2016-12-20 19:24:54

Hi, I use tomb on luks. After last upgrade I cant open tomb file. https://www.dyne.org/software/tomb/

$ tomb open priv.tomb -k priv.tomb.key -f -D
tomb [D] Identified caller: tomasz (1000:100)
tomb [D] Tomb command: open priv.tomb
tomb [D] Caller: uid[1000], gid[100], tty[/dev/pts/1].
tomb [D] Temporary directory: /tmp/zsh
tomb . Commanded to open tomb priv.tomb
tomb [D] is_valid_tomb priv.tomb
tomb . Valid tomb file found: priv.tomb
tomb [D] load_key argument: priv.tomb.key
tomb [D] load_key: priv.tomb.key
tomb [D] is_valid_key
tomb . Key is valid.
tomb . Mountpoint not specified, using default: /run/media/tomasz/priv
tomb (*) Opening priv on /run/media/tomasz/priv
tomb . This tomb is a valid LUKS encrypted device.
tomb . Cipher is "aes" mode "xts-plain64:sha256" hash "sha1"
tomb [D] dev mapper device: tomb.priv.1482261742.loop0
tomb [D] Tomb key: priv.tomb.key
tomb [D] Tomb name: priv (to be engraved)
tomb . A password is required to use key priv.tomb.key
tomb [D] asking password with tty=/dev/pts/1 lc-ctype=pl_PL.UTF-8
tomb [D] using pinentry-gtk2

** (pinentry-gtk-2:3540): WARNING **: it took 249 tries to grab the keyboard
tomb [D] get_lukskey
tomb [D] get_lukskey returns 0
tomb . Password OK.
tomb [E] Failure mounting the encrypted file.

Maybe somebody can help? I dont have access to many important files

tralce · 2016-12-22 22:09:21

I am also having this problem.

Stefan Husmann · 2016-12-23 02:52:18

What was upgraded? Does downgrading help?

der_joachim · 2016-12-24 07:14:12

It appears that the pinentry package was updated earlier this month. You may want to try do downgrade that package to an earlier version and see whether that solves your problems.

I am having the same problem (and did not downgrade). Part of the solution is bypassing pinentry-gtk2 and falling back to pinentry-curses. You can achieve that by unsetting DISPLAY.

Try the following command:

$ unset DISPLAY && tomb open priv.tomb -k priv.tomb.key -f -D

[edit]: Quickcougar gave the correct answer below. It wasn't pinentry that broke tomb, but zsh. Pinentry does give some weird warnings, but this does not break tomb.

Last edited by der_joachim (2016-12-24 20:01:22)

quickcougar · 2016-12-24 15:47:34

After determining what changed since my last working state on 2016-12-14, I narrowed suspect packages down to gnupg, libcrypt, and finally zsh.

Upgrading zsh from 5.2-2 caused tomb report "Failure mounting the encrypted file." and fail to function properly.

[2016-12-20 09:57] [ALPM] upgraded zsh (5.2-2 -> 5.3-1)

These zsh versions do NOT work with aur/tomb 2.2-3
zsh-5.3-1-x86_64
zsh-5.3.1-1-x86_64

The issue is also reported here:
https://github.com/dyne/Tomb/commit/b9f … f28736135c
https://github.com/dyne/Tomb/issues/232

A temporary fix (x86_64) is to downgrade zsh to 5.2-2:

sudo pacman -U /var/cache/pacman/pkg/zsh-5.2-2-x86_64.pkg.tar.xz

Last edited by quickcougar (2016-12-24 15:54:58)

Stefan Husmann · 2016-12-24 22:09:57

Or to use bash ...

der_joachim · 2016-12-25 06:21:03

Stefan Husmann wrote:

Or to use bash ...

You are aware that tomb is basically a huge zsh script, right?

Stefan Husmann · 2016-12-26 15:46:49

Actually I was not. Sorry for the bad advice.

Arch Linux

#1 2016-12-20 19:24:54

tomb broke after last update

#2 2016-12-22 22:09:21

Re: tomb broke after last update

#3 2016-12-23 02:52:18

Re: tomb broke after last update

#4 2016-12-24 07:14:12

Re: tomb broke after last update

#5 2016-12-24 15:47:34

Re: tomb broke after last update

#6 2016-12-24 22:09:57

Re: tomb broke after last update

#7 2016-12-25 06:21:03

Re: tomb broke after last update

#8 2016-12-26 15:46:49

Re: tomb broke after last update

Board footer