Password hacking
This redirect may meet Wikipedia's criteria for speedy deletion as a very short article lacking sufficient context to identify the subject of the article. See CSD A1.
If this redirect does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this redirect may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to page author: you have not edited the article talk page yet. If you wish to contest this speedy deletion, clicking the button above will allow you to leave a talk page message explaining why you think this redirect should not be deleted. If you have already posted to the talk page but this message is still showing up, try purging the page cache. This page was last edited by Dekisugi (contribs | logs) at 10:04, 1 April 2008 (UTC) (17 years ago) |
Password Hacking
Many systems with password protection store the password in a local file. The password is usually encrypted in some way to make it unreadable. The following example involves Sage, an ancient DOS accounts package, but the technique is general and applies in many other cases.
Sage stores it's password locally in SAGE.PSW as a 10 character string. Make a backup copy first then remove the archive and read-only attributes to gain write access to the file:
copy sage.psw password.bakattrib sage.psw -a -r
Now we can edit the password file using debug:
debug sage.psw-dOC4B:0100 85 8C 89 9A 8F 83 E9 E9-E9 E9 xx xx xx xx xx xx The first six bytes in this example are the encrypted password followed by padding (encrypted spaces) and the terminator. Use debug to change all but the first byte to match the padding. For example: -e101 E9 E9 E9 E9 E9-d100OC4B:0100 85 E9 E9 E9 E9 E9 E9 E9-E9 E9 xx xx xx xx xx xx Now write the edited file back to disk and quit debug: -wWriting 00012 bytes -quit Start the Sage program and try each letter of the alphabet in turn. It will throw you out after 3 invalid entries so simply reload it and continue. In the worst case you will need to reload 8 times. As soon as you discover the new improved single character password you're in. Happy Hacking!