- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 12 2024
Fixed in 1.51, by introducing gpgrt_spawn_actions_set_env_rev, which assumes utf-8 encoding.
Fixed in 1.51.
Fixed in 1.51.
Nov 11 2024
Hmm, calling QProcess::setStandardInputFile(QProcess::nullDevice()) before start() may be even better than calling closeWriteChannel() after start().
On the Cli, gpg does not give an error but an info message informing that the subkey already exists so there is no error message for Kleopatra to act on.
Fix for the crash https://invent.kde.org/pim/kleopatra/-/merge_requests/318
It works in Gpg4win-Beta-75 to add the ADSK to more than one Key.
The QProcesses we start should be configured with closed stdin so that the started process don't hang waiting for input, e.g. by calling closeWriteChannel() immediately after start(). Or by calling start() with QIODeviceBase::ReadOnly, but, sadly, the documentation of QProcess doesn't document what effect that has.
Gpg4win-Beta-75: This is in principle ok. Even adding further commands to
C:\Program Files (x86)\Gpg4win\etc\xdg\kleopatradebugcommandsrc works:
@ebo @ikloecker Let me explain my thoughts. If you have time, please help me doing some tests in your environment.
Nov 10 2024
Nov 9 2024
This shell script running gpg-connect-agent should run successfully: