TIPS,TRICKS AND HACKING ZONE |
HOW TO MAKE YOUR COMPUTER FASTER Posted: 17 May 2011 11:40 PM PDT how to make your computer faster? well,this is so simple.just follow some steps to make faster your pc. 1-go to the command prompt & type: msconfig 2-click on start up & disable all. 3-if you using windows7 or vista,then use the software called ready boost. if you are windows xp users,then go to computer properties>advance>performance>settings>advance>virtual memory,now set the volume 20% more than recommended. 4-increase pagefile of your computer.click on my my computer,click on the c:// drive,go to the properties of c drice & click on change virtual memory,now set the space how much you wana use for temp.memory. 5-always delete your temp.file,click on start,go to run & click on it,type in box:%temp% & hit the enter.so many files will open,select all & delete. 6-again go to start,run,type in box:recent & hit the enter select all & delete. 7-disable search indexing,go to my computer,right click on c drive,click on properties,check free to allow files on this drive to have contents indexed....,now click on ok & close it. 8-download windows washer software. 9-clean your disk.go to start, all programms,accesories,system tool,disk clean up choose the c drive & click on clean.same with other drive. 10-disk dgfr once in a week.go to start,all programms,accesories,system tool,disk degfragment,click on c drive & second click on degfragment.it will be start,let it be finish,same with all other drives. that's it friend. source:http://www.learntohack.webnode.com |
HOW TO PHYSICAL ACCESS TO LINUX SYSTEMS Posted: 17 May 2011 01:06 PM PDT From a Physical Security (PHYSSEC) perspective, problems do not really begin until attackers have their hands on a machine. Having suitable access controls to prevent direct access and policies in place to prevent social engineering will help ensure that attackers are kept at a safe distance. Linux is a robust OS, but it is still vulnerable to hardware dangers that may lead to damage on its physical drives or power losses that may cause data corruption. Therefore, in addition to access controls, server rooms should include the following items to ensure integrity and availability and provide protections from power outages, power anomalies, floods, and so on: • Adequate air conditioning for all servers at peak utilization • Suffi cient power, UPSs, and PDUs • Raised fl ooring Social Engineering Social engineering is not particularly a Linux thing, but it does apply. People are often the weakest link in security, and Linux is not immune to this problem. Very sensitive servers should, therefore, be contained within a locked server rack, thus providing an additional layer of access control and protecting highly sensitive equipment from semitrusted personnel. Furthermore, servers should always be contained in a suitable environment, having at least the following access controls to protect security: • Keycard access to server room allowing only authorized personnel • Real-time cameras and video recording equipment to guard all servers and archive activity • Locking server rack for highly sensitive servers Although serious social engineering can take the form of uniformed workers and contractors with business cards and badges, keep in mind it can also occur in the form of interviewees, new hires, temporary employees, or interns doing low-level jobs. Preventing Social Engineering Considering the potential consequences, the best plan is to stop would-be attackers at the beginning. Prospective entrants to server rooms, especially visitors or contractors, should always be vetted to verify they are expected and have sufficient approvals. Any guests or contractors should be supervised at all times while in the server room. They should never be left unattended. Security awareness training for all personnel will also go a long way toward assuring such security processes are adhered to. Although secure processes and security awareness training will reinforce such concepts, unauthorized physical access is still best hindered by • Maintaining least privilege physical access controls by locking vital areas and providing unique keys only to specifi c personnel who need access • Performing background checks, both criminal and fi nancial, prior to granting physical access • Designing the route used to access systems such that it passes more than one employee, especially employees with access privileges to the respective systems • Mixing physical locks with more high-tech ones, so hacking the access control system does not grant access to places that also require a key. CONSOLE ACCESS Once attackers have access to the Linux server console, you can still put up several potential barriers other than just the root password. All barriers have notable weaknesses, however, that require review and mitigation. Stealing/Changing Data Using a Bootable Linux CD Once an attacker has gained physical access, getting into a box can be as simple as booting to a CD-based Linux distribution, deleting the root user account password in the /etc/shadow file (or replacing it with a known password and salt), and booting into the system, normally with full access. This can be accomplished step-by-step as follows: 1. Reboot the system and confi gure it to boot from the CD-ROM. 2. Boot the system into the bootable Linux distribution, such as one of the following: • Backtrack2 (http://www.remote-exploit.org/backtrack_download.html) • Knoppix-STD (http://s-t-d.org/download.html) 3. Open a root command shell. 4. Create a mount point by typing the following mkdir mountpoint, which will create a directory called mountpoint. This is where the fi le system will be mounted. 5. Determine the type of hard disks (SCSI or IDE) on the system. SCSI drives will be represented by sda, sdb, sdc, and so on, whereas IDE drives are represented by hda, hdb, hdc, and so on. To determine the disk type, type fdisk –l or look through the output of the dmesg command. Sometimes you'll need to try several approaches. 6. Determine the partition on the disk to be mounted. Partitions on the disk are represented as sda1, sda2, sda2, and so on, for SCSI drives and hda1, hda2, hda3, and so on, for IDE drives. Identifying the correct partition that contains the /etc/shadow fi le (always the root "/" partition) can be trial and error, especially if numerous partitions exist on the system, but it is usually one of the fi rst three partitions. 7. Type mount /dev/sda# mountpoint, where /dev/sda# is your root partition (sda1, sda2, sda3,…), and mountpoint is the directory you created. 8. Change to the /etc directory on your root partition by typing cd mountpoint/ etc. 9. Use your favorite text editor (such as vi) to open the etc/shadow fi le for editing. 10. Scroll down to the line containing the root's information, which looks something like: root:qDlrwz/E8RSKw:13659:0:99999:7::: 11. Delete everything between the fi rst and second colons, so the line resembles this one: root::13659:0:99999:7::: If password complexity is enabled on the system, deleting the root password will not allow you to successfully log in to the system using a null password. A known password meeting complexity requirements using the same encryption methodology must be copied and pasted in place of the old root password. 12. Save the fi le and exit your editor. 13. Type cd to return to the home directory. 14. Type umount mountpoint to unmount the target file system. 15. Type reboot to reboot the system and remove the bootable Linux distribution CD from the drive. 16. Now the system can be accessed as root with no password (or the known password). source:http://www.learntohack.webnode.com |
You are subscribed to email updates from Tricks,Tips and Hacking Zone To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |
0 comments:
Post a Comment