Tomb

[feboss]

i try tomb plugin but when i enter password the answer is always could not decrypt...wrong key? same with gpg plugin

[mhogomchungu]

How did you create your tomb? can you unlock the tomb using the tomb script? If yes,what steps do you do when you do that? I am asking the above because i just created a tomb using steps specified in their home page[1] and it opened correctly.

The tomb plugin is used for tombs that stores their key in an image file using steghide.

The "regular" tombs are opened with the gpg plugin.

[1] https://www.dyne.org/software/tomb/

[feboss]

so in the plugin area i have steghide and tomb. what the differences? 1)yes with the tomb script i can open the tomb (tomb open) 2) tomb open secret2.tomb -k secret2

tomb dig -s 10 secret2.tomb tomb forge secret2 tomb lock secret2.tomb -k secret

this is my key secret2 with password ciao https://www.dropbox.com/s/97zum25nzlyw88g/secret2?dl=0

this is my secret2.tomb of 10mb https://www.dropbox.com/s/d16vlhtpowz8iex/secret2.tomb?dl=0

[mhogomchungu]

The volume you linked to opened here with "gpg" plugin.It does not in your system?

steghide is a tool that hides information in image files.The steghide plugin is for those who want to store their volume keys hidden in image files using the steghide tool.

The tomb project stores keys in 2 different ways.

1. In a gpg enclosure and zuluCrypt opens them using the "gpg" plugin.
2. In a gpg enclosure that is hidden in an image file using steghide tool and zuluCrypt opens them using the "tomb" plugin.

keys that are hidden in image files using steghide can be retrieved using the "steghide" plugin.This plugin is completely independent of the tomb project.

The volume you link to has its key in a gpg enclosue and hence the plugin to use is "gpg" plugin.

[feboss]

Do you try to open the tomb?

[mhogomchungu]

Yes, I opened the volume you gave me using tomb script and it worked.I also tried to open it using zuluCrypt and it worked too.

Maybe you are using a wrong version of zuluCrypt,what version of zuluCrypt are you using? You can know the version by running the following command from the terminal

zuluCrypt-cli -v

[feboss]

version : 4.7.2 copyright: 2011-2014 Ink Francis,mhogomchungu@gmail.com license : GPLv2+

i get it from this https://aur.archlinux.org/packages/zulucrypt/

later i install also the git version(4.7.3) from the aur but still not work. i try also from the command line

[mhogomchungu]

There must be something interfering in your system,maybe a locale issue.

what does this command give you?

 env | grep -i lang

ps: copy and paste the command to make sure you dont mistype it.

The command will give information about the language setting of your system.

[feboss]

LANG=it_IT.UTF-8

[feboss]

is possible that the reason is because i not run with root privileges? but when i try to run with sudo i get a lot of error and blank page

X Error: BadAccess (attempt to access private resource denied) 10
  Extension:    130 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x153
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    130 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x9d
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x1600013

[mhogomchungu]

I changed locale to italian and i found no problem and hence the problem is not with locale.

zuluCrypt is meant to be run from normal user account.

Though you might be on to something.Tomb requires root's privileges and you are using it while already as root.

You are running zuluCrypt as normal user and the reason you could not decrypt the gpg key maybe because the key has permissions that prevents a normal user from reading it.

Try to change the permissions of the key to allow your normal account to read it and try again.

[feboss]

ok this is very strange behaviour. Work only if i do

gpg -d keyfile

i put password and later when i open with zulucrypt everything work

[mhogomchungu]

That is strange. I did a bit of goggling to try to explain it and nothing came up yet. Will keep on looking for an explanation and hopefully something will come up and its something i will be able to prevent programmatically.

For now,i am closing this bug report since you can now open your volume normally.

The bug will be closed but feel free to add anything if anything comes up.