https://bugs.kde.org/show_bug.cgi?id=376318
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #19 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=376318
postix changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #17 from Fuchs ---
I'd say the main problem here is that it does not only break for special use
cases, but for some people (e.g. me) for the very standard usecase of ssh.
So it's completely unusable for me right now.
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #16 from Christoph Feck ---
Well, we had developers looking at the patches that broke your use case, so I
guess the chances are high that someone understands your position and accepts a
patch to restore that.
In any case, if
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #15 from Moritz Bunkus ---
I get that, believe me. However, ksshaskpass is a very convenient tool for
storing & retrieving passwords securely without having to write a whole script
around dbus calls. Excellent for
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #14 from Christoph Feck ---
I do not know if we have a maintainer for ksshaskpass, it looks like someone
else (i.e. not the developer) imported the code.
Reading the commit log of 9dbabcb38862c1590503169be3ae7806e6673dba I
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #13 from Fuchs ---
(In reply to Moritz Bunkus from comment #12)
> [...]
>
> In each case I simply execute ksshaskpass with a custom prompt, e.g.
> "ksshaskpass 'IMAP password'". I've modified my scripts and
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #12 from Moritz Bunkus ---
Sorry for spamming, but I think I should explain my use case here. I'm using
ksshaskpass not just with ssh-add via SSH_ASKPASS, but also for other purposes,
including:
* letting mutt retrieve
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #11 from Moritz Bunkus ---
More information. Running the compiled ksshaskpass from the command line shows
the following debug information:
> ksshaskpass: Unable to extract keyFile from phrase "wuff"
"wuff" is the sole
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #10 from Moritz Bunkus ---
I've just bisected the problem. The first bad commit is
9dbabcb38862c1590503169be3ae7806e6673dba.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376318
andreas.sturmlech...@gmail.com changed:
What|Removed |Added
CC||andreas.sturmlechner@gmail.
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #9 from Fuchs ---
(In reply to Moritz Bunkus from comment #8)
> Still completely useless.
And still completeley broken and useless in 5.9.3, I think I'll ask gentoo to
mask it as it is apparently broken.
And no, it
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #8 from Moritz Bunkus ---
I've tried the following with 5.9.2:
[0 mbunkus@chai-latte ~/tmp/askpass] export
QT_LOGGING_RULES='ksshaskpass.*=true'
[0 mbunkus@chai-latte ~/tmp/askpass] ksshaskpass wuff
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #7 from Christoph Feck ---
Your distribution might also have configured Qt to redirect any logging to the
syslog daemon instead of to the Konsole. In that case, please ask in a forum of
your distribution how to search for
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #6 from Christoph Feck ---
ksshaskpass uses the new Qt logging. To get the debug output, please add
ksshaskpass.*=true to your QT_LOGGING_RULES as described at
http://doc.qt.io/qt-5/qloggingcategory.html
Either put it into
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #5 from Moritz Bunkus ---
I can confirm that for me 5.9.2 doesn't save anything at all. Reverting to
5.9.0 fixes the problem. ksshaskpass itself doesn't output anything useful.
Neither does the wallet subsystem, even if I
https://bugs.kde.org/show_bug.cgi?id=376318
Moritz Bunkus changed:
What|Removed |Added
CC||mor...@bunkus.org
--
You
https://bugs.kde.org/show_bug.cgi?id=376318
Fuchs changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #3 from Fuchs ---
Hi, seems to work so far with 5.9.3, otherwise I shall re-open.
Kind regards,
Christian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376318
--- Comment #2 from Christoph Feck ---
We could not verify if the issue from bug 376228 is indeed a duplicate.
If your issue is not fixed with Plasma 5.9.3, please add a comment, ideally
with the debug output of the ksshaskpass program.
https://bugs.kde.org/show_bug.cgi?id=376318
Christoph Feck changed:
What|Removed |Added
Resolution|--- |DUPLICATE
22 matches
Mail list logo