Cascade fails at a certain key
There are cases when cascade fails to correct a key. See below...
#1 Updated by Oliver Maurhart about 2 years ago
Attached is a tarball with such case.
There is just one key stored in the files
After running the
./test-bb84-cascade additional key files are created. Examining the corrected keys via the
qkd-key-compare tool reveals:
$ qkd-key-compare corrected-keys.* comparing keys... file 1: corrected-keys.alice file 2: corrected-keys.bob key bits disclosed bits error rate state crc encoding - key bits disclosed bits error rate state crc encoding - diff. bits diff. rate 0000000017 00018440 00000199 0.0009 corrected 3e2e8809 shared secret bits - 0000000017 00018440 00000199 0.0009 corrected 15229a50 shared secret bits - 0000000542 0.0294
The log of (e.g. alice) reads:
working on incoming keys started synchronizing keys... key-PULL [000000000002179ms] id: 0000000017 bits: 0000018440 err: 0.0000 dis: 0000000000 crc: 3e2e8809 state: sifted synchronizing keys... key #17 is present at peer - picked cascade done: errors = 16/18440, error rate = 0.000867679, disclosed = 199/18440, efficiency = 1.07103 key-PUSH [000000000002244ms] id: 0000000017 bits: 0000018440 err: 0.0009 dis: 0000000199 crc: 3e2e8809 state: corrected dur: 000065468705 ns (000065 ms)
So cascade fails to correct the key. --> why?