Build a TlsMasquerader that makes data look like one or more valid TLS ApplicationData packet(s),
and that can reassemble such packets on the other side of a Node-to-Node connection and extract the hidden CORES package.
Make sure that:
A) the TlsMasquerader puts a signature in the masked data so that, when presented with the data, it can tell whether or not it can handle unmasking of that data. (Talk to Dan about how to employ encryption here.) It's important that the TlsMasquerader not assume that it's the only Masquerader in the system.
B) space is left for other TLS Masqueraders as well. Real TLS connections don't consist solely of ApplicationData packets; therefore, as we become more clandestine, we'll have to enhance the existing TLS Masqueraders and add more.
Build a TlsMasquerader that makes data look like one or more valid TLS ApplicationData packet(s),
and that can reassemble such packets on the other side of a Node-to-Node connection and extract the hidden CORES package.
Make sure that:
A) the TlsMasquerader puts a signature in the masked data so that, when presented with the data, it can tell whether or not it can handle unmasking of that data. (Talk to Dan about how to employ encryption here.) It's important that the TlsMasquerader not assume that it's the only Masquerader in the system.
B) space is left for other TLS Masqueraders as well. Real TLS connections don't consist solely of ApplicationData packets; therefore, as we become more clandestine, we'll have to enhance the existing TLS Masqueraders and add more.