Trivendra's blog

Fatal error: the system has become unstable or is busy," it says. "Enter to return to Windows or press Control-Alt-Delete to restart your computer. If you do this you will lose any unsaved information in all open applications." You have just been struck by the Blue Screen of Death. Anyone who uses Microsoft Windows will be familiar with this. What can you do? More importantly, how can you prevent it happening? 1 Hardware conflict The number one reason why Windows crashes is hardware conflict. Each hardware device communicates to other devices through an interrupt request channel (IRQ). These are supposed to be unique for each device. For example, a printer usually connects internally on IRQ 7. The keyboard usually uses IRQ 1 and the floppy disk drive IRQ 6. Each device will try to hog a single IRQ for itself. If there are a lot of devices, or if they are not installed properly, two of them may end up sharing the same IRQ number. When the user tries

Over the past few years TCP sequence number prediction attacks have become a real threat against unprotected networks, taking advantage of the inherent trust relationships present in many network installations.   TCP sequence number prediction attacks have most commonly been implemented by opening a series of connections to the target host, and attempting to predict the sequence number which will be used next.   Many operating systems have therefore, attempted to solve this problem by implementing a method of generating sequence numbers in unpredictable fashions.   This method does not solve the problem. This advisory introduces an alternative method of obtaining the initial sequence number from some common trusted services.   The attack presented here does not require the attacker to open multiple connections, or flood a port on the trusted host to complete the attack.   The only requirement is that source routed packets can be injected into the targe