The new gpgol with support for web mailers.
Details
Yesterday
the web client received some changes in the meantime and behaves more verbose regarding connections to a native client. we should check this again, especially if GpgOL/Web is supposed to be used for different outöook accounts at the same time.
in the meantime we decided it's not always desirable to have the process autostarted. therefore the current default (manual start) is considered ok, but if possible a configuration option should be implemented, so users can activate autostart if they find it useful.
Tue, Jul 15
Thu, Jul 10
Jul 3 2025
Jun 25 2025
Should current behavior of 'starting with no arguments' be preserved? or should we add a --generate or --doit or similar ?
Jun 23 2025
A bit tricky to fix unfortunately, making the window active is not really possible on Windows. See https://doc.qt.io/qt-6/qwidget.html#activateWindow but there seems to be some tricks one can use: https://forum.qt.io/topic/1939/activatewindow-does-not-send-window-to-front/11?_=1750663659477
Jun 16 2025
The question is whether any part of Qt/KF6/MTP forks another process and does not do it correctly. For example it is required that the child figures out the fds to close and then closes them and does not rely here on the parent.
Jun 13 2025
For each part that needs to be reencrypted I create a QGpgME Encrypt Job
Do you start other process while this context is in use? If you do a fork, you need to make sure that all file descriptors are closed. How is that done?
Interesing part of the logs: