Affects Version/s: None
Fix Version/s: EJBCA 184.108.40.206
Issue discovered during:Customer
Sprint:EJBCA Team Alice - 2020 w50
The customer mentiond to the attached code (Image.png) and explain that inside the SIM, EJBCA is storing the hash of the authorityRandomSource (i.e.: authorityRandom), however during the PEPSI generation, the authorityRandomSource itself is being used.
they refer to:
4.3. Random Number Generation
The RA generates a random number, R. A new R MUST be generated for
each SIM. The length of R MUST be the same as the length of the
output of the hash algorithm H. For example, if H is SHA-1, the
random number MUST be 160 bits.
based on this, the length of R must be the same as the length of the output of the hash algorithm H, but it seems like the length of the authorityRandomSource is always 16 bytes regardless of the hashing algorithm?
They want to validate the PEPSI or SIM value without knowing the real value of the authorityRandomSource?