Using the NONE cipher causes replication to erroneously report failure
[ Cloning this bug to the 9.2.1-BRANCH so we remember to merge the fix in case a 184.108.40.206 is ever done ]
I don't have the output that you and I were looking at, so I'll use Josh's
Replication ZFS1/ctliscsi -> 10.90.90.2 failed: WARNING: enabled NONE cipher
Basically, ssh issues a warning when NONE is enabled and the replication code sees this message as indicative of an error, when of course it is not.