@SMT_Solvers@jonathandata1@Equifax The https://t.co/TndR0QyTkl web interface truncates large result sets for performance reasons, and I haven't yet found a way to efficiently sort by certificate expiry date before truncating.
Try https://t.co/hx65OZTJof
@rmhrisk https://t.co/TndR0QyTkl has caught up on (re)counting issuances, but has not yet caught up on (re)counting expirations. See https://t.co/y6burmYmHC
@julianor @ic0nz1 https://t.co/TndR0QyTkl has fallen significantly behind on ingesting new log entries (see https://t.co/B2xdXWsDlm). However, I was finally able to deploy some performance improvements this week, and I'm hoping the ingestion backlog will disappear within the next month or so.
@eabalea@dfaranha@julianor@BenLaurie https://t.co/TndR0QyTkl is currently way behind on ingesting log entries, unfortunately (see https://t.co/B2xdXWsDlm). Performance improvements coming soon.
@ericlaw Please try it now, using either the default "q=" search type (which is what the https://t.co/HzS6sKj2hy front page search interface uses) or the more specific "cnlspkisha256=" search type.
e.g., https://t.co/UOtrwToT9P
Implemented by https://t.co/2HplqJZVLn
@ericlaw Is the prefix always "sha256/", or are there other options?
Is the remainder of the string a base64-encoded certificate thumbprint? Or something else?
@Martijn___@jschauma The certificate_identity table is a historical artifact from the original https://t.co/TndR0QQubT database, which had int32 certificate IDs. As part of rebuilding the database to have int64 IDs, I switched to using postgres's Full Text Search instead.
@rmhrisk Actually, tbh I'd always assumed timstamp.dll was so named due to legacy DOS filename length restrictions (8 chars, then 3 for the extension).
Turns out the truth is stranger. 🙂