← Byte Computer S.A. cases
Bugzilla #2015563 Incident

Byte Computer S.A.: Missing CCADB contact information (CA Email Alias 1/2)

RESOLVED WONTFIX Byte Computer S.A.
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

This case concerns Byte Computer S.A.’s CCADB entry missing required contact information. The reporter stated that Byte Computer had not updated required CCADB contact fields after being notified on 2026-01-23, and that “CA Email Alias 1” and “CA Email Alias 2” were empty. The reporter cited CCADB Policy Section 2 – Contact Information Disclosures, which requires CA Owners to supply at least one non-personal contact email alias. Mozilla stated that Byte Computer was required to complete the incident reporting process described in the CCADB Incident Reporting Guidelines. The bug was later proposed for closure as WON’T FIX due to lack of response from the CA Owner since the bug was filed. The current resolution is WONTFIX.

Model: gpt-5.4-nano Generated: 2026-06-13 12:30 UTC Revised: 2026-06-16 18:16 UTC Confidence: 0.86 3 comments
Chronology
  1. Byte Computer S.A. was notified that required CCADB contact information needed updating.
  2. A Mozilla CA Program bug was filed for Byte Computer S.A.’s missing CCADB contact information.
  3. Mozilla directed the CA to complete the CCADB incident reporting process.
  4. The reporter proposed closing the bug as WON’T FIX due to no CA response.
Thread Activity
  1. Community commenter — Reported that Byte Computer S.A. had not updated required CCADB contact information after notification and that both “CA Email Alias 1” and “CA Email Alias 2” were empty, citing CCADB Policy Section 2.
  2. Mozilla representative — Stated that Byte Computer was required to complete the incident reporting process in the CCADB Incident Reporting Guidelines.
  3. Community commenter — Recommended closing as WON’T FIX due to no response from the CA Owner since the bug was filed.
Participants
Apple representative Mozilla representative Byte representative
Similar Local Cases
#2015568 RESOLVED Ccadb Metadata Update Incident Opened 2026-02-09 · Closed 2026-05-13 · 91% similar
NISZ Nemzeti Infokommunikacios Szolgaltato: Missing Contact Information in CCADB
#2015562 RESOLVED Contact Information Opened 2026-02-09 · Closed 2026-05-13 · 57% similar
Agencia Notarial de Certificacion (ANCERT): Missing Contact Information in CCADB
#2004699 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Repository Issue Opened 2025-12-08 Still Open · 53% similar
Netlock: CA in AIA in PEM format
#1941675 RESOLVED Ca Documents Incident Opened 2025-01-14 · 48% similar
Certum root lists a Microsec CPS in AllCertificateRecordsCSVFormatv2
#1772414 RESOLVED Incident Opened 2022-06-02 · Closed 2023-02-22 · 48% similar
E-Tugra: Failure to Respond to May 2022 Survey
#1946418 RESOLVED Audit Delay Incident Opened 2025-02-06 · Closed 2025-03-14 · 48% similar
Chunghwa Telecom: Delayed to Submit Annual CCADB Self-Assessment 2024 by GTLSCA.
#1843265 RESOLVED Incident Opened 2023-07-13 · Closed 2024-03-27 · 47% similar
PKIoverheid: Delayed audit statements for intermediate CAs
#2008023 RESOLVED Incident Opened 2025-12-30 · Closed 2026-02-19 · 47% similar
PKIoverheid: TSP CIBG Findings in 2025 ETSI Audit - Incident Report #2 – Supply Chain Management

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action