Eth2.0-specs: Allow Only Snappy-Compressed Encoding

[rauljordan]

Hi all,

Currently Prysm allows for both snappy compressed and regular ssz encoded messages via p2p. Our security audit concluded allowing these two options is a security risk that can result in a network partition of someone operates nodes without snappy and others operate nodes with snappy enabled. Is there still a need for non-snappy encoded messages in the networking spec, or should the spec enforce snappy-compressed only?

[protolambda]

We can discuss this during the implementers call today: https://github.com/ethereum/eth2.0-pm/issues/162#issuecomment-649079956

[djrtwo]

So we certainly shouldn't have non-snappy in gossip.
We have in currently in the req/resp which shouldn't be a security risk, but I don't see a particular use case for this

[djrtwo]

Thinking we remove this in the v0.12.2 release unless anyone is relying upon it and with good reason to continue to support

[djrtwo]

closed via #1982