Concurrent database access not supported
Brought to you by:
chris2511
Menu
▾
▴
1 Attachments
#118 Concurrent database access not supported
Hello,
I have a problem with last version of xca installed in ubuntu from repo in yakkety (1.3.2-1 amd64).
Sometimes we have different certificates with same serial number.
This is how to reproduce :
database.xdb (already initialised with a CA cert) is located in a file share (debian)
Computer A do a "mount -t cifs //server/share /mnt
Computer B do the same mount
Computer A (yakkety with xca 1.3.2-1) launch xca and open /mnt/database.xdb
Computer B (yakkety with xca 1.3.2-1) launch xca and open /mnt/database.xdb
So the same database is opened from two computer at same time.
Computer A create a new cert (signed by CA)
Computer B create a new cert (signed by CA)
Computer A close database.xdb
*Computer B close database.xdb
When computer A or B reopen database.xdb serial number is the same for certs created by computer A and computer B.
I have joined a screenshot to show this.
So my question is : Is there a problem with concurrent access with the database ?
If yes , is it possible to create a "lock" in the database in order to prevent this issue (maybe as "vim" warns when opening an already opened file) ?
Thank you.
Currently XCA does not support conncurrent access reliably.
I will change the database format with version 2.0 to a SQL API.
SQLite supports concurrent access.
For multi user access over network mysql or postgres should be used then