https://bugs.kde.org/show_bug.cgi?id=482819
Fabian Vogt changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=482819
Matt Fagnani changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=482819
Fabian Vogt changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #26 from Matt Fagnani ---
I switched /etc/pki/tls/openssl.cnf back to the old config and rebooted. I
closed the wallet and ran killall kwalletd6 twice. I ran ltrace -fCe
'DH_*+OSSL_*' kwalletd6 I opened the wallet. I ran protonvpn-app which
https://bugs.kde.org/show_bug.cgi?id=482819
Matt Fagnani changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #25 from Matt Fagnani ---
Created attachment 167997
--> https://bugs.kde.org/attachment.cgi?id=167997=edit
ltrace output on kwalletd6 when running Proton VPN GUI twice
I ran ltrace -fCe 'DH_*+OSSL_*' kwalletd6 with the newer default
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #24 from Matt Fagnani ---
Created attachment 167996
--> https://bugs.kde.org/attachment.cgi?id=167996=edit
Older openssl config file which the problem happened with
Thanks. I created an empty file empty.cnf. I closed the wallet in
https://bugs.kde.org/show_bug.cgi?id=482819
Fabian Vogt changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #22 from Matt Fagnani ---
I think I've found why the problem happened on my system but not yours. The
openssl config file /etc/pki/tls/openssl.cnf was last modified in September
2020 at the time I ran a SCAP Workbench remediation script
https://bugs.kde.org/show_bug.cgi?id=482819
Matt Fagnani changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=482819
Fabian Vogt changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #19 from Matt Fagnani ---
I tried setting the legacy fedora crypto policy which allows DH keys >= 1024
bits with sudo update-crypto-policies --set LEGACY and rebooting but the
problem still happened. I also built kwallet with const auto
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #18 from Albert Astals Cid ---
(In reply to Matt Fagnani from comment #17)
> In KWalletFreedesktopService::createSessionAlgorithmDhAes at
> /usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/
>
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #17 from Matt Fagnani ---
In KWalletFreedesktopService::createSessionAlgorithmDhAes at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:415
there is const auto dlGroup =
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #16 from Matt Fagnani ---
Yes, my system is fully updated with the updates-testing repo enabled. I ran
those steps with the qca 2.3.8 build with your patch which gave me the
following output. privateKey.context() appeared to have a non-null
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #15 from Albert Astals Cid ---
This is super curious as why i can't reproduce this.
Just to confirm, you are fully
dnf upgrade
right?
Can you try compiling this simple program?
You may need to install qca-qt6-devel qt6-qtbase-devel
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #14 from Matt Fagnani ---
I ran the steps like in comment 9 with the qca 2.3.8 build with the patch, but
instead with
export QT_LOGGING_RULES="*.debug=true"
kwalletd6 &
The end of the output appeared to show that the first line added by
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #13 from Matt Fagnani ---
I built qca 2.3.8 with your patch added. I reproduced the crash first without
using valgrind. The crash happened on the line with static_cast(context())->key() Since context() looked to be run with out a pointer to
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #12 from Albert Astals Cid ---
Once you compile with those changes do the same valgrind thing.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #11 from Albert Astals Cid ---
Can you add these changes?
https://pastebin.com/raw/ryCpqQyb
I'm trying to figure out which of the 4 pointers involved in that line is a
null pointer
I'm assuming you know what that file means, if not tell
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #10 from Matt Fagnani ---
My kwallet is opened automatically when I log in to Plasma with the same
password. You could try installing GNOME 46.0 in your Fedora 40 installation as
I have in case there's something from GNOME that's involved
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #9 from Albert Astals Cid ---
I've been finally been able to install Fedora 40 and can't still reproduce the
problem :/
Can you do this (with the version that crashes)
Open a terminal
Start kwalletmanager5 and press the close wallet
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #8 from Matt Fagnani ---
I bisected this problem with qca from 2.3.7 to 2.3.8. The following first bad
commit involved loading legacy openssl providers.
14eb1ae746c3c75afaef02b487ac65b3de85ad15 is the first bad commit
commit
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #7 from Matt Fagnani ---
In frame 1 in KWalletFreedesktopService::createSessionAlgorithmDhAes,
privateKey and publicKey had null d pointers and clientPublicKey had d = 0x75.
Those keys were generated by qca functions.
(gdb) frame 1
#1
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #6 from Matt Fagnani ---
I used kwalletmanager to export my wallet in encrypted form, then I deleted my
wallet. I created a new wallet when I started Proton VPN GUI and logged in.
kwalletd6 crashed each time when logging in to the Proton
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #5 from Matt Fagnani ---
(In reply to Albert Astals Cid from comment #4)
> unfortunately that image you linked seems to have a broken installer
> https://i.imgur.com/yZXIoG4.png
That problem with the installer might be because you appeared
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #4 from Albert Astals Cid ---
unfortunately that image you linked seems to have a broken installer
https://i.imgur.com/yZXIoG4.png
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #3 from Matt Fagnani ---
You can download the Fedora 40 KDE Plasma live beta
Fedora-KDE-Live-x86_64-40_Beta-1.10.iso from
https://koji.fedoraproject.org/koji/buildinfo?buildID=2423953 You can boot that
in a QEMU/KVM VM though I haven't
https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #2 from Albert Astals Cid ---
Cannot reproduce on my system
I tried following your steps but
1. Boot a Fedora 40 KDE Plasma installation updated to 2024-3-8 with the
updates-testing repo enabled
got me blocked on how to get a Fedora 40
https://bugs.kde.org/show_bug.cgi?id=482819
Yaroslav Sidlovsky changed:
What|Removed |Added
See Also||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=482819
Matt Fagnani changed:
What|Removed |Added
Product|frameworks-kwallet |qca
Component|general
31 matches
Mail list logo
