Same serial number for two different certs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xca (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello,
I have a problem with last version of xca installed from repo in yakkety (1.3.2-1 amd64).
Sometimes we have some 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.
Yakkety is no longer supported. Please test in a current supported release and see if this issue still happens (please also test with the latest available release if possible). If the issue still exists, please make a comment as such; otherwise this bug will be closed in 60 days as I am marking it "Incomplete"