...are measured in units that are smaller than micrometer (one tenth of millimeters), grows every day. It is very clear that the smallest imprecision affects the work of hard drives. Memory devices are also often damaged when computers are accidentally dropped. Can you afford taking the risk of losing data stored on your hard drive in every 5-6 years? Regular backups really help in case of hardware troubles. Hard disk failures do not mean that data is lost forever if you have the opportunity to take the latest version of your data from safe storage and continue using it after any kind of hardware failures. 4. Power failures There are two adversary effects of power failures. When you are halfway through writing a long article and you have not saved it yet, then in case of power going out you lose your data. This is perhaps the simplest example but imagine working with sophisticated databases or creating detail-rich graphic illustrations...you get the idea what can happen if you lose power during working. Another, even deeper problem may arise when power failures affect operation systems or hardware of computers. Shutting computer down suddenly without proper shutdown procedures may cause problems with rebooting operation system later. These operation system problems cause chain reaction and your data might not be accessible any more. Sudden changes in voltage may damage many different computer parts. Most problems can be solved by changing power supply unit but there are also...
Words: 1336 - Pages: 6
...1. 1. MD5 weaknesses/Creating a rogue CA certificate è The first article mostly talks about the weakness of MD5 hashing algorithm by giving a couple of examples that why MD5 is easy to break. The first example was Microsoft’s windows update. The flame espionage malware created a counterfeit certificate based on the same MD5 hash then computers starts to download malwares instead of updates using the legitimate credential. This is how it was easy to spread over millions computers using Windows operating system. Since then Microsoft started to use SHA1 instead but this is also believed to be broken in near future. Second example was stating that there were two images with one MD5 hash. This could be done by adding near collision blocks repeatedly until the two hashes become the same. This is the main flaw of MD5 which is MD5 collision. One reason that we need to pay attention to this problem is that this could be done within ten hours using Amazon Web Service paying only $0.65 plus tax. These examples convinced people why we should not use the MD5 hash for encryption. From my own research shows that SHA 256/512 is the most popular one for encryption today. Second article is about a report from a group of security experts succeeded to create a rogue CA certificate that can be trusted from all common web browsers. This is done by using the defect of MD5 hash. They did the project to reveal the realistic security problems resulted from some certificate authority that still...
Words: 1129 - Pages: 5
...Sole's Blog SOLVE YOUR IT PROBLEMS FASTER, SAVE YOUR FEET AND GET MORE TIME ON YOUTUBE! * HOME * * ABOUT SOLE VIKTOR * * USEFULL LINKS « How to publish a website with both Anonymous and Forms Based Authentication in ISA 2006 How to configure ISA 2006 with FBA for OWA and NTLM for Outlook Anywhere and Autodiscover in Exchange 2007 » How to place FSMO and Global Catalog roles in Active Directory During installation of Active Directory on a Windows Server 2000/2003/2008 all FSMO roles will automatically be installed on the first server. But Best Practice dictates to move some of theese Flexible Single Master of Operation (FSMO) roles to seperate servers. If you only have one domain controller (not recommended), there is nothing to do since all roles must be on this server, but if you have multiple servers you should move some of theese roles on to more servers. It is also important to be aware of what servers are Global Catalog servers, especially if you have more than one domain and even if only one domain, they will be prefered by applications like Exchange server. It is recommended to place the forest roles on one Domain Controller (DC) and the domain roles on another server. If not all Domain Controllers are Global Catalog servers, it is also important to place the infrastructure master on a server that is NOT a Global Catalog server. Recommended Best Practice setup of FSMO roles. Domain Controller #1 Place the two forest roles on this server. * Schema Master...
Words: 10360 - Pages: 42