Add fields for identifying the security protocol, cipher, signature and so on
Open
Nobody has claimed this yet.
enhancement
whiteboard
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Add those fields to PerformanceResourceTiming.
Protocol - SSL 1.0, SSL 2,0, SSL 3.0, TLS 1.1, TLS 1.2, TLS 1.3...
Cipher - AES_128_GCM...
Key exchange - ECDHE_RSA...
Signature algorithm - SHA256RSA...
Signature hash - SHA256...
Thumbprint algorithm - SHA1...
Public key - RSA...
Public key bits - 2048...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the PerformanceResourceTiming specification and the requested fields: protocol, cipher, key exchange, signature algorithm and hash, thumbprint algorithm, public key, and key size. Done means reaching agreement on the fields and defining their behavior and representation in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100