Changes between Version 2 and Version 3 of org/meetings/2014WinterDevMeeting/notes/GuardDesign


Ignore:
Timestamp:
Jun 24, 2014, 2:12:38 AM (5 years ago)
Author:
cypherpunks
Comment:

is the "dhcp attack" on the per-network guard idea an actual problem?

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2014WinterDevMeeting/notes/GuardDesign

    v2 v3  
    2020- Hey, should there be a different set of guards per identity?
    2121- Or a different tor state per identity
    22   - see 10969. See wiki link from there. See tordyguards
     22  - see #10969. See wiki link from there. See tordyguards
    2323  - way to kill state reload state and restart tor
    2424  - need way to not have Tor launch a connection to an old guard before it realizes it's moved.
    2525  - need way to avoid dhcp attack
    2626     - networkmanager / systemd integration?
     27     - what is the dhcp attack? would an attacker in a position to manipulate your dhcp leases gain anything by causing you to keep picking new guards until you pick one of theirs? (wouldn't it be easier to just become the default gateway and then do whatever attacks they might do as a guard from that position instead?)
    2728- Separate guards per isolation profile.  That would be neat.
    2829  - Can't do in full. since there are infinite isolation profiles.