I've confirmed that WP for Mac uses the same encryption scheme as WordPerfect 5.1.
Here's how to break it (WARNING-- requires use of OSX command line and some basic
idea of what you're doing. It could be made easier, but I don't have the time to do it. I
take no responsibility for any damages that could be caused by this information. I'm a
lawyer-- I haven't been a regular programmer in years, and while I've confirmed this works
on my 10.3.9 system, YMMV.). (You must have the Developer Tools installed into OSX,
since the program requires compilation. As I didn't write the cracker program, I don't feel
comfortable distributing a mac binary distribution of it. If someone wants to write a script
to simplify this, or contact the original author and get permission to distribute the binary,
you'll be a very popular person, I suspect. I'm sorry, but I don't have the time to use this
program for other people. Find a friend with more command line experience than you do
if it's a problem. I'll answer any questions I can in this forum.)
Go to http://members.aol.com/jpeschel/recovery.htm
and download "wpcrackb.zip."
Unzip it. You should end up with four files -- WPCRACK.C is the one to pay attention to.
Open this file up, and make the following changes (as the program was originally written
for Microsoft C, not ANSI C):
1. Starting at line 60 of WPCRACK.C, change
" if ((max_char >= 32) && (max_char < 127))
"if ((max_char >= 32) && (max_char < 127))
2. Save these changes. *Make sure to save the file into a lowercase name, ie, wppw.c*--
IIRC, a capital C in the extension will screw up the gcc compiler, which will think the
program was written in C++.*
3. Compile the program with "gcc wppw.c" (in Terminal): You'll see these messages:
wppw.c: In function `main':
wppw.c:10: warning: return type of `main' is not `int'
4. You should now have a file called "a.out" in the directory. Rename it with "mv a.out
5. Find the file which is password protected. Copy it to where you can get at it.
6. Make a new copy of the file using "cp" (this will zap the resource fork, which confuses
every password descrambler I've found. KEEP THE ORIGINAL FILE.). ie:
"cp protected protectedwithoutrsrc"
7. Run the program-- it works like this: (you only need the ./ if you aren't in a searchable
./wpcrack protectedwithoutrsrc <ASCII code for what you think the most common
character in the file is>
./wpcrack protectedwithoutrsrc 32
(32 is the ASCII code for space, if you didn't know)
It will give you an output that looks something like this:
One of these things should look like the password to the file (in the above example, it's
"PASS"). Run WP, open the file with
the password, and you're all set.