1 |
On Tue, Dec 01, 2009 at 04:07:44PM +0100, Penguin Lover laurent squawked: |
2 |
> Is it a common thing, or really easy to do, to redirect the content from a |
3 |
> server to another one? |
4 |
> |
5 |
> Like launching an lil app telling the port to listen and then get all data |
6 |
> travelling there?? |
7 |
|
8 |
You need to be a bit more precise about what you mean... |
9 |
|
10 |
If you are talking about client A sitting behind router B which |
11 |
interfaces with Big Scary Internet C, then it is trivial for the |
12 |
router B to have a transparent proxy or some other form of package |
13 |
re-write that redirects your traffic. |
14 |
|
15 |
If you are talking about client A and server B and server C then it is |
16 |
also trivial for server B to redirect all its traffic to server C. |
17 |
|
18 |
If you are talking about client A and server B and Bad server C and |
19 |
attacker D, I don't see how in general the attacker D can redirect |
20 |
traffic from B to C, unless D somehow sits on the only node that |
21 |
connects A to B (in which case you are essentially back to scenario |
22 |
1). (Yes yes, there are DNS injections and what nots, but in essence |
23 |
they are just variations of scenario 1.) |
24 |
|
25 |
There are also other possible scenarios. So please describe in a bit |
26 |
more detail what you are thinking of and why you care. |
27 |
|
28 |
Cheers, |
29 |
|
30 |
W |
31 |
|
32 |
|
33 |
-- |
34 |
English lessons for programmers #28: |
35 |
"Fewer" is of type int; whereas "less" is of type double. |
36 |
Sortir en Pantoufles: up 1089 days, 16:41 |