I'd sad we keep it as it is now (unless we see a regression). The real and only correct solution is the use of a daemon to serialize access.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
Still, there is a fundamental problem with keydb locking.
- It only assures no-data-corruption.
- When a process doing write access, another process reading the resource may encounter a problem (inconsistent data read), since data could be changed while accessing.
- Currently, write access may occur with keybox compress, this means that users are not safe to invoke multiple gpg/gpgsm simultaneously (to be sure).
- It would be: only keybox compress when users explicitly ask.
- We could introduce a lock to read access... BUT naively adding a lock (both for read and write or read-multiple-write-one) results possible deadlock in gpgsm
- in gpgsm, gpgsm_walk_cert_chain and gpgsm_validate_chain access the resource of keydb in a way of:
- While it has a handle kh, by find_up routine, it may call keydb_store_cert by callback routine; The callback does write access to the resource opening another handle.
- Currently, it works because of no lock for read access and keydb_store_cert appends data at the end.
- in gpgsm, gpgsm_walk_cert_chain and gpgsm_validate_chain access the resource of keydb in a way of:
- Currently, write access may occur with keybox compress, this means that users are not safe to invoke multiple gpg/gpgsm simultaneously (to be sure).
All changes in gniibe/t7855 are pushed into master.
Yesterday
Backported for VSD 3.4 since this is clearly a regression introduced with T7350 and the fix is zero risk.
Fixed. The check box has been removed from the "S/MIME Validation" tab.
Fixed and backported for VSD 3.4
That might be related to T2196 which has been hopefully fixed in 2.2.50 and also in the next 2.6. Closing this task.
That might be related to T2196 which has been hopefully fixed in 2.2.50 and also in the next 2.6. Closing this task.
Might there be a relation to T7842? But I would have thought that then all signed messages would be unaffected.
I applied it to the 2.4 branch but please do not continue to translate for 2.4. 2.6 (master) is the new target.
Implemented but not tested at all.
This issue should be fixed in 2.6, too.
Pushed the change to gnupg master: rG61ff3759e827: common,dirmngr:w32: Fix for semi-hosted environment.
In libgpg-error, I pushed thread-safe version : rE0313b660f8bd: w32: Don't convert slash->backslash when it's under Wine.
I'm going to push similar code to gnupg master.
Mon, Oct 20
I merged Tobias's MR
We need to check what the current status here is. This has been in the 5.0 Betas for a while, so testing with 5.0-Beta369 will work
Fixed and backported for VSD 3.4