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=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=466197
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
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=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 #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 #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 #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=432713
michaelk83 changed:
What|Removed |Added
CC||pos...@posteo.eu
--- Comment #3 from michaelk83
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=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=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=383896
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
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=458318
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
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=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=458085
michaelk83 changed:
What|Removed |Added
Version Fixed In|5.98|
Ever confirmed|0
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=458774
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=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=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=459289
michaelk83 changed:
What|Removed |Added
Blocks||458318
Referenced Bugs:
https://bugs.kde.org
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=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
See Also||https://bugs.kde.org/show_b
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=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=460730
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
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=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=313216
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #36 from
https://bugs.kde.org/show_bug.cgi?id=455041
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=234434
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=313216
michaelk83 changed:
What|Removed |Added
CC||m...@apache.org
--- Comment #37 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=458318
Bug ID: 458318
Summary: Deprecate `org.kde.kwalletd5` API
Product: frameworks-kwallet
Version: 5.97.0
Platform: unspecified
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=458309
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=458339
Bug ID: 458339
Summary: KWallet/Secret Service: potential conflict of
auto-start files (DBus etc) with other Secret Service
providers
Product: frameworks-kwallet
Version
https://bugs.kde.org/show_bug.cgi?id=458341
Bug ID: 458341
Summary: KWallet/SecretService: Support "plain" algorithm for
DBus communications
Product: frameworks-kwallet
Version: 5.97.0
Platform: unspecified
https://bugs.kde.org/show_bug.cgi?id=458341
--- Comment #1 from michaelk83 ---
That said, apps should generally use QtKeyChain or at least `libsecret` to
communicate with the the Secret Service API, so this is more a matter of
completeness and broader compatibility with existing apps.
--
You
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Resolution|DOWNSTREAM |DUPLICATE
--- Comment #9 from michaelk83 ---
(In
https://bugs.kde.org/show_bug.cgi?id=458069
michaelk83 changed:
What|Removed |Added
CC||nic.chris...@gmail.com
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #16 from michaelk83 ---
A possible solution might be to temporarily disable the Secret Service API
while unlocking the wallet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #17 from michaelk83 ---
(In reply to michaelk83 from comment #16)
> A possible solution might be to temporarily disable the Secret Service API
> while unlocking the wallet.
However, this can cause all sorts of race condition bugs
https://bugs.kde.org/show_bug.cgi?id=405627
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=350109
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=455041
michaelk83 changed:
What|Removed |Added
CC||xtem...@gmail.com
--- Comment #2 from michaelk83
https://bugs.kde.org/show_bug.cgi?id=398931
michaelk83 changed:
What|Removed |Added
CC||marc_altm...@live.de
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=453358
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=398931
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=403300
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=458063
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458069
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=313216
--- Comment #38 from michaelk83 ---
(In reply to Björn Bidar (Thaodan) from comment #34)
> (In reply to Alexander Schlarb from comment #33)
> > (In reply to Thaodan from comment #32)
> > > (In reply to Alexander Schlar
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #18 from michaelk83 ---
(In reply to michaelk83 from comment #17)
> (In reply to michaelk83 from comment #16)
> > A possible solution might be to temporarily disable the Secret Service API
> > while unlocking the wallet.
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #20 from michaelk83 ---
(In reply to michaelk83 from comment #18)
> A related question is where does GPG take its passphrase from when Secret
> Service is not running?
To answer my own question after re-reading the OP, the alter
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #24 from michaelk83 ---
(In reply to ioo+kde from comment #23)
> Does anyone know which version of KDE neon I would need to downgrade to to
> get this working again?
You'll need to specifically downgrade the KWallet packages to
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #26 from michaelk83 ---
(In reply to nic.chris...@gmail.com from comment #25)
> (In reply to michaelk83 from comment #20)
> > And two other experiments:
> > 1. After providing the passphrase, if you close the wallet,
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #27 from michaelk83 ---
(In reply to michaelk83 from comment #26)
> So short-circuiting `OpenSession` while waiting on GPG should fix this, IMO.
> It should return something like `InvalidMethodCall`, or simply `NotSupported`.
On f
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #28 from michaelk83 ---
(In reply to michaelk83 from comment #27)
> A more robust approach is to check if the key/passphrase are already loaded
> into gpg-agent,
> and if not, display a prompt and pre-load the passphrase before
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #30 from michaelk83 ---
(In reply to nic.chris...@gmail.com from comment #29)
> Unfortunately I'm already using pinentry-qt.
Hmm.. that is unfortunate.
> I see gpg has a "--pinentry-mode loopback" option, that red
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #32 from michaelk83 ---
(In reply to nic.chris...@gmail.com from comment #31)
> I can confirm that the process calling OpenSession is indeed pinentry-qt:
Thanks. Not surprising, but does make a full fix more difficult...
--
You
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #33 from michaelk83 ---
@nic.christin, one more thing to try:
https://man.archlinux.org/man/gpg-agent.1#no-allow-external-cache
> --no-allow-external-cache
>Tell Pinentry not to enable features which use an external cac
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #39 from michaelk83 ---
(In reply to Nicolas Fella from comment #38)
> we just needs to find one approach that works and stick with it
Option A (`no-allow-external-cache`) is the correct solution IMO, if you want
to use a GPG wallet w
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #40 from michaelk83 ---
(In reply to michaelk83 from comment #39)
> Option A (`no-allow-external-cache`) is the correct solution IMO
@Nicolas Fella, the patch would be something like the following (pseudo-code,
in backendpersisthandler.
https://bugs.kde.org/show_bug.cgi?id=458069
--- Comment #10 from michaelk83 ---
(In reply to ioo+kde from comment #9)
> Does this patch apply to all distributions or just archlinux?
Should apply to all, but it hasn't been released yet except on Arch. It should
be in the next KWallet Fr
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #42 from michaelk83 ---
(In reply to ioo+kde from comment #41)
> Will this solution allow users to again use a third party secret service
> agent along with kwallet again?
You don't need this patch to run a 3rd-party Sec
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #44 from michaelk83 ---
(In reply to Frank Kruger from comment #43)
> Recommendation A works fine for me - thanks for the "solution". However, I
> am really puzzled by the fact that the regression definitely introduced by
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #46 from michaelk83 ---
(In reply to Frank Kruger from comment #45)
> Appreciated, but your solution seems to be restricted to a fix when setting
> up a GPG wallet. What about current users?
The proposed fix should work the same wheth
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #49 from michaelk83 ---
(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 the key is not used automatically with
> the login
https://bugs.kde.org/show_bug.cgi?id=458639
Bug ID: 458639
Summary: KWallet: non-unique renames via old API cause items
loss in Secret Service API
Product: frameworks-kwallet
Version: 5.97.0
Platform: Neon Packages
https://bugs.kde.org/show_bug.cgi?id=458644
Bug ID: 458644
Summary: Make legacy KWallet entries searchable via Secret
Service API
Product: frameworks-kwallet
Version: 5.97.0
Platform: unspecified
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
Depends on||458644, 458085
Referenced Bugs:
https
https://bugs.kde.org/show_bug.cgi?id=458644
michaelk83 changed:
What|Removed |Added
Blocks||458318
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Blocks||458318
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=458318
--- Comment #1 from michaelk83 ---
(In reply to michaelk83 from comment #0)
> There is still one migration concern as discussed in
> https://invent.kde.org/frameworks/kwallet/-/merge_requests/11#note_428272
> and its replies, but that should
https://bugs.kde.org/show_bug.cgi?id=458644
--- Comment #1 from michaelk83 ---
(In reply to michaelk83 from comment #0)
> Expose a read-only virtual attribute `org.kde.kwalletd5:label` for all legacy
> items.
Maybe make it non-virtual, so that it's discovera
https://bugs.kde.org/show_bug.cgi?id=458737
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=334646
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458774
Bug ID: 458774
Summary: KWallet/Secret Service: `default` alias should default
to the 1st collection
Product: frameworks-kwallet
Version: 5.97.0
Platform: Neon Packages
https://bugs.kde.org/show_bug.cgi?id=458776
Bug ID: 458776
Summary: Changing the default wallet does not update Secret
Service `default` alias (unless `kwalletd5` is
restarted).
Product: kwalletmanager
Version: 22
https://bugs.kde.org/show_bug.cgi?id=458774
--- Comment #1 from michaelk83 ---
Related to Bug 458776.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458737
michaelk83 changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=263174
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=457807
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=443571
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=451039
michaelk83 changed:
What|Removed |Added
CC||pingo-po...@hotmail.fr
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=457807
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=451039
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=448357
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=450004
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=403432
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=399232
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #5 from michaelk83 ---
(In reply to michaelk83 from comment #4)
> What you want here is a separate daemon that exposes the pass backend
> through the Secret Service API.
Actually, this already exists: https://github.com/md
1 - 100 of 219 matches
Mail list logo
