Recent changes to feature-requestshttps://sourceforge.net/p/hivemindloic/feature-requests/2011-01-05T13:34:59ZIon Canon Control Protocol RFC2011-01-05T13:34:59Z2011-01-05T13:34:59ZSm@ckerhttps://sourceforge.net/u/hansvonsmacker/https://sourceforge.netddae8422fb7ea2322edf84a5f3ce6bed33890742<div class="markdown_content"><p>Hi!<br />
I think we need a universally recognized and well-formed specs for loic control protocol. Currently, we have none, but it would be quite cool if we had RFC-like documents, as the ones we have i.e. for IRC. Naturally, it should be plain-text based, and thus expandable to different carriers, i.e. XMPP, DHT-varieties etc. Also, considering twitter and suchlike, I guess it would be handy to have short and long versions for parameters, like we have in *NIX (think -p or --protocol).</p></div>Using "false sender's IP"2010-12-13T00:07:11Z2010-12-13T00:07:11Zarcadiushttps://sourceforge.net/u/arcadius-radius/https://sourceforge.net923d931db09fcf1d2c820799ca20607c6834578e<div class="markdown_content"><p>Currently DDos attacks have some lacks:<br />
1. Target can easily firewall attacker machine(s),<br />
2. Their IPs can be easily logged.</p>
<p>I'm not sure, but: can attacker send TCP packets with false, distorted source IP?<br />
Most likely, such packets will be filtered out by NAT/ISP.<br />
But probably some pass through. If so, problems 1 &amp; 2 can be partially solved.</p>
<p>To select appropriate "source IP mask" attacker needs "test target" - remote machine, which reports him if his packets come OK.<br />
In this scenario, attacker:<br />
- Sends test packets to "test target" to define source IP mask which is as wide as possible but still passes through his NAT/ISP,<br />
- Bombs real target(s) with TCP-packets with random source IPs from mask defined.</p></div>