feat(certinfo): add tls-info flag to display negotiated TLS settings …#34
Conversation
…and supported protocols and ciphers
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR introduces TLS protocol and cipher suite probing for remote endpoints in the certinfo command. It adds a ChangesTLS Probing and Negotiation Info Feature
Sequence DiagramsequenceDiagram
participant PrintData
participant ProbeTLSInfo
participant probeProtocol
participant probeCiphersConcurrently
participant printTLSInfo
PrintData->>ProbeTLSInfo: call when TLSInfoRequested
ProbeTLSInfo->>probeProtocol: test each protocol version
probeProtocol-->>ProbeTLSInfo: populate ProbedProtocols map
ProbeTLSInfo->>probeCiphersConcurrently: scan all cipher suites
probeCiphersConcurrently-->>ProbeTLSInfo: populate ProbedCiphers slice
PrintData->>printTLSInfo: render negotiated + probed tables
printTLSInfo-->>PrintData: formatted TLS info output
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsStopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@internal/certinfo/certinfo_handlers.go`:
- Around line 325-327: The dialer used for probe dials currently hardcodes
Timeout as 1 * time.Second which can cause false negatives on slow links; change
the net.Dialer Timeout initialization (the variable named dialer) to use the
existing TLSTimeout constant instead of 1 * time.Second, and update the other
identical occurrence later in the file (the second net.Dialer initialization) to
do the same so all probe dials share TLSTimeout.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 081bfcd3-e5bb-4c60-8abc-0986e83ee8f5
📒 Files selected for processing (8)
README.mdinternal/certinfo/certinfo.gointernal/certinfo/certinfo_handlers.gointernal/certinfo/certinfo_handlers_test.gointernal/certinfo/certinfo_test.gointernal/certinfo/main_test.gointernal/cmd/certinfo.gointernal/cmd/certinfo_test.go
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
…and supported protocols and ciphers
Summary by CodeRabbit
New Features
--tls-infoflag to display negotiated TLS protocol and cipher information from remote endpoints, with probing of supported protocols and cipher suites.Documentation
certinfocommand examples and documentation for the new--tls-infoflag.