status-im/go-libp2p-pubsub
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add a note why we're expecting two messages

Browse Source 
As the adversary has turned of signature verification, we should expect
to see two messages (the correctly signed and the incorrectly signed
one) when we publish. Those that have verification on, should only see
one.
This commit is contained in:
Raghav Gulati 2019-05-08 09:00:25 -07:00
parent 84bb35ebf4
commit 594e6a4ab9
No known key found for this signature in database
GPG Key ID: EA2C73F6F7EF2701
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
floodsub_test.go
View File

@ -1022,6 +1022,9 @@ func TestImproperlySignedMessageRejected(t *testing.T) {
<-time.After(1 * time.Second) <-time.After(1 * time.Second)
adversaryCancel() adversaryCancel()
// Ensure the adversary successfully publishes the incorrectly signed
// message. If the adversary "sees" this, we successfully got through
// their local validation.
if len(adversaryMessages) != 2 { if len(adversaryMessages) != 2 {
t.Fatalf("got %d messages, expected 2", len(adversaryMessages)) t.Fatalf("got %d messages, expected 2", len(adversaryMessages))
} }