speaking from experience (https://github.com/bryanbrannigan/pastebin-parser) if you are just grabbing the pastes from the "latest" box you are missing a lot. To grab everything we actually had to create a distributed setup or else pastebin would start banning our IPs.
I ran into that issue myself. Pastebin throttling is real. I was playing around with the idea of actually using the socks5 proxies gathered through scraping in order to retain modularity (and eliminate the necessity of multi-IP set ups which could easily get pricey).
It would be tough because I would have to check the health of each proxy prior to use (so that I don't miss out on request windows), but still an interesting concept to consider.
21 comments
[ 5.3 ms ] story [ 51.8 ms ] threadThe two of you together can help us (l)users know when we've been pwned...
#1 - Hacker breaks into your production server and steals your config files
#2 - Hacker breaks into your dev computer and steals your config files
If either of these things happen, I think you have a bigger security issue than any you might find on Pasteye.
https://news.ycombinator.com/item?id=6166731
https://canary.pw
New version is coming out this week that lets you search via relation.
Also, just to draw the distinction: Pasteye is for near-realtime monitor notifications, and it seems like Canarypw is more like an archival search.
[edit]
I should add that a component of it might be open-sourced but I haven't had much time to digest the idea of doing so.
Also, I wrote mine in Node (scrape parsing & RESTful APIs just SCREAM async), while dumpmon is written in Python
I'm planning a solid revision sometime soon!
It would be tough because I would have to check the health of each proxy prior to use (so that I don't miss out on request windows), but still an interesting concept to consider.
I take my entries from the archive as they are available, and I don't believe I ever miss any.
Inb4 not reading before posting