hashicorp / hashicorp/nomad

Incorrect TLS uses too much CPU

Open
#3,245 0 comments 0 reactions 0 assignees View on GitHub
theme/tls type/bug
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

If filing a bug please include the following:

### Nomad version

```
nomad v0.6.3
```

### Operating system and Environment details

### Issue

### Reproduction steps

1. Give Nomad wrong certificates
2. Watch CPU burn

### Nomad Server logs (if appropriate)

### Nomad Client logs (if appropriate)

### Job file (if appropriate)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue on Nomad v0.6.3 using incorrect certificates and observing CPU usage. Trace the TLS failure path and verify that invalid certificates no longer cause sustained CPU burn.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.