-
Notifications
You must be signed in to change notification settings - Fork 13
Description
Describe the bug
The auto generated ids for sec-certs urls pointing to specific certified product are not always persistent in time (https://sec-certs.org/cc/**6207e27699db6695**/). We do have at least two cases of id that changed in time - for example https://sec-certs.org/cc/6207e27699db6695/ vs. https://sec-certs.org/cc/56ef6c45d7eab7ee/ . The ID is generated from presumably static parameters of certificates, but it changed anyway. If these changes, we are loosing permalink people may have in their papers or watched certificates (email/RSS/Compare). We shall at least detect and add redirect. (and also investigate what is changing)
To Reproduce
Steps to reproduce the behavior:
- Find some certificate (e.g., Strong Customer Authentication for Apple Pay on Apple Watch with S8 running watchOS 9.4(watchOS 9.4 (build 20T253)) ( ANSSI-CC-2023/60) https://sec-certs.org/cc/56ef6c45d7eab7ee/)
- Wait some time
- Check again based on url - if bug demonstrates itself, you will get Not Found
- Search for certified device name again => observe different url https://sec-certs.org/cc/6207e27699db6695/
Expected behavior
Once indexed and inserted to database, the url static string shall stay same.
If change is anyway detected, notify admins and add automatic redirect to new url.
Desktop (please complete the following information):
- web at sec-certs.org (end of 2023/begin 2024 -> October 2024)
Additional context
Known examples
NXP JCOP 4 P71 https://sec-certs.org/cc/2a45531c2dbd1ab8/ -> https://sec-certs.org/cc/f29f88756682e034/
Strong Customer Authentication for Apple Pay on Apple Watch with S8 running watchOS 9.4(watchOS 9.4 (build 20T253)) ( ANSSI-CC-2023/60) https://sec-certs.org/cc/56ef6c45d7eab7ee/ -> https://sec-certs.org/cc/6207e27699db6695/