0ec4f55fa9
Since I turned out to be implementing parts of Noise which I did not need to implement, I'm taking a different approach, and doing an unmodified Noise transport first and then making our modifications to it. That should reduce what I need to do to message pre-processing mostly, I think.
64 lines
1.7 KiB
Go
64 lines
1.7 KiB
Go
package i2np
|
|
|
|
import (
|
|
common "github.com/go-i2p/go-i2p/lib/common/data"
|
|
)
|
|
|
|
/*
|
|
I2P I2NP DatabaseSearchReply
|
|
https://geti2p.net/spec/i2np
|
|
Accurate for version 0.9.28
|
|
|
|
+----+----+----+----+----+----+----+----+
|
|
| SHA256 hash as query key |
|
|
+ +
|
|
| |
|
|
+ +
|
|
| |
|
|
+ +
|
|
| |
|
|
+----+----+----+----+----+----+----+----+
|
|
| num| peer_hashes |
|
|
+----+ +
|
|
| |
|
|
+ +
|
|
| |
|
|
+ +
|
|
| |
|
|
+ +----+----+----+----+----+----+----+
|
|
| | from |
|
|
+----+ +
|
|
| |
|
|
+ +
|
|
| |
|
|
+ +
|
|
| |
|
|
+ +----+----+----+----+----+----+----+
|
|
| |
|
|
+----+
|
|
|
|
key ::
|
|
32 bytes
|
|
SHA256 of the object being searched
|
|
|
|
num ::
|
|
1 byte Integer
|
|
number of peer hashes that follow, 0-255
|
|
|
|
peer_hashes ::
|
|
$num SHA256 hashes of 32 bytes each (total $num*32 bytes)
|
|
SHA256 of the RouterIdentity that the other router thinks is close
|
|
to the key
|
|
|
|
from ::
|
|
32 bytes
|
|
SHA256 of the RouterInfo of the router this reply was sent from
|
|
*/
|
|
|
|
type DatabaseSearchReply struct {
|
|
Key common.Hash
|
|
Count int
|
|
PeerHashes []common.Hash
|
|
From common.Hash
|
|
}
|