If an attestation exchange message is rejected, respond with an error message before closing the channel.

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
security

Research direction

Start by reading the attestation exchange protocol described in the issue and the linked pull request discussion, especially the rejection behavior. Trace where a failed attestation currently closes the channel, then verify that a rejection message is sent before closure and that the exchange still terminates correctly.

Written by the indexing model from the issue text.

Description

enhancement

As part of the attestation exchange protocol, if an attestation fails - don't just close the channel but first respond with a rejection message.

https://github.com/flashbots/attested-tls-proxy/pull/37#discussion_r2545700557

Dominant language
Rust
Stars
6
Forks
2
Avg merge
13m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flashbots/attested-tls-proxy

All issues in flashbots/attested-tls-proxy

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.