Skip to content
Standard Reader
Log in
Tag

Tls

Articles and publications tagged Tls across the Atmosphere.

37articles10publications
kozhevnikova
kozhevnikovaNov 4, 2026
A TLS syslog tunnel is not authenticated until both ends verify certificates
A practical review of rsyslog TLS authentication and failure testing.
syslogtls
ioneyrezende
ioneyrezendeNov 2, 2026
CVE-2026-105483: when an IPv4 address is checked as a DNS name
A technical explanation of the Node.js TLS identity classification mismatch in CVE-2026-105483.
CVE-2026-105483Node.js
jeffreyciend
jeffreyciendNov 2, 2026
Auditing Node.js code for the CVE-2026-105483 TLS identity mismatch
A code audit method for Node.js TLS destinations, certificate callbacks and affected runtimes.
CVE-2026-105483Node.js
ivanova
ivanovaNov 2, 2026
Threat modeling the CVE-2026-105483 certificate bypass
A threat model for destination influence, certificate trust and sensitive traffic in CVE-2026-105483.
CVE-2026-105483Node.js
eiuspkz
eiuspkzNov 2, 2026
Testing the fullwidth-IPv4 certificate path in CVE-2026-105483
Regression and positive-control tests for the Node.js certificate identity behavior.
CVE-2026-105483Node.js
andreagomez205
andreagomez205Nov 2, 2026
Measuring CVE-2026-105483 exposure without overstating it
How to interpret ZoomEye product fingerprints and CVE-filter results for CVE-2026-105483.
CVE-2026-105483Node.js
johnettagaweraks
johnettagaweraksNov 2, 2026
Patching CVE-2026-105483 across a mixed Node.js estate
Inventory, rebuild and validation steps for Node.js 24.22.1 and 26.12.1.
CVE-2026-105483Node.js
facilishz
facilishzNov 2, 2026
Why a trusted certificate is not always the right certificate
The distinction between chain trust and endpoint identity in CVE-2026-105483.
CVE-2026-105483Node.js
kozhevnikova
kozhevnikovaNov 1, 2026
CVE-2026-105483 remediation checklist for Node.js teams
A concise remediation and assurance checklist for affected Node.js runtimes.
CVE-2026-105483Node.js
ivanova
ivanovaNov 1, 2026
CVE-2026-106072: inventory and logging gaps around alternate IPv4 forms
Technical analysis of CVE-2026-106072 and the Node.js TLS hostname-verification defect.
securityvulnerability
eiuspkz
eiuspkzNov 1, 2026
CVE-2026-106072 response guide: patch, test, and monitor the client boundary
Technical analysis of CVE-2026-106072 and the Node.js TLS hostname-verification defect.
securityvulnerability
eiuspkz
eiuspkzNov 1, 2026
Regression Testing Node.js Integrations for CVE-2026-106069
Regression Testing Node.js Integrations for CVE-2026-106069
CVE-2026-106069Node.js
kozhevnikova
kozhevnikovaNov 1, 2026
OAuth mTLS binds credentials to certificates, not to people
Design checks for mutual-TLS client authentication and certificate-bound OAuth tokens.
securityoauth
ivanova
ivanovaOct 31, 2026
Testing Fragmented ClientHello Handling After CVE-2026-75595
A focused regression test plan for the Netty parser flaw and the mTLS policy around its fallback path.
securityvulnerability
ivanova
ivanovaOct 30, 2026
The threat model behind CVE-2026-111943: forged chains without a broken signature
Technical analysis of CVE-2026-111943 in Go crypto/x509, including affected versions, certificate-chain impact, remediation, and evidence limits.
securityvulnerability
eiuspkz
eiuspkzOct 30, 2026
Running a controlled response to CVE-2026-111943 without weakening TLS checks
Technical analysis of CVE-2026-111943 in Go crypto/x509, including affected versions, certificate-chain impact, remediation, and evidence limits.
securityvulnerability
andreagomez205
andreagomez205Oct 30, 2026
What a ZoomEye match for Go does not say about CVE-2026-111943
Technical analysis of CVE-2026-111943 in Go crypto/x509, including affected versions, certificate-chain impact, remediation, and evidence limits.
securityvulnerability
johnettagaweraks
johnettagaweraksOct 30, 2026
Custom root pools and proxy trust after CVE-2026-111943
Technical analysis of CVE-2026-111943 in Go crypto/x509, including affected versions, certificate-chain impact, remediation, and evidence limits.
securityvulnerability
kozhevnikova
kozhevnikovaOct 30, 2026
Code-signing trust sits outside the eMudhra TLS scan
Code-signing trust, build integrity and where network measurement stops
securitytls
ioneyrezende
ioneyrezendeOct 30, 2026
An incident-response sequence for the eMudhra CA disclosure
Incident-response sequence for scoping, validating and monitoring CA trust exposure
securitytls
半ちゃーはん特盛りテック別館
半ちゃーはん特盛りテック別館Oct 14, 2026
【Postfix】Gmailの「赤い南京錠（暗号化されませんでした）」警告を消す！STARTTLS有効化手順
自前のメールサーバーから Gmail 宛てに送信した際、SPF や DKIM、DMARC がすべて PASS しているにもかかわらず、差出人欄に「開いた赤い南京錠アイコン（このメールは暗号化されませんでした）」という不穏 […]
セキュリティUbuntu
半ちゃーはん特盛りテック別館
半ちゃーはん特盛りテック別館Sep 22, 2026
【保存版】Cloudflare導入時に絶対踏む520〜526エラー完全攻略ガイド！原因の切り分けと設定手順
CDNやWAF、DDoS保護を手軽に導入できる超強力なサービス「Cloudflare」。しかし、DNSを切り替えた直後やSSL設定を変更した瞬間に、見慣れない「Error 520」「Error 521」といった画面が表示 […]
CloudflareSSL
-=Kernel-Error=-
-=Kernel-Error=-Aug 17, 2026
ECH aktivieren: Encrypted Client Hello in nginx mit OpenSSL 4.0, sechs Domains und ein gemeinsamer Deckname
Der Servername im TLS-Handshake bleibt für jeden Netzwerkbeobachter sichtbar, selbst wenn DNS-Anfragen längst verschlüsselt laufen. Mit OpenSSL 4.0 und einem gemeinsamen Deckname über mehrere unabhängige Domains hinweg lässt sich das schließen, wenn eine Entscheidung nicht falsch getroffen wird: der öffentliche Name.
DNSDNSSEC
-=Kernel-Error=-
-=Kernel-Error=-Aug 16, 2026
sipgate unter Linux: ein Softphone, das Kontakte und Kalender aus der eigenen Nextcloud kennt
Ein Softphone unter Linux, das an meinem sipgate-Konto hängt und beim Klingeln den Namen aus meiner eigenen Nextcloud anzeigt statt einer nackten Rufnummer. Der Weg dahin führt nicht über CardDAV im Telefon, sondern über den evolution-data-server, und das Softphone merkt davon nichts. Dazu die Frage, was bei so einem Anruf eigentlich verschlüsselt ist, einmal nachgemessen statt geglaubt.
1
EncryptionFlatpak