I wrote a script that waits for a connection and then just sends a shell command
nc -z works great as a ātcp pingā
Hm. Thatās interesting. I never noticed that flag, to be honest. Googling and playing around with it a bit and you could probably use this too, youāre right. Neat.
For me it was easier/quicker to just whip out Python and do it that way (it was all of ten lines), but this netcat feature could be useful in the future, so thanks!
Another good use ā I use nc - z flag for scanning whenever transport is limited somehow and nmap isnāt reliable. I used this on another active box recently.
can someone pm me. Iām having some trouble talking to president Eisenhower. Iāve never done it, iāve already installed more software on my computer than iām really happy with, and itās making me feel all sorts of stupid
Another good use ā I use nc - z flag for scanning whenever transport is limited somehow and nmap isnāt reliable. I used this on another active box recently.
For scanning via nc I always add -w 1 so I donāt have to wait for longer timeouts and -vn to get results and omit dns resolution, eg. scan for the first 100 ports:
@spoppi Yes, agreed, that timeout is important for scanning. Also for those following along at home, notice that @spoppi didnāt need to write the iteration over ports because nc does that. (the reason I had an iteration was because I was periodically pinging a single port)
@quas said:
how is everyone getting a P*K without Agg***ive mode? I can only get M*in mode h******akesā¦ Do I have to guess / brute-force the gr**p id?
LAME LAME LAME REALLY i have been on privsac for almost 6 days i am doing it right it just the stupid thing does not work for me while it works for some of my friends!
@quas said:
how is everyone getting a P*K without Agg***ive mode? I can only get M*in mode h******akesā¦ Do I have to guess / brute-force the gr**p id?
Someone give me somehint of that box, i find a hash or some user using SN** enum, try ik*fo** but dont get anything, i need some technical or keyword for google search
Use connect scans (nmap -sT, ā¦). Will probably help. Another thing: you wonāt see more open ports than you saw from the service where you found the credentials for the connection
Working on the first part and trying to connect. Kind of flying blind with my configuration files and command options though. Upon executing c*****-**d my packets get sent but from the output they arenāt being accepted. Eventually the application reports the āpeer is not respondingā and the application quits. Also I see that the application is connecting to a related yet filtered UDP port (per my Nmap scans). Is this normal behavior? Any hints via DM would be appreciated.