Comment on Three Dead ProtocolsparentComments−pjc5011yNot necessarily; presumably conservative admins will still configure it to deny-default. Especially if the traffic is encrypted and unfamiliar.−cbd198411yBOFH-admins will configure to accept-and-bitbucket-default; that is, make the other party think it's gotten through, and then ignore everything it has to say.Maybe throw in some fuzzing: accept-and-respond-with-gibberish-default.accept-and-spam-MX-record-always−paulmd11yHow about accept-and-randomly-lose? I'm a big fan of RFC 748 [1][1] https://tools.ietf.org/html/rfc748
Comments
Not necessarily; presumably conservative admins will still configure it to deny-default. Especially if the traffic is encrypted and unfamiliar.
BOFH-admins will configure to accept-and-bitbucket-default; that is, make the other party think it's gotten through, and then ignore everything it has to say.
Maybe throw in some fuzzing: accept-and-respond-with-gibberish-default.
accept-and-spam-MX-record-always
How about accept-and-randomly-lose? I'm a big fan of RFC 748 [1]
[1] https://tools.ietf.org/html/rfc748