They're based on the way ACPI events cause interference in the way ASGS makes Windows API calls via the DBus pipelines. Combine this with the fact ASGS was built with IE6 in mind and you have a problem.djrbk wrote:QUOTE (djrbk @ Sep 22 2010, 11:40 PM) Somebody PM me your Allegiance hacks.
First update your system to IE8 or better so the about dialog causes memory corruption on delayed loading of the appropriate dll, then press and hold the power button for five seconds while logging in.
See, your computer is really a series of tubes and ACPI can clog them so ASGS can't DES the encryption primary key via the Windows Encryption Service. Just clog them enough and bam! ASGS times out on checking its local HTML5 caches and activate your mutex without actually receiving the encrypted three way handshake. ASGS doesn't check your files and you can play with your ubercharged hvy int of doom.
You may notice some screen flickering when this happens. This is ACPI disabling itself -- an inbuilt security measure indeed. See, ACPI flooding can crash any program, so ACPI disables itself after five seconds allowing properly written systems to recover while the tubes are restored to normal circulation. However, five seconds are enough to bring ASGS's XML parser to its knees and enable the hack.
CSS, set to replace ASGS, has been tested to sustain 10 seconds of ACPI clogging. This should close the analog hole in ASGS.
