🌐 Website Issue | Enabling Chacha20 in TLS 1.2 #1792
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1792
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
I propose to activate Chacha20-Poly1305 in TLS1.2 at
www.privacytools.io
andprivacytools.io
.https://www.ssllabs.com/ssltest/analyze.html?d=www.privacytools.io
https://www.hardenize.com/report/privacytools.io/1584778546#www_tls
Any particular reason why you want this though?
Not much point in this.
Chacha20-Poly1305 was an extension to TLS 1.2, and is included in TLS 1.3. It's unlikely there would be a device old enough to not support TLS 1.3 that would have the Chacha20-Poly1305 extension ciphers.
The site does not support TLS 1.0 or 1.1.