You should also check out cloud hosters: upload pdf, doc or txt with
unique hidden service urls and log pageviews with php. Create a dump.php
which dumps "getallheaders()" to a file and then create URL redirections
at your webserver so all url requests get internally executed with
dump.php without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> I was informed to bounce my results over to you so you can look
> deeper in why the exits are doing what they do.
Interesting, I never answered such questions (why are [bad] exits
doing what they do - in terms of malicious activity). May I ask who
Hi,
This is just part of my research and I was informed to bounce my results
over to you so you can look deeper in why the exits are doing what they do.
All URLs are unique, so the chance for a crawler/spider/robot to find
that URL is extremely unlikely.
/db/backups/997391913-2015 is a uniq
On Sat, 27 Jun 2015 17:42:35 +0200
chloe wrote:
>
> Hello,
>
> I have a question regarding some strange behavior on some nodes(11 of
> them).
>
>
> See this access-log:
>
> 81.89.0.201 - - [25/Jun/2015 12:25:30] "GET /db/backups/965110218-2015
> HTTP/1.1" 200 5057
> 37.187.202.46 - - [25/J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I read your email in the context of your recent blog post [1] on bad
exits (without it, the email does not make much sense to me).
Since I'm just assuming and other readers probably don't have that
context you might want to specify it.
If my a
Hello,
I have a question regarding some strange behavior on some nodes(11 of
them).
See this access-log:
81.89.0.201 - - [25/Jun/2015 12:25:30] "GET /db/backups/965110218-2015
HTTP/1.1" 200 5057
37.187.202.46 - - [25/Jun/2015 14:00:10] "GET /db/backups/965110218-2015
HTTP/1.1" 200 5057
37
