Opened 3 years ago

Closed 2 years ago

#22694 closed defect (fixed)

prop224: Disable netflow padding if v3 single onion services are enabled

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop224, single-onion
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

Once #17857 is implemented, we need to do the same thing for v3 single onion services.

That could be harder, because we need to decide what to do for a mixed single onion/anonymous onion instance. Maybe we shouldn't allow it?

Child Tickets

Change History (3)

comment:1 in reply to:  description Changed 3 years ago by dgoulet

Parent ID: #20657

Replying to teor:

Once #17857 is implemented, we need to do the same thing for v3 single onion services.

That could be harder, because we need to decide what to do for a mixed single onion/anonymous onion instance. Maybe we shouldn't allow it?

Current work is not allow it right now. We could change that in future version but for 032 I say we keep it simple.

comment:2 Changed 2 years ago by dgoulet

Parent ID: #20657

This is blocking on #17857

comment:3 Changed 2 years ago by dgoulet

Resolution: fixed
Status: newclosed

In channelpadding_decide_to_pad_channel(), it disables padding for onion service at large (all versions). rend_service_allow_non_anonymous_connection() does check for the global options that affect both v2 and v3.

We are good here. The day we get mixed onion service, we should think this one through.

Note: See TracTickets for help on using tickets.