[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Our nameless project.
- To: [email protected]
- Subject: Our nameless project.
- From: [email protected] (davidroman96)
- Date: Sat, 31 May 2014 19:15:57 +0200
- In-reply-to: <CAD2Ti29VBSF=GJ79=RCt6fiHZooHSe0b3CJ43Tt9S0yD7Z-=FA@mail.gmail.com>
- References: <[email protected]> <20140531114251.GB1973@miyamoto> <[email protected]> <CAD2Ti29VBSF=GJ79=RCt6fiHZooHSe0b3CJ43Tt9S0yD7Z-=FA@mail.gmail.com>
On 31/05/14 17:54, grarpamp wrote:
>> hosts that comunicate each other spoofing the
>> source ip
>> will recieve
>> the file with spoofed ip
>> in our network all the source ips are fake
>> (spoofed ips)
>> our project delete your real ip
>> and put a one fake.
> This may work in your test lan, but on the real internet, packets
> with bogus src ip's are generally dropped at the customer interface
> with rpf and other filters, thus breaking your app.
>
>> With this method the reciever don't know who want to download X
>> file and if the NSA or FBI get the logs of the reciever they can not use
>> it for trace the origin.
> They will become a receiver and trace them back with netflow.
>
We know that the sources ips generally are dropped, this is the only
problem that we have.
But if multiple hosts can use the same ip how the connection can be
traced? Only the ISP have the information, the receiver don't know
anything a part from the content of the packet.