Opened 5 months ago

Last modified 6 weeks ago

#29083 new defect

WTF-PAD: Specify exit policy for machine conditions

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: wtf-pad, tor-relay, tor-cell, padding
Cc: nickm Actual Points:
Parent ID: Points: 4
Reviewer: Sponsor: Sponsor2-can

Description

From the TODO file:

  - Specify exit policy for machine conditions?
    - short_policy_t looks good, except for its flexible array member :/
      - Can we make our own struct with a small, fixed number of policy
        entries? Say 3-4? Or is that a bad idea to lose this flexibility?
    - Check conditions based on attached streams on the circuit
      - Accept should mean "only apply if matched"
      - Reject should mean "don't apply if matched"
      - If a policy is specified, Reject *:* is implicit default (so reject
        policies need an Accept entry).
      - With no policy, Accept *:* is implicit default.

Child Tickets

Change History (9)

comment:1 Changed 5 months ago by asn

Milestone: Tor: 0.4.0.x-finalTor: unspecified

comment:2 Changed 5 months ago by mikeperry

Keywords: 041-proposed added

comment:3 Changed 5 months ago by mikeperry

Points: 4

comment:4 Changed 5 months ago by mikeperry

Priority: MediumHigh

comment:5 Changed 5 months ago by nickm

Sponsor: Sponsor2

comment:6 Changed 4 months ago by mikeperry

Keywords: 041-proposed removed

Take some wtf-pad stuff out of 041-proposed

comment:7 Changed 4 months ago by mikeperry

Priority: HighMedium

comment:8 Changed 3 months ago by mikeperry

Parent ID: #28632

Not strictly necessary for padding to be useful for us.

comment:9 Changed 6 weeks ago by mikeperry

Sponsor: Sponsor2Sponsor2-can

FYI: we are not planning on doing this unless a research machine needs a way to specify that padding should only apply to connections to specific ports.

Note: See TracTickets for help on using tickets.