* ss95deco.txt (this resistant)
* ss95deco.cpp (the source code)
What does ss95deco
ss95deco the windows 95/98 decode screen saver guard word. This guard word stands stored gecodeert in the registry.
How I does it aanroep?
ss95deco: uses c:\windows\user.that as an input.
ss95deco export.reg: uses export.reg as an input.
ss95deco h:\userXXX\user.that: uses h:\userXXX\user.that as an input.
Why still windows 95/98 screen saver decoder?
The existing screensaver decoders which I had found did not decode all character between 31 and 127 well. Furthermore they decoded but to maximum passwoord length of 14 characters. Another decoder needed even several traffic-jams the encoded obtain string from the registry.
Since there is a large number of people those their inlogwachtwoord the same have such as their screensaver guard word this tool can be skilful at retrieving of this.
How does it work?
Windows 95/98 store the encoded guard word in the registry:
guard words which exist from characters >31 and <127 become gedecodeert, could not the programme the character recognise put the there <?> for in the place. The maximum password length which recognises become by this programme are 18. Also the bits registry by regedit geexporteerd are supported, this offers therefore the possibility of storing this rapidly and then later the affair to decode.
The windows represented every character the string encoded by two characters in. Each character have a fixed value on a certain spot this way if the first character a ' a ' is this always by the same two characters in the string is represented, independently of the length of the guard word and the following characters. I no algorithm has been possible discover representatie and the place of the character. Because of this I was obliged this to solve with tables. In this programme are present tables therefore 18 which represent the charcters between 31 and 127 with always 2 characters. This is therefore the largest part of the code.
Found bugs mbt the screensaver in OSR2
1 guard word all windows in Uppercase are put, because of this the number of possible codings decreases drastically.
2 Each charachter in the guard word string are represented by each time 2 characters in the encoded string. With as last 2 characters ' 00 ' to conclude the string encoded. This has therefore as a disadvantage that infer the length of the guard word directly is from the encoded string. 3 If you think a guard word established longer than 14 characters to windows that you have established no guard word and therefore on a test will not press in the screen the saver the guard word to ask but simply the screensaver conclude. (MAJOR BUG)
4 Further zit still a buffer overflow, if you establish a guard word that longer is than 19 character then windows on its face go. You get no blue baffle, but simply error report. Unfortunately work afterwards whole no longer good and you have been forced start windows again on.
I can hope that these bugs are obtained in windows 98 from.