101–110 of 111 posts
Earlier quoted context omitted.
You, sir, win .
but 4coin can add some simple code (e.g. use regex) just to remove that line from scrapped content before sending it to the user though.
Earlier quoted context omitted.
Why do you jump to the assumption that they're malicious then? Put a few more branding elements into your page design, so that visitors to their site will understand that they're redirecting your data. Then take advantage of the extra publicity that they're giving you.
Having a duplicate site would do a lot of damage to my Google search rankings.
Instead of blocking source IP. Detect and send "unwanted information".
I agree, this may be a more effective approach than trying to block the IP and the whole whack-a-mole issue. Essentially, they trust the data you're providing and are trying to make a buck off that info. But if they lose that trust because they don't know whether the data is legit or not, you win! I would also try to mask the fact that the data is not accurate, if they immediately see everything as simply zeroed out,…
I'd also recommend only borking SOME of the data - an intermittent bug is harder to fix than a consistent one!
I would contact the other site first and find out WTF. It is unlikely, but they might have a good reason for it. If they are just trying to rip you off, solution might be as simple as just asking them to stop.
In addition to the other ideas here, I'd also recommend feeding a completely fake site to the source IP of the thief. Possibly including some political ideas that could get him in trouble in his host country (up to you depending on how mean you wish to be).
Earlier quoted context omitted.
So, you're suggesting him just giving up on his site and moving on? One issue that wasn't even his fault and he should walk away? I guess trying to ask for advice and acting on that advice, all the while learning more and more about the potential attack vectors one should be aware of when dealing with these relatively new cryptocurrency services, is a shit idea. BTW, love your intolerant handle. I guess you'd be bash…
No, I expect him to sit, analyze the situation and learn things instead of a hopeless "I don't know what to do" The issue is not "Please advice me what to do", it is saying it in the spirit of someone who doesn't know how he got in the situation in the first place. For someone who builds a site like that, he should've know better.
If you end up trying to block his IP, don't just DROP or REJECT his packets. TARPIT [1] them! This way not only would you be denying him access, but you would also be draining his resources. Another thing to try is to see just how much data his server will take. See if you can send him a GB-sized response. [1] http://www.netfilter.org/projects/patch-o-matic/pom-external...
Please try contacting them directly and simply asking to stop before doing this!
Dan, I need to show that I'm over 18 on a couple of sites, and they want me to verify by entering a credit card number. But I pay everything in cash, so I don't have any credit cards. Could you email me your card #s, please?
Earlier quoted context omitted.
but 4coin can add some simple code (e.g. use regex) just to remove that line from scrapped content before sending it to the user though.
You could defeat regex by sending a different base64 string each time by including a call to void(server side random number).
Earlier quoted context omitted.
If you have a hard time determining their IP, here's a trick that might work. Visit their site with a unique but innocuous-looking path or query that would never be accessed by a normal user. For example: http://4co.in/?q=1 If the query string is being passed through, which I suspect it is, you can use the query string to easily locate the corresponding entry in your own logs. Or, if the query string isn't being pass…
countermove: he works it out and blocks your magic query - query needs to be made from somewhere indistinguishable from normal requests. Changing IP would be best... maybe via tor. A unique sequence of legitimate requests might be more difficult to for the other side to detect and it won't result in 404s. Could randomise the sequence and each can come from a different IP as long as they were synchronised properly.
He very well might. But my estimation of the thief's skills is low. I could be wrong, of course.
> A unique sequence of legitimate requests might be more difficult to for the other side to detect and it won't result in 404s. Could randomise the sequence and each can come from a different IP as long as they were synchronised properly.
That's probably the best bet. A legitimate but very winding path through actual links on the site would work quite well. Given enough steps, it would almost certainly be unique. Because you'd be varying the path each time, the thief would find it hard or impossible to block you.
In addition to the other ideas here, I'd also recommend feeding a completely fake site to the source IP of the thief. Possibly including some political ideas that could get him in trouble in his host country (up to you depending on how mean you wish to be).
That's dark...