close Warning: Can't synchronize with repository "(default)" (Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.

Changes between Initial Version and Version 1 of Ticket #1336, comment 8


Ignore:
Timestamp:
Jul 23, 2014, 6:29:08 AM (5 years ago)
Author:
ExtraBattery
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1336, comment 8

    initial v1  
    33About that backward-incompatibility: I take it you refer to applications becoming incompatible. Applications that let SAM/BOB handle their repliable datagrams would normally not notice the change. Would it be possible to make the change so that it's off by default, allowing you to opt-in? Like specifying a parameter in the form "i2cp.sendEnhancedRepliableDatagrams=true". This would allow applications to control what kind of repliable datagram they send. If you have an old application that needs to interpret ingoing repliable datagrams on the (raw) binary level and thus relies on the "old" (427+ bytes) format, your application would continue to be able to interact with itself.
    44
    5 If you look at things from the position of an application developer, there are a lot of protocols in use that cannot easily be changed. And it's hard to add replay security on the application level. You can't use the destination key for that, since you only know its length, but you don't understand its format. So you would have to introduce another asymmetric key management on the application layer, which adds a lot of complexity to applications and increases the overall bandwidth consumption and cryptographic overhead.
     5If you look at things from the position of an application developer, there are a lot of protocols in use that cannot easily be changed. [Wrong claim removed.]
    66
    77Not that I2P is at fault. It's just in the optimal position to solve the problem. I believe you don't need a nonce and a bloom filter to have a satisfying result. 32 bytes of receiver destination hash + four bytes of timestamp (with say one second granularity starting at y2k) would already make a huge difference.