I already did a search for Kingston, dtvp, encrypt, usb, vault, but didn’t get any interesting results. So I try it this way.
I own a Kingston DataTraveler Vault 4GB. This device has been set up on Kubuntu following the official manual and it works on Kubuntu pretty fine.
To use it on my main machine with Manjaro i3, I do
cd /run/media/daniel/DTVP30/linux/linux64/
sudo ./DTVP_login
After entering my sudo-password there is a message “Can not detect DTVP device !!”
In PCMANFM the stick is shown, the unprotected part of course. But when pressing “eject” in PCMANFM or when entering
umount /run/media/daniel/DTVP30
PCMANFM crashes.
That is not normal, because nothing else crashes on my Manjaro machine.
Yesterday, for testing, I did a new initialize on the stick on Kubuntu. And there it works normal.
But under Manjaro i3 I cannot execute any of the programs on the stick, no “init” and no “forgot”.
lsusb and lsblk show, filtered for the stick, the following:
lsusb:
Bus 002 Device 005: ID 0951:1505 Kingston Technology DTVaultPrivacy30
lsblk:
sr0 11:0 1 100M 0 rom /run/media/daniel/DTVP30
Manual can be found here
[http s://www.manualslib.com/manual/646920/Kingston-Technology-Datatraveler-Vault-Privacy.html?page=24#manual]
I installed dtvp-utils from AUR (seems those are the same as already on the stick), cd’d into /usr/bin/ where it was installed to, and executed sudo ./dtvt_login.
same problem
For testing, I took the apps in the linux32 path, but still no dtvp device detected.
Why not reformat with LUKS encryption? Is there something special about this proprietary software? I always delete stuff like that first thing on a new USB stick. This sounds like more trouble than it is worth.
yes, this literally copies the directory with the commands in it
from the stick to system directories
so that you don’t need to change directories into the stick and execute them from there
it’s just more convenient that way
…
i3 is just a window manager and some programs
Kubuntu is a full KDE desktop
much more is automated and made easily accessible with a click
I’d think what happens when you “decrypt” that encrypted part of the device
via your command
another device is made accessible
perhaps check lsblk -f
again after unlock whether that is so
I have never seen it in operation and don’t know what is supposed to happen.
You have - on KDE in Ubuntu.
i3 is a much more sparse environment - more manual work probably
@jrichard326
reformatting would make my investment in this stick overfluid, you understand
I don’t want to. Also I could imagine there is some special hardware within this device.
Short: I want to use this device its supposed way.
@Nachlese
I got your point on copying the tools into the system directories.
Well, I really like i3, it’s ultra fast and minimal. And I don’t have any problem working with it as long as anything is setup correctly. My scanner works, printer too, audio interface, external CD-ROM, normal USB sticks. I don’t want anything else.
There are always some issues, that makes it interesting
Nachlese, you are absolutely right: logging in on the stick makes a hidden device accessible.
I logged in into the stick on my tablet, Kubuntu, but that is not my main machine. You can see on the screenshot (wanted to upload but cannot find a function to do so) the lsblk -f output and the Partition Manager output. Now I could use it pretty comfortable like any normal stick. Everything is fine here, but still not on i3.
Screenshot lsblk -f shows the following: (sorry for the formatting, but wasn’t possible otherwise)
It is a device ~ 4 GB in capacity, which is accessible under the directory /media/SECURITY
there should be all your secret data
on a vfat filesystem named SECURITY
lsblk -f output is structured like a table
this is the heading: NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
and under each tag are the corresponding columns of the output
so that you know what is what
The name you chose for your file is different from my example - but the name doesn’t matter
as long as it ends with .conf
The name should probably be descriptive - it makes things easier for you. The machine doesn’t care.
You can even put a comment inside the file to remind you what it is there for.
start with a hash mark # and then put anything you like on that line - like:
# this is to load the sg kernel module so my kingston data traveler vault will work as intended
sg
… you may have the “solution” mark - I could not care less about anything else than this.
Just wanted to make you aware of what is actually important here and what is not.
probably something like: