#urlteam 2015-01-03,Sat

↑back Search

Time Nickname Message
01:11 🔗 pwnsrv has quit IRC (Read error: Operation timed out)
01:18 🔗 primus has joined #urlteam
01:29 🔗 GLaDOS has quit IRC (Ping timeout: 272 seconds)
01:31 🔗 GLaDOS has joined #urlteam
01:31 🔗 swebb sets mode: +o GLaDOS
02:15 🔗 aaaaaaaaa has quit IRC (Read error: Operation timed out)
02:50 🔗 aaaaaaaaa has joined #urlteam
03:29 🔗 Mayonaise how do fusl, chip, and 2tl get such crazy high numbers on the tracker stats page? the max workers on the warrior is 6 and i assume that their ip would be blocked if they had a dozen warriors running on the same interface. is there a trick, or do they simply have access to vms on a lot of different networks?
03:33 🔗 ^F Mayonaise: i run a datacenter, that should be explanation enough :)
03:34 🔗 Mayonaise so multiple vms with different external ips?
03:35 🔗 ^F yea
03:35 🔗 Mayonaise i am asking because i can run plenty more warriors on a few different networks, but i thought it might be worth seeing if there was a different approach that was not obvious to me
03:35 🔗 Mayonaise cool
03:35 🔗 Mayonaise how many do you have running?
03:36 🔗 ^F none at the moment, i use up all servers for portscanning 0.0.0.0/0
03:37 🔗 Mayonaise haha ok
03:37 🔗 Mayonaise that sounds like fun
03:37 🔗 ^F it is
03:37 🔗 Mayonaise https://github.com/robertdavidgraham/masscan
03:38 🔗 ^F yep
03:38 🔗 ^F near to 1500 abuse mails generated
03:38 🔗 ^F mostly automatic
03:39 🔗 ^F some people describe portscanning as illegal and they will file a police report
03:39 🔗 ^F err, someone said "fail a police report"
03:41 🔗 GitHub49 has joined #urlteam
03:41 🔗 GitHub49 has left
04:11 🔗 ivan` has quit IRC (Max SendQ exceeded)
04:11 🔗 ivan` has joined #urlteam
04:27 🔗 z00nx0 has joined #urlteam
04:55 🔗 aaaaaaaaa has quit IRC (Leaving)
06:02 🔗 Start is now known as StartAway
07:20 🔗 dashcloud has quit IRC (Read error: Operation timed out)
07:25 🔗 dashcloud has joined #urlteam
07:34 🔗 Fusl has quit IRC (Read error: Operation timed out)
07:34 🔗 Fusl has joined #urlteam
09:38 🔗 dashcloud has quit IRC (Quit: No Ping reply in 240 seconds.)
09:42 🔗 dashcloud has joined #urlteam
09:52 🔗 dashcloud has quit IRC (Read error: Operation timed out)
09:55 🔗 dashcloud has joined #urlteam
10:40 🔗 dashcloud has quit IRC (Read error: Operation timed out)
10:45 🔗 dashcloud has joined #urlteam
11:34 🔗 dashcloud has quit IRC (Read error: Connection reset by peer)
11:36 🔗 dashcloud has joined #urlteam
11:44 🔗 pwnsrv has joined #urlteam
12:02 🔗 ^F has quit IRC (Ping timeout: 272 seconds)
12:03 🔗 ^F has joined #urlteam
12:30 🔗 GLaDOS has quit IRC (Ping timeout: 272 seconds)
12:30 🔗 ^F has quit IRC (Ping timeout: 272 seconds)
12:31 🔗 deathy has quit IRC (Connection closed)
12:31 🔗 fresco___ has quit IRC (Connection closed)
12:32 🔗 fresco___ has joined #urlteam
12:32 🔗 ^F has joined #urlteam
12:33 🔗 deathy has joined #urlteam
12:35 🔗 GLaDOS has joined #urlteam
12:35 🔗 swebb sets mode: +o GLaDOS
12:35 🔗 dashcloud has quit IRC (Read error: Operation timed out)
12:40 🔗 dashcloud has joined #urlteam
12:49 🔗 dashcloud has quit IRC (Read error: Operation timed out)
12:55 🔗 dashcloud has joined #urlteam
16:05 🔗 aaaaaaaaa has joined #urlteam
18:34 🔗 dashcloud has quit IRC (Ping timeout: 240 seconds)
18:37 🔗 dashcloud has joined #urlteam
19:09 🔗 T31M has joined #urlteam
21:08 🔗 nevon has joined #urlteam
21:09 🔗 nevon has quit IRC (Client Quit)
21:58 🔗 dashcloud has quit IRC (Read error: Operation timed out)
22:02 🔗 dashcloud has joined #urlteam
22:42 🔗 S[h]O[r]T has joined #urlteam
23:28 🔗 z00nx0 has quit IRC (Ping timeout: 272 seconds)
23:30 🔗 z00nx0 has joined #urlteam
23:31 🔗 GLaDOS has quit IRC (Ping timeout: 272 seconds)
23:31 🔗 GLaDOS has joined #urlteam
23:31 🔗 swebb sets mode: +o GLaDOS

irclogger-viewer