[ Assembly ] Fix parse_tls_record version parsing byte order bug
Open-source bounty · GitHub (bounty labels) · open as of 17 Oct 2026
- Amount as listed
- $1 fixed “$1” — quoted from GitHub (bounty labels)
- Platform
- GitHub (bounty labels)
- Kind of work
- Open-source bounty · Engineering
- Open to
- not stated by the platform
- Deadline
- not stated by the platform
- Status
- Open
- Checked
- 17 Oct 2026, 18:22 UTC
What the listing says
Fix parse tls record version parsing byte order bug - Line 128: mov ax, [rsi+1] loads version bytes in little-endian x86 order instead of network byte order (big-endian). TLS 1.0 wire bytes 0x03 0x01 are read as 0x0103 instead of the correct 0x0301. TLS 1.2 (0x03 0x03) passes by coincidence since both bytes are identic
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, bug, good first issue, help wanted, 💎 Bounty, $1, AI Agent friendly, AI only allowed - no humans
Open on GitHub (bounty labels) ↗
The work is offered, scoped and paid by GitHub (bounty labels) — not by GOAT Market. We record what they publish and link to it. Claiming, delivering and getting paid all happen on their site, under their terms.
More open on GitHub (bounty labels)
- [Feature] Implement Basic Anti-Cheat Protection $10,000
- [ Bounty $9k ] [ SDK ] Fix encoding.ts decodeParameter doesn't handle dynamic types — back... $9,000
- [ Bounty $9k ] [ Solidity ] Add gas sponsorship relay for agent transactions — security cr... $9,000
- [ Bounty $9k ] [ API ] Fix agents.py doesn't validate endpoint URL format — testnet findin... $9,000
- [ Bounty $9k ] [ SDK ] Fix rpc.ts doesn't handle JSON-RPC batch response ordering — backwa... $9,000