[tahoe-lafs-trac-stream] [tahoe-lafs] #1767: update Announcement "timestamp": sequence number?

[tahoe-lafs]

#1767: update Announcement "timestamp": sequence number?
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  warner
         Type:           |     Status:  assigned
  enhancement            |  Milestone:  1.10.0
     Priority:  major    |    Version:  1.9.1
    Component:  code-    |   Keywords:  forward-compatibility introduction
  network                |  time blocker
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by AmmonRs):

 Replying to [comment:5 warner]:
 > * if two nodes are somehow configured with the same private key, they'll
 fight over the announcements: each inbound announcement will trigger an
 outbound one with the higher seqnum, and they won't ever converge because
 they'll undoubtedly have different swissnums for the storage-server FURLs.
 They'll just chase each other up to infinity.
 if an attacker were able to get a node's private key, they could use the
 seqnum as a DoS attack, by making the node increment the counter until it
 looped, at which point all other nodes would forever ignore that node.
 probably not something to worry about, since if the private key is leaked,
 there are bigger problems, but something to consider.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1767#comment:16>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage