Your message dated Thu, 4 Jul 2019 17:08:50 +0000 (UTC)
with message-id <[email protected]>
and subject line Re: Bug#931423: kwalletcli: How can the content of Maps entry 
can be read with kwalletcli ?
has caused the Debian Bug report #931423,
regarding kwalletcli: How can the content of Maps entry can be read with 
kwalletcli ?
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 [email protected]
immediately.)


-- 
931423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931423
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kwalletcli
Version: 3.02-1
Severity: normal
Tags: upstream

Dear Maintainer,

I've setup Maps entries using kwalletmanager. Unfortunately, I cannot
figure out how to retrieve the content of Maps using a kwalletcli.

For instace, kwalletmanager show entries like:

\/ Passwords (26)
  > Passwords
  \/ Maps
     stuff

stuff is a Name-Value Map containing foo and bar Keys.

I've tried:
$ kwalletcli -f Passwords -e stuff
[no output]
$ kwalletcli -f Passwords -e stuff/user
entry does not exists
$ kwalletcli -f Passwords/stuff -e user
folder does not exists

Is there a way to get the value of "user" Key stored in "stuff" Maps
in "Passwords folder ?

If yes, shoudln't that be documentated ?

All the best


-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kwalletcli depends on:
ii  libc6              2.28-10
ii  libgcc1            1:8.3.0-7
ii  libkf5coreaddons5  5.54.0-1
ii  libkf5i18n5        5.54.0-1
ii  libkf5wallet-bin   5.54.0-1
ii  libkf5wallet5      5.54.0-1
ii  libqt5core5a       5.11.3+dfsg1-2
ii  libqt5widgets5     5.11.3+dfsg1-2
ii  libstdc++6         8.3.0-7
ii  mksh               57-1

Versions of packages kwalletcli recommends:
ii  gnupg-agent                     2.2.13-2
ii  gpg-agent [gnupg-agent]         2.2.13-2
ii  kwalletmanager                  4:18.04.1-1
ii  openssh-client                  1:7.9p1-10
ii  pinentry-curses [pinentry]      1.1.0-2
ii  pinentry-gnome3 [pinentry-x11]  1.1.0-2
ii  pinentry-qt [pinentry-x11]      1.1.0-2
ii  pinentry-qt4                    1.1.0-2

kwalletcli suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Dominique,

>I've setup Maps entries using kwalletmanager. Unfortunately, I cannot
>figure out how to retrieve the content of Maps using a kwalletcli.

kwalletcli is normally used to retrieve entries it wrote itself.
In particular, it only has support for password entries.

>If yes, shoudln't that be documentated ?

It’s documented:

DESCRIPTION
     The kwalletcli utility is a command line interface to KWallet.  It will
     only work if KDE is running (DCOP) and reachable (via X11).  kwalletcli
     can be used to get password entries from the default Wallet, or to write
     them there.

It says “password entries” there.

I’ve got no understanding of all the possible data structures
in all possible versions of the KDE wallet (3, 4, 5), plus
keeping it simple makes kwalletcli extensible (e.g. someone
once intended to write a gnome-keyring and apple-keychain
binding for it, to keep the same CLI UI).

I’m sorry that this is not the tool that will help you further.
I also, occasionally, get asked to dump the whole wallet, but
this all is out of scope and you need specialised, KDE version-
matching, utilities for that.

Good luck,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜<thkoehler:#grml> also warum machen die xorg Jungs eigentlich alles
kaputt? :)    15:49⎜<novoid:#grml> thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?      -- ~/.Xmodmap wonders…

--- End Message ---

Reply via email to