pyth0n3

Pannel antenna Realtek RTL8187L functioneaza destul de bine am testat in win xp win 7 si linux Yagi e buna daca esti la munte iar antenna omni are semnal mai slab decat antenna pannel

Exista un tool pt honeypot ===>>> Safe-Honeypot-Hunter

Eu sunt un alien

#1 – 100% FREE targeted traffic pouring in to your websites from around the world, eager to buy what you are selling #2 – To beam with pride as you see your sites on top of Google and even show your friends and family. #3 – To make your site totally IMMUNE to “Google Slaps” so you can sleep at night knowing that your business is secure #4 – To easily make the changes necessary for all this to come true because it wouldn’t be any fun if you had to spend all your time doing the SEO #5 – To become recognized as an SEO expert by peers and competitors… maybe even someone they look to for advice CD1===>> Hotfile.com: One click file hosting CD2===>> Hotfile.com: One click file hosting CD3===>> Hotfile.com: One click file hosting CD4===>> Hotfile.com: One click file hosting CD5===>> Hotfile.com: One click file hosting Password & source default shytex.com

Si eu prefer pidgin dar nu mai exista PPA pt Intrepid Ibex si ramane la version 2.5.2 care nu functioneaza cu yahoo , iar daca incerci sa copilezi ultima version iti cere multe dependencies updated ,multe din care nu am reusit sa le fac update Problema ramane in Ubuntu 8.10 (intrepid ibex) , pt restul de distro se poate face

Features: Show Invisible YM Users Voice chat webcams faders nicknames audibles avatars display images, and more use 15 different encryption. There are two vesion GYache Improved GYach Enhanced

This book show how to change the default system settings and get Ubuntu however you want Optimize: - appearance - speed - usability - security And some other hacks such as : - running Ubuntu from a USB drive - installing it on a Mac - enabling multiple CPUs - putting scripts in menus and panels Go here for ===>> Hacking_Ubuntu md5sum (128 bit) a490d61d5469cc3013f7b3b1fcbc1da9 No password request Reader .chm Unix/Linux based ===>>> xchm

Thanks ! useful things for work

Am terminat de citit asta , pe care il intereseaza Take the book here =====>>>Attack_Simulation_and_Threat_Modeling Summary: Threat Vectors and Attack Signatures Attack Virtualization and Behavioural analysis Security Event Correlation and Pattern Recognition Exploratory Security Analytics and Threat Hypothesis Machine Learning Algorithms

Sunt mult mai importante cunostintele acumulate decat sa treci un examen cu success si sa nu stii de l-ai trecut Vad prea multi care lucreaza in anumite domenii doar pt ca au niste diplome, dar sunt paraleli == 0 Pe mine nu ma angajeaza nimeni nicaieri pt ca nu am diploma E o prostie cum functioneaza tot sistemul asta btw pyt0n3 have no fu**ing school

Log Analysis

ThreatExpert is an advanced automated threat analysis system designed to analyze and report the behavior of computer viruses, worms, trojans, adware, spyware, and other security-related risks in a fully automated mode. Threatexpert file scanner VirusTotal is a free virus and malware online scan service Virustotal NoVirusThanks Security Solutions and Information Technology. Security Software to protect your pc from trojans, viruses and any other malicious threats Multi-Engine Antivirus Scanner Norman’s innovative SandBox® technology detects and isolates existing and zero day threats before they infect your system Use a virtual appliance , let the virus execute its payload Use an isolate environment where the file may do whatever it wants You can upload any file you want, the file wil be executed and a few minutes later you will get a report of the analysis in your mailbox The solution is simple according to Norman and that is "Let the malware execute its game.Then control the game!" Sandbox analysis The BitBlaze project aims to design and develop a powerful binary analysis platform and employ the platform in order to (1) analyze and develop novel COTS protection and diagnostic mechanisms and (2) analyze, understand, and develop defenses against malicious code Bitblaze Malware analysis

ISBN-10 / ASIN: 1847194966 | 2010-04-07 | PDF | 224 pages | 5.7 Mb Arm yourself to destroy UI and javascript bugs Expand your toolkit by learning to use Firebug to help you monitor, debug, develop and edit web pages on the fly Create your own Firebug extensions and learn about popular third-party extensions Covers javascript, AJAX, and CSS development Covers all of Firebug’s features Clear explanations with easy-to-follow examples of HTML and JavaScrip Download: Hotfile.com: One click file hosting: Firebug.1.5.Editing.Debugging.and.Monitoring.Web.Pages.rar Source & default password shytex.com

Authors: Barrie Sosinsky Description Everything you need to set up and maintain large or small networks Barrie Sosinsky Networking Bible Create a secure network for home or enterprise Learn basic building blocks and standards Set up for broadcasting, streaming, and more The book you need to succeed! Your A-Z guide to networking essentials Whether you’re setting up a global infrastructure or just networking two computers at home, understanding of every part of the process is crucial to the ultimate success of your system. This comprehensive book is your complete, step-by-step guide to networking—from different architectures and hardware to security, diagnostics, Web services, and much more. Packed with practical, professional techniques and the very latest information, this is the go-to resource you need to succeed. Demystify the basics: network stacks, bus architectures, mapping, and bandwidth Get up to speed on servers, interfaces, routers, and other necessary hardware Explore LANs, WANs, Wi-Fi, TCP/IP, and other types of networks Set up domains, directory services, file services, caching, and mail protocols Enable broadcasting, multicasting, and streaming media Deploy VPNs, firewalls, encryption, and other security methods Perform diagnostics and troubleshoot your systems Download: Hotfile.com: One click file hosting: revskill_Networking Bible.rar Source & password default shytex.com

Publisher: Apress | ISBN: 1590599810 | edition 2008 | PDF | 417 pages | 20,3 mb You’ve long been enamored with the Python language, and have mastered its many nuances. Yet something seems to be missing—a productivity boost that you know is possible but you’re not sure how to go about it. This was the sentiment of so many developers before discovering Agile programming paradigm, which embraces concepts such as automation, effective code management, and test–driven development. Foundations of Agile Python Development is the first book to apply these sought–after principles to Python developers, introducing both the tools and techniques built and supported by the Python community. Authored by Jeff Younker, a well–known member of Python’s agile community who is perhaps best known for his creation of a popular Python testing framework, this book is sure to be a hit among readers who may have reached their limits of knowledge regarding the Python language, yet are seeking to improve their understanding of how sound processes can boost productivity to unparalleled heights. Download : Hotfile.com: One click file hosting: 4653.rar Source & password default shytex.com

Publisher: Course Technology 2009 | 384 Pages | ISBN: 1435454235 | PDF | 10 MB HTML, XHTML, & CSS For the Absolute Beginner provides beginner level programmers with an entry level introduction to HTML, XHTML and CSS. This book serves as a primer for client-side web development. To make learning fun, the book uses a games-based instructional approach that provides working examples that demonstrate how HTML, XHTML and CSS can be applied to the development of web pages and sites. HTML, XHTML, & CSS For the Absolute Beginner is a fun and easy way for a beginner to master web development through the creation of computer games. Download: Hotfile.com: One click file hosting: HTML__XHTML__and_CSS_for_the_Absolute_Beginner.rar Source & default password booktraining.org

Pai el crede ca e o pagina web ssh-ul Si daca pui captcha nu se mai poate face brute-force

For years, on security forums and mailing lists, if you ever dared to suggest changing SSH’s default port (TCP 22) the “security by obscurity” crowd would come out of the woodwork and nail your ass to the Cross of Righteousness for having the unmitigated gall to even dare utter such heretical nonsense. Unfortunately for these dogmatic True Believers, changing the ssh daemon’s default listening port is such an incredibly effective method for avoiding ssh scans and brute force password attacks that it’s starting to show up in HOWTO security articles as a method for hardening your system. For example, see this article at Linux Magazine. But the Port 22 Crowd will not leave well enough alone. Although they haven’t abandoned the “security by obscurity” mantra completely, they’re now using the following argument with increasing frequency: NEVER CHANGE YOUR SSH PORT! If an exploit comes out that can crash SSH locally, a local unprivileged user on your system could crash SSH and start their own daemon on the SSH port > 1024 and capture your usernames and passwords. If you want SSH on a different port, do this with firewall rules. Note that ALL CAPS is required when raising this alarm. Also note that if you require users to connect with SSH in the first place, it’s not going to do them a helluva lot of good to crash SSH. If you have users who actually sit down at the keyboard of the physical system, that’s another problem entirely. Why bother with crashing SSH when they can slip a bootable CD into the tray and bounce the box? And of course if you choose a port other than 22 but less than 1024 you can avoid this issue completely. However, “changing the port with firewall rules” struck me as a novel idea (maybe I’m just stupid but it never occurred to me before) and set me to wondering how you would do such a thing, since I’ve always taking the easy way out by changing or adding ports in sshd_config. So I sat down with iptables and experimented a bit. I came up with the following method. If everything you have is behind NAT, the problem can be reduced to simple port forwarding. If not, there are a few hoops you need to jump through. Be advised the iptables rules presented below assume you have a blank set of rules. Just copying and running them against an existing set of rules probably won’t work. First, set SSHD back to the default port 22. Next, figure out what port or ports you want to do SSH over. We’re going to use 44, 88, and 8188 here. Now we take care of the Hypothetical Evil Unprivileged User by not accepting anything over those ports in the first place. This is only effective for port 8188 but we’ll do all three ports for the sake of completeness: #~iptables -t filter -A INPUT -p tcp -m multiport --dports 44,88,8188 -j REJECT --reject-with tcp-reset Then, pick a number between 1 and 4294967295. This will be the value of the iptables “mark” we use for ssh. I’ll use 0×2200 (8704), just because it’s ssh-ish, but any positive integer in that range will do. We’re going to tell iptables to reject anything without this mark coming into port 22. #~iptables -t filter -A INPUT -p tcp -m tcp --dport 22 -m connmark ! --mark 0×2200 -j REJECT --reject-with tcp-reset I would prefer to DROP these packets rather than REJECT them, but more on that later. Now we’ll tell iptables what ports we will accept for ssh. #~iptables -t filter -A FORWARD -p tcp -m multiport --dports 44,88,8188 -j ACCEPT In the “mangle” table we slap our mark on these packets. #~iptables -t mangle -A PREROUTING -p tcp -m multiport --dports 44,88,8188 -j CONNMARK --set-mark 0×2200 Finally, in the “nat” table we tell iptables to send the marked packets back to port 22. #~iptables -t nat -A PREROUTING -p tcp -m multiport --dports 44,88,8188 -j REDIRECT --to-ports 22 The packets go back to the INPUT rule and, since they’re marked correctly, are sent to the SSHD process listening on port 22. We have done exactly what was recommended, i.e. we have indeed changed the default ssh port with firewall rules alone (and without NAT). And yet, ssh still listens on port 22! I must admit this appeals to me on a number of levels, not the least of which is that it has all the hallmarks of a slick little hack. Secondly, it definitely takes a load off of the ssh daemon since it’s listening on one port instead of three (in reality I have ssh listening on seven ports). However, this is done at the expense of complexity, which has yet another group of True Believers who are fond of chanting “COMPLEXITY IS THE ENEMY OF SECURITY” at the slightest provocation. This is another religion I have never bought into (it may be the same group since increasing complexity generally tends to increase obscurity). Well, fuck them, you can’t please everyone. Besides, I use the most bizarre, complex combination of port forwarding and routing you’d ever want to see. Most days I have a hard time understanding it myself. It keeps me sharp. I am almost 100% certain this wouldn’t please a “real” firewall administrator. They’re mostly overpaid Certified Cisco Clowns anyway. It would never even occur to them to actually use iptables. But what we have done in essence is put all our trust in iptables working “just right”. And we’re betting the next time there’s an update to the netfilter core code (or the kernel) everything will still work. I’ve been around iptables/netfilter far too long to ever bet on that. Sorry, fellas, “once bitten, twice shy” and all that. Then there’s the TCP reset thing. Can it be bypassed? Web filtering appliances that use span ports and two-way TCP resets work fine when everyone “plays by the rules of TCP/IP” (actual statement from Web filter appliance vendor Sophos), but the Bad Guys don’t usually play by the rules. The alternative, DROP-ing the packet, lets anyone scanning our system with tools like nmap know with absolute certainty that SSHD is listening on port 22 since it will show up as “filtered”. This makes TCP resets the lesser of two evils, but it’s still evil. In the end analysis, isn’t sending a reset from an “open” port just another instance of “security by obscurity”? Not that I care, that was a purely rhetorical question. And what about attacks against iptables connection marking (CONNMARK) itself? Do they even exist? Am I opening myself up to an unknown exploit vector? Do I have to take additional measures to avoid spoofing or brute forcing or some other method (fragmented/crafted packets, maybe) to get around my firewall rules? Even though we followed this fellow’s advice, there are too many open questions and it appears that just changing the port in sshd_config is still a simple and effective countermeasure. It’s worked for me for over ten years. I have escaped all 0day SSHD vulnerabilities for over a decade and no one ever tries to brute force passwords on my box. It doesn’t happen because port 22 isn’t open. Simple. Effective. Source: proxyobsession

From the category of log based tools I have chosen to present fail2ban because I consider it to be the best available log based brute force blocker. Basically, as any other log based brute force blockers, fail2ban will monitor the system log files and when certain configured events occur they will trigger fail2ban to block the offending host. Here are the main features of fail2ban: running as daemon (no delay to take actions as in cron based tools). can use various methods to block the attack: iptables (this is the default, and will most certainly be the best choice for most users) TCP Wrappers (/etc/hosts.deny): this might be particular useful if you are running a VPS that has no access to iptables rules. any other method you might need to implement in your firewall setup (you will have to define the rules yourself in this case). can handle more than one service: sshd (default), apache, vsftpd/proftpd, etc. can send e-mail notifications. can ban IPs for a limited amount of time and since 0.6.1 can also permanently ban hosts. The installation is not at all complicated as the author provides packages for major linux distributions. I will show how we can install fail2ban on Debian. By the way the Debian package is different than the source package you can find at the project page. This is because the author is closely collaborating with Debian maintainers to conform its software to the Debian rules and have it in the official Debian sources. This is very nice! If we want to install fail2ban on a Debian system all we have to do is: apt-get install fail2banthis will take care of the dependencies you might not have on the system (python, iptables, lsb-base). Once installed, it will be started automatically. The configuration file is located in /etc/fail2ban.conf. It will enable by default the protection against SSH brute force attacks. The configuration file contains each available parameter excellently commented and that should be the only documentation you will need for fail2ban. Compared with other software, I found the need to change very few parameters from the default. Here are some of the important parameters from the main section: [DEFAULT] maxfailures = number of failures before IP gets banned. Defaults to 5. I like to lower this to 3: maxfailures = 3 bantime = number of seconds an IP will be banned. If set to a negative value, IP will never be unbanned (permanent banning). Defaults to 600 (10 min). bantime = -1 ignoreip = space separated list of IP’s to be ignored by fail2ban. No default. I like to add my own static management ips here just in case… ignoreip = 192.168.0.1 All fail2ban actions are logged and can be reviewed. The log file is defined using: logtargets = /var/log/fail2ban.logThe SSH section works perfectly out of the box being aware of Debian log files names, etc: [sSH] enabled = true logfile = /var/log/auth.log port = ssh timeregex = S{3}s{1,2}d{1,2} d{2}{2}{2} timepattern = %%b %%d %%H:%%M:%%S failregex = : (??:Authentication failure|Failed [-/w+]+) for(?: [iI](?:llegal|nvalid) user)?|[ii](?:llegal|nvalid) user|ROOT LOGIN REFUSED) .*(?: from|FROM) (?:::f{4,6}?(?PS*)Here we can see the log file fail2ban will monitor for SSH attacks (/var/log/auth.log), the port that will be used to block the hosts (they will still be able to communicate with other protocols with our host even after ssh blocking) and also the regular expressions that will trigger fail2ban. Besides the SSH section that is enabled by default the configuration file contains other usable sections for other programs (you just have to enable them as they default to disabled): SASL, Apache, ApacheAttacks, VSFTPD, PROFTPD. This can also be the starting point for writing your own rules targeted for any program you might need. Here are the iptables definitions that will actually block the offending hosts: fwchain = INPUT fwstart = iptables -N fail2ban-%(__name__)s iptables -A fail2ban-%(__name__)s -j RETURN iptables -I %(fwchain)s -p %(protocol)s --dport %(port)s -j fail2ban-%(__name__)s fwend = iptables -D %(fwchain)s -p %(protocol)s --dport %(port)s -j fail2ban-%(__name__)s iptables -F fail2ban-%(__name__)s iptables -X fail2ban-%(__name__)s fwcheck = iptables -L %(fwchain)s | grep -q fail2ban-%(__name__)s fwban = iptables -I fail2ban-%(__name__)s 1 -s -j DROP fwunban = iptables -D fail2ban-%(__name__)s -s -j DROPfwstart will create when starting the program for each of the defined active sections a different iptables chain. This will be called fail2ban-(name_of_section), for ex: fail2ban-SSH, fail2ban-VSFTPD, etc. iptables -L -n Chain INPUT (policy ACCEPT) fail2ban-SSH tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 Chain fail2ban-SSH (1 references) RETURN all -- 0.0.0.0/0 0.0.0.0/0On program exit these chains are deleted. There is no persistence in fail2ban. If for any reason the program is restarted it will rescan the log files for failed attempts (only events newer then findtime - def 600) and it will add them to the active list. This is not at all a big limitation and I would not care about this… but just that you are aware that if you restart the program you will start fresh. The action that is taken when a host is banned will just add a new iptables rule in the program chain that will drop the traffic for the attacker. Let me exemplify this: we are being attacked by a host with the IP 192.168.0.200 (just a private ip for the sake of the example) In system logs we see the following (/var/log/auth.log): sshd[6787]: Did not receive identification string from 192.168.0.200 sshd[13299]: Invalid user lpd from 192.168.0.200 sshd[13299]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.0.200 sshd[13299]: Failed password for invalid user lpd from 192.168.0.200 port 41458 ssh2 sshd[13324]: Invalid user lpa from 192.168.0.200 sshd[13324]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.0.200 sshd[13324]: Failed password for invalid user lpa from 192.168.0.200 port 41689 ssh2At this time fail2ban has seen enough authentication errors (with maxfailures = 3) and in fail2ban log file we will see: /var/log/fail2ban.log 2006-07-01 16:06:39,261 INFO: SSH: 192.168.0.200 has 3 login failure(s). Banned. 2006-07-01 16:06:39,287 WARNING: SSH: Ban (permanent) 192.168.0.200We have started with empty iptables rules that look like: iptables -L -n Chain INPUT (policy ACCEPT) fail2ban-SSH tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 Chain fail2ban-SSH (1 references) RETURN all -- 0.0.0.0/0 0.0.0.0/0Meaning that all the SSH traffic will just pass thru the fail2ban-SSH chain without any change. Once fail2ban has blocked our attacker 192.168.0.200 it will add a new iptables rule that will drop SSH traffic from this host. After this the rules will look like: iptables -L -n Chain INPUT (policy ACCEPT) fail2ban-SSH tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 Chain fail2ban-SSH (1 references) DROP all -- 192.168.0.200 0.0.0.0/0 RETURN all -- 0.0.0.0/0 0.0.0.0/0Using iptables to block the offending hosts is probably the best way to do this (and can be easily integrated in any existing iptables firewall), but as I said there are other methods available that might be useful in some cases (hosts.deny might be the only choice for VPS owners that don’t have access to iptables). You can look into the examples that come with fail2ban for how to easily implement this. Sources: using-fail2ban-to-block-brute-force-attacks MANUAL 0 8

Title: The Art of Debugging with GDB, DDD, and Eclipse Authors: Norman Matloff Peter Jay Salzman Description Debugging is of central importance to successful software development, and yet many beginning programmers are unaware of the techniques they can use to reduce the time they spend finding and fixing programming errors. GDB, a popular open source debugger, allows a programmer to trace program execution line by line, set breakpoints, inspect variables, and look at what the program is doing at any given time. Using an assortment of real world coding errors “from simple typos to major logical blunders “The Art of Debugging with GDB and DDD discusses how to manage memory, understand core dumps, and trace programming errors to their root cause. The book covers topics other debugging books omit “such as threaded, server/client, GUI, and parallel programming “as well as how to avoid common debugging pitfalls. Readers also learn about techniques and tools they can use to prevent errors, saving themselves valuable time and effort. Download: Hotfile.com: One click file hosting: revskill_The Art of Debugging With GDB and DDD and Eclipse.rar Source & Password default shytex.com

Pai nu am reusit sa inteleg si eu , nu cred ca unul singur a reusit sa scrie atat de mult , uite aici site-ul official O'Reilly Media - Bookstore: Complete List oricum sunt mai multi autori

English | 640×480 | DIVX | 25fps | MP3 192Kbps | AVI | 700MB Genre: Document This film explores the origin of true hackers vs. today’s computer criminals by following the adventures of Adrian Lamo and other well intentioned hackers, who found security holes and pointed them out so they might be fixed, only to eventually be arrested. Commonly thought of as computer criminals and vandals, a true hacker is an innovative thinker able to “hack” himself out of a given problem or situation, whether it be computer related or not. Historically, hackers have accounted for mankind’s greatest inventions and discoveries and yet have repeatedly been persecuted for their new ideas by the powerful and fearful. Experts on cyber terrorism also examine our societal view of the hacker and debate as to whether or not we should recruit and utilize the skills of the helpful hackers to fight future cyber wars, instead of continuing to punish what we do not understand. Download [URL="http://hotfile.com/dl/44086927/6ca2fb3/Hackers_Wanted_DMZ.part1.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part1.rar[/URL] [URL="http://hotfile.com/dl/44086983/6b56d3c/Hackers_Wanted_DMZ.part2.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part2.rar[/URL] [URL="http://hotfile.com/dl/44087025/174c568/Hackers_Wanted_DMZ.part3.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part3.rar[/URL] [URL="http://hotfile.com/dl/44087058/c907d07/Hackers_Wanted_DMZ.part4.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part4.rar[/URL] [URL="http://hotfile.com/dl/44087121/adcf242/Hackers_Wanted_DMZ.part5.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part5.rar[/URL] [URL="http://hotfile.com/dl/44087157/d8a059a/Hackers_Wanted_DMZ.part6.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part6.rar[/URL] [URL="http://hotfile.com/dl/44087184/6b89077/Hackers_Wanted_DMZ.part7.rar_shytex.com.html"]Hotfile.com: One click file hosting: Hackers_Wanted_DMZ.part7.rar[/URL] Source & default password shytex.com

Useful Hacker Techniques: Which Part of Hackers’ Knowledge Will Help You in Efficient IT Administration? Everyone has heard about hackers. It is commonly known that their jobs differ from system administrator jobs. However, things they do in their darkened rooms are definitely interesting and worth knowing. Many of the techniques they use are very useful in everyday administration tasks. A Hackers’ knowledge is considered to be valuable, both by system creators and common users. As an IT security auditor, I know that administrators do not have to be taught how to be a hacker; it is often enough to show them one simple, but very interesting tool or technique, to change the point of view on their own IT environment. Topics covered in this session help you to feel for the hacker’s role and evaluate your network from their point of view. Be careful — this session is designed for IT and Security professionals who want to take their skills and knowledge to the next level. After this session you will be familiar with hacker techniques which can be useful to protect yourself against. Speaker(s): Paula Januszkiewicz Download : Hotfile.com: One click file hosting: LFH.part1.rar Hotfile.com: One click file hosting: LFH.part2.rar Source & Default password shytex.com

Use nmap to scan ip ranges , for vnc servers , and save the scan to a log file #!/usr/bin/python #Author: pyth0n3 #Blog: http://pyth0n3.blogspot.com/ #Date: 20.06.2010 #Use nmap to scan ip ranges for open vnc server then save the results to log file #Need python-nmap library #Download module : wget http://xael.org/norman/python/python-nmap/python-nmap-0.1.4.tar.gz #Install : tar xvzf python-nmap-0.1.4.tar.gz && cd python-nmap-0.1.4 && sudo python setup.py install #Must specify the range , by default is '192.168.1.0/24' #The log file must be created in the local directory, by default is 'log' import nmap import time map = nmap.PortScanner() print '.............Start scanning ................' time.sleep(5) print '.....................this may take a while ..............' time.sleep(10) print '....................................still scanning be patient..............' map.scan(hosts='192.168.1.0/24', arguments='-sV -sS -R -PS5900') map.all_hosts() f = open('log','w') log = f for host in map.all_hosts(): print >> log, ('================================================') print >> log, ('Host : %s (%s)' % (host, map[host].hostname())) print >> log, ('State : %s' % map[host].state()) print >> log, ('================================================') for proto in map[host].all_protocols(): print >> log, ('#################') print >> log, ('Protocol : %s' % proto) lport = map[host][proto].keys() lport.sort() for port in lport: print >> log, ('port : %s\tstate : %s' % (port, map[host][proto][port]['state'])) f.close() print '=====================================================>the scan was finished ,go and check the log file<===========================================' #END

0 centi pt ca nu mi-am propus sa castig bani , toti urasc site-urile cu publicitate De ce as pune-o pe blog la mine?