https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Blocks|458318 |
See Also
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #70 from michaelk83 ---
> if pinentry always uses the same lookup attributes, KWallet could potentially
> detect those
I forgot that the deadlock is in the `OpenSession()` call, so this is not
possible.
I think that handling the
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #69 from michaelk83 ---
> as long as pinentry makes the request via the Secret Service API, KWallet has
> no way to know that it's its own password that is being requested here.
On 2nd thought, if pinentry always uses the
https://bugs.kde.org/show_bug.cgi?id=156547
--- Comment #11 from michaelk83 ---
As discussed in the MR (
https://invent.kde.org/utilities/kwalletmanager/-/merge_requests/46#note_1146725
), there are two parts to this:
1. On KWallet's side, it absolutely *should* tell Klipper that "
https://bugs.kde.org/show_bug.cgi?id=458639
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=491280
michaelk83 changed:
What|Removed |Added
CC||a...@cryptomilk.org
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=484045
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=491280
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=179678
--- Comment #121 from michaelk83 ---
Is this considered resolved with KIO Admin
(https://invent.kde.org/system/kio-admin)?
The latest merge request for this has been closed:
https://invent.kde.org/frameworks/kio/-/merge_requests/1004#note_1070765
https://bugs.kde.org/show_bug.cgi?id=324254
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=179678
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=489021
--- Comment #1 from michaelk83 ---
@Nate Graham, although the steps to reproduce are with KDE Connect, the bug is
experienced in relation to xdg-desktop-portal-kde, unrelated to KDE Connect or
to Android. See for example
https://github.com
https://bugs.kde.org/show_bug.cgi?id=489021
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=468538
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=467534
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
See Also
https://bugs.kde.org/show_bug.cgi?id=451039
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=467533
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=432713
michaelk83 changed:
What|Removed |Added
CC||pos...@posteo.eu
--- Comment #3 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #66 from michaelk83 ---
(In reply to Thiago Macieira from comment #65)
> In any case, this doesn't prevent a race condition anyway. How about we try
> to fix it the right way first?
I think handling the Assuan protocol is our b
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #64 from michaelk83 ---
(In reply to Thiago Macieira from comment #63)
> Does it support setting ephemeral settings not saved to disk? I didn't see
> that in the documentation.
>
> Otherwise, you're just asking
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #62 from michaelk83 ---
(In reply to Thiago Macieira from comment #61)
> A proper implementation would realise that
> the request for GPG to open the wallet is still pending and queue the
> request to be answered when the wallet g
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #60 from michaelk83 ---
(In reply to Thiago Macieira from comment #59)
> But the fact is that if the query was asynchronous, then pinentry would have
> got its answer instead of timing out, and then would have prompted the user
>
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #58 from michaelk83 ---
(In reply to Thiago Macieira from comment #57)
@Thiago, the issue is bigger than just synchronous vs asynchronous. The issue
is that if you use a GPG wallet, with Secret Service provided by KWallet, and
while
https://bugs.kde.org/show_bug.cgi?id=466197
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=466494
--- Comment #4 from michaelk83 ---
(In reply to Piotr Mierzwinski from comment #3)
> Yes, but If in my PC will appear malware/ malicious software
> then will be able to get the password. Am I right?
It's generally the same with other passwo
https://bugs.kde.org/show_bug.cgi?id=466494
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=432810
michaelk83 changed:
What|Removed |Added
Summary|exiting keepassxc after it |exiting some apps sometimes
https://bugs.kde.org/show_bug.cgi?id=463148
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=432810
michaelk83 changed:
What|Removed |Added
CC||andihartm...@freenet.de
--- Comment #14 from
https://bugs.kde.org/show_bug.cgi?id=455041
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=399232
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #13 from michaelk83 ---
(In reply to Bernd Steinhauser from comment #11)
For KeePass, there is a standard file format (`.kdbx`) that multiple
applications can work with, and indeed there are many KeePass variations that
all work with this
https://bugs.kde.org/show_bug.cgi?id=462477
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=462333
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=462244
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=459287
michaelk83 changed:
What|Removed |Added
CC||k...@lecris.me
--- Comment #1 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=461653
--- Comment #8 from michaelk83 ---
(In reply to Volker Kuhlmann from comment #7)
> I don't understand why testing this from a text console has any merit. A
> Linux text console (e.g. ctrl-alt-f3) can only render characters, not
> graphi
https://bugs.kde.org/show_bug.cgi?id=461653
--- Comment #6 from michaelk83 ---
(In reply to Volker Kuhlmann from comment #5)
> When I quit kmail, stop akonadi, pkill -e kwallet, and then start kmail from
> the konsole shell, it behaves as expected and as if started from the
> launche
https://bugs.kde.org/show_bug.cgi?id=461653
--- Comment #4 from michaelk83 ---
That is some useful info, thank you. Since it's 5.90, there is no Secret
Service code in KWallet in that version, and kmail should not be asking for
Secret Service either. It also shouldn't matter whet
https://bugs.kde.org/show_bug.cgi?id=461728
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=461653
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=460730
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458341
--- Comment #5 from michaelk83 ---
(In reply to tgpski from comment #3)
> After upgrading KWallet today, I was locked out of my company VPN due to the
> plain algorithm
> being used in wallet communications between the VPN frontend and th
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=313216
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
Depends on||459289
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=459289
michaelk83 changed:
What|Removed |Added
Blocks||458318
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=459289
Bug ID: 459289
Summary: KWallet/Secret Service: items lost if `kwalletd5`
dies.
Classification: Unclassified
Product: frameworks-kwallet
Version: 5.98.0
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=459287
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458776
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=459287
Bug ID: 459287
Summary: KWallet/Secret Service: inconsistent locked/unlocked
state of wallets.
Classification: Unclassified
Product: frameworks-kwallet
Version: 5.98.0
Platfor
https://bugs.kde.org/show_bug.cgi?id=458774
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458776
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Version Fixed In|5.98|
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=459039
--- Comment #5 from michaelk83 ---
(In reply to michaelk83 from comment #2)
> As for your concerns with KeePassXC, you can try raising those with
> KeePassXC's developers (but do search for existing issues first).
What I meant was if yo
https://bugs.kde.org/show_bug.cgi?id=459039
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
See Also
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #50 from michaelk83 ---
(In reply to michaelk83 from comment #49)
> (In reply to pipapo from comment #48)
> > Here on kde neon option A is working in the sense that a dialog is asking
> > for the passphrase immediately. But
https://bugs.kde.org/show_bug.cgi?id=383896
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458644
--- Comment #2 from michaelk83 ---
Better/additional STEPS TO REPRODUCE, assuming the proposed
`org.kde.kwalletd5:label` behavior:
1. Install KWallet 5.97.0 and enable Secret Service integration.
2. Create some entries via the old `org.kde.kwalletd5
https://bugs.kde.org/show_bug.cgi?id=458318
--- Comment #3 from michaelk83 ---
Related: https://github.com/frankosterfeld/qtkeychain/issues/220
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=172523
--- Comment #6 from michaelk83 ---
Oops, wrong link. Should be: Bug 228308 comment 14.
Sorry for the multi-post noise.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=172523
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=172523
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=228308
--- Comment #14 from michaelk83 ---
That said, and especially assuming most apps would use the default collection
anyway, the backend can choose to ignore the selected collection, and re-route
`CreateItem()` requests as it sees fit. That somewhat
https://bugs.kde.org/show_bug.cgi?id=228308
--- Comment #13 from michaelk83 ---
(In reply to michaelk83 from comment #12)
> Furthermore, the plan is to migrate the KDE apps to QtKeyChain, which AFAIK
> just uses the default collection and doesn't provide an API for specifying
> wh
https://bugs.kde.org/show_bug.cgi?id=334646
--- Comment #7 from michaelk83 ---
(In reply to al F from comment #6)
> There is a bug report regarding this at
> https://github.com/bitwarden/clients/issues/1047
As noted in
https://github.com/bitwarden/clients/issues/1047#issuecomment-1097
https://bugs.kde.org/show_bug.cgi?id=147873
--- Comment #23 from michaelk83 ---
(In reply to kilrae from comment #22)
> I have a little experience with Linux. But I couldn’t pull off any of these
> “trivial exploits” without some time to think about it. However, I can click
> “Show
https://bugs.kde.org/show_bug.cgi?id=312325
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458318
--- Comment #2 from michaelk83 ---
An interesting thought has occurred to me in Bug 399232: if `org.kde.kwalletd5`
is discontinued without porting KWalletManager to Secret Service, then KWallet
daemon would be left without a KDE-native front-end (or
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #10 from michaelk83 ---
(In reply to michaelk83 from comment #9)
Btw, if KDE devs decide to port KWalletManager to Secret Service before
discontinuing it, *then* it can also act as a front-end for pass, again via the
likes of
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #9 from michaelk83 ---
(In reply to Borden from comment #8)
At least at the moment, KWallet and pass are two completely separate systems.
They can each present the same Secret Service API to client apps, so the apps
don't care which o
https://bugs.kde.org/show_bug.cgi?id=433485
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #7 from michaelk83 ---
(In reply to Michi from comment #6)
The main goal of this task, as I understand, is to have KDE apps access
passwords from the pass backend. The proposed solution was to integrate pass
with KWallet, and then have the
https://bugs.kde.org/show_bug.cgi?id=141267
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=131430
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
See Also
https://bugs.kde.org/show_bug.cgi?id=432713
michaelk83 changed:
What|Removed |Added
CC||knec...@gmail.com
--- Comment #2 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=171616
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=228308
--- Comment #12 from michaelk83 ---
(In reply to michaelk83 from comment #9)
> Related to Bug 451039 comment 2.
On 2nd thought, with the Secret Secret API (KWallet Framework 5.97.0+), it's up
to each application to specify which collection (wa
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
CC||bugzi...@kerridis.de
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=136094
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC
https://bugs.kde.org/show_bug.cgi?id=228308
michaelk83 changed:
What|Removed |Added
Summary|Applications only check |Control which application
https://bugs.kde.org/show_bug.cgi?id=172523
michaelk83 changed:
What|Removed |Added
CC||mh+kde-b...@zugschlus.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=216824
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=216658
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=451039
michaelk83 changed:
What|Removed |Added
CC||kde-2011...@dotancohen.com
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=180504
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=451039
michaelk83 changed:
What|Removed |Added
CC||le...@confuego.org
--- Comment #6 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=444252
michaelk83 changed:
What|Removed |Added
CC||e...@shadowsun.net
--- Comment #5 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=281237
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=444252
michaelk83 changed:
What|Removed |Added
CC||rsimmo...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=276634
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC
https://bugs.kde.org/show_bug.cgi?id=204238
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=141267
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=384935
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=141267
--- Comment #19 from michaelk83 ---
*** Bug 335881 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 222 matches
Mail list logo
