3 ms·
This would be an entertaining way of dealing with MITM agents as well, over HTTP. As long as the client knows not to open the request, you could trade them back
by hirsin 9y ago
This would be an entertaining way of dealing with MITM agents as well, over HTTP. As long as the client knows not to open the request, you could trade them back and forth with the MITM spy wasting tons of overhead.
- steego 9y agoIt would be an interesting way of streaming data if both sides used a custom decompression algorithm that skipped n bytes without allocating it anywhere. The payload could be encrypted text of two chat bots talking jibberish.
- mirimir 9y agoNow that's very interesting. Maybe hack a custom ssh with this feature. Adversaries that intercepted data or attempted MitM would be inconvenienced. Edit: Or even more useful, bbcp. Which is the best file transfer app that I've ever used.
- danesparza 9y agoThis is similar to kippo or cowrie, SSH honeypots: https://github.com/desaster/kippo https://github.com/desaster/kippo https://github.com/micheloosterhof/cowrie https://github.com/micheloosterhof/cowrie
- mirimir 9y agoI meant more than a honeypot. But rather, a functional SSH app that messes with standard SSH apps and libraries.
- shabble 9y agoSounds a bit like a simplified "Chaffing and Winnowing"[1], where the chaff identification is pre-shared through your custom compression parameters. There was a HN story[2] on Chaffinch[2], which is where I came across teh idea. [1] https://en.wikipedia.org/wiki/Chaffing_and_winnowing https://en.wikipedia.org/wiki/Chaffing_and_winnowing [2] https://news.ycombinator.com/item?id=14408757 https://news.ycombinator.com/item?id=14408757 [3] https://www.cl.cam.ac.uk/~rnc1/Chaffinch.html#Chaffing https://www.cl.cam.ac.uk/~rnc1/Chaffinch.html#Chaffing