Sinisterly
[Kali Linux] Get access, Find and attack into a network - Printable Version

+- Sinisterly (https://sinister.ly)
+-- Forum: Hacking (https://sinister.ly/Forum-Hacking)
+--- Forum: Tutorials (https://sinister.ly/Forum-Tutorials)
+--- Thread: [Kali Linux] Get access, Find and attack into a network (/Thread-Kali-Linux-Get-access-Find-and-attack-into-a-network)

Pages: 1 2 3 4 5 6


RE: [Tutorial] Find potential targets and informations on your network - soldi3r - 01-01-2013

(12-31-2012, 10:22 PM)hunt3r972 Wrote: which way did you use for wpa cracking ??

I tried dictionary and brute force both...But failed.


RE: [Tutorial] Find potential targets and informations on your network - hunt3r972 - 01-02-2013

If the password is not referenced in the dictionnary, it will not work. This is way it failed.
Brute force take too much time because it must generate every possibilities to find the key. You can reduce the time of cracking by giving some informations if you know the chars or the length of the password for example. But has I always say, WPA2 is very hard to crack and most of the time it will fail

[I added some informations for wep/wpa cracking to help new people to know what is performed by the command line used]


RE: [Tutorial] Find potential targets and informations on your network - yimcooldude - 01-02-2013

after running this nmap command, you'll know what services are running. search if those services have public, remote exploits. if they have then yes, you can metasploit. if no, you need to get creative and find other way in ???


RE: [Tutorial] Find potential targets and informations on your network - yimcooldude - 01-02-2013

after running this nmap command, you'll know what services are running. search if those services have public, remote exploits. if they have then yes, you can metasploit. if no, you need to get creative and find other way in ???


RE: [Tutorial] Find potential targets and informations on your network - hunt3r972 - 01-02-2013

I think that you will have to learn some programmation language and find the fails by yourself (and write your own exploit by the same way). I haven't enough knowledge to explain that.


RE: [Tutorial] Find potential targets and informations on your network - hunt3r972 - 01-02-2013

I think that you will have to learn some programmation language and find the fails by yourself (and write your own exploit by the same way). I haven't enough knowledge to explain that.


RE: [Tutorial] Find potential targets and informations on your network - JackDaniels - 01-16-2013

Great tutorial! Needs more people like you that are willing to help out new members!


RE: [Tutorial] Find potential targets and informations on your network - JackDaniels - 01-16-2013

Great tutorial! Needs more people like you that are willing to help out new members!


RE: [Tutorial] Find potential targets and informations on your network - JackDaniels - 01-16-2013

Great tutorial! Needs more people like you that are willing to help out new members!


RE: [Tutorial] Find potential targets and informations on your network - snowblind956 - 01-17-2013

Excellent tutorial! I'm sure it will really help a lot of people. I'd like to offer a couple tips for finding out what's on your network, you can feel free to just ignore me if you'd like. I use fping to do a ping sweep of my target network, and I use several nmap commands to port scan. To ping sweep a range I use this command:
Code:
fping -a -g 192.168.0.1 192.168.0.254>filename.txt
This scans a whole subnet and makes a nice clean text file for our results. For my nmap syn scan i use:
Code:
nmap -p- -PN 192.168.0.10
to scan a single ip. Without the -p- nmap only scans the 1000 most common ports, and -PN skips the host discovery and just scans all ports as if they were alive. This takes a little longer but it's more thorough. Also don't forget to scan for UDP as well as TCP with at least this:
Code:
nmap -sUV 192.168.0.10
I don't use all of the extra's for udp only because it does take a lot longer than tcp, and if you're feeling like you could find more i urge you to look up different kinds of scans such as xmas and null. Also don't forget to vulnerability scan with a vulnerability scanner like nessus, nexpose, or openvas!