Skip to content

feat(domains): certificate details and TLS modes on hover cards - #151

Merged
hiddify-com merged 1 commit into
hiddify:devfrom
Hiddify-Official:feat/domain-badge-cards
Nov 1, 2026
Merged

hiddify-com merged 1 commit into
hiddify:devfrom
Hiddify-Official:feat/domain-badge-cards

Conversation

@Hiddify-Official

Copy link
Copy Markdown
Contributor

Problem

On the Domains page, hovering a domain's certificate badge ("Valid · N days left") showed a few wrapped lines of white text: a hint, the issuer's short name and the expiry. A Reality / Fake badge only said "Fake and Reality TLS domains do not need a certificate of their own". Admins asked for the certificate's full details and a clearer look.

Change

  • domains_page_api.py: _tls_out now also returns issued_at, names (SANs), key ("ECDSA P-256", "RSA 2048"), ca (the issuing organisation), the stored fingerprint and auto_renew. The first four are read from the stored PEM with cryptography, lru_cached per PEM; an unreadable PEM gives nothing.
  • DomainsView.vue: both badges open a hover card (PrimeVue tooltip with escaped HTML, class dm-tip) in the badge's own colour.
    • Certificate card:
      • state and hint;
      • a bar of the life left, between the issue and expiry dates, amber under three weeks and red under one;
      • issued by, covers (names as chips), key, auto-renew and fingerprint;
      • the last error when the certificate failed.
    • TLS mode card (Reality, Fake, DNS, a built-in server's fake-TLS name): what the mode does (the existing tlsMode.*Hint text), that it needs no certificate, and the name (SNI) it shows.
    • Solid on the glass themes; new domains.tip.* strings in 7 languages.

Screenshots

The fingerprint is blurred, because it would identify the test server's certificate in CT logs.

Before After
before after
before after
before after
before after

Tested

  • _cert_facts locally with a generated ECDSA certificate (organisation, SANs, key, issue date) and with garbage, which returns {}.
  • On main, after a panel restart: the Valid card, the Reality card, Persian with Jalali dates, and the Fake card in dark mode. No errors in the panel log.
  • vue-tsc: no errors in the changed files.

Review

  • Confidence: High (>90%) — additive API fields read from data the panel already stores, and a UI-only change, checked on the server.
  • Complexity: Simple — the domains page and its row serializer.

🤖 Generated with Claude Code

…r cards

Hovering a domain's certificate badge showed a few lines of text (a hint,
the issuer, the expiry), and a Reality / Fake badge only "Fake and Reality
TLS domains do not need a certificate of their own".

- The domains API reads the stored certificate (cached per PEM): when it
  was issued, the names it covers, its key and the issuing organisation;
  with the stored fingerprint and auto-renew.
- The certificate badge opens a card in the badge's colour: its state and
  hint, a bar of the life left with the issue and expiry dates (amber under
  three weeks, red under one), then issued by, covers, key, auto-renew,
  fingerprint, and the last error when it failed.
- A TLS mode badge (Reality, Fake, DNS, a built-in server's fake-TLS name)
  opens a card that says what the mode does, that it needs no certificate
  and which name (SNI) it shows. Solid on the glass themes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🥷 Ninja i18n – 🛎️ Translations need to be updated

Project /project.inlang

lint rule new reports level link
Identical pattern 2 warning contribute (via Fink 🐦)

@hiddify-com
hiddify-com merged commit 9169220 into hiddify:dev Nov 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants