Congrats, Ray! Looks nice. Wish I had some good suggestions for you for your password puzzle...
thx, I think it means that there's a set of universal desktop document libraries somewhere that every LOS Application uses for unified document saving/opening, and in there is key to this. It's an interesting implementation, no encryption, but it makes it useless for importing files into LOS without writing an LOS app.
It means that unless I just want to pass a plain text file to LPW, if I want to import something into LOS, I have to write some app in LOS that copies stuff to the clipboard so it can be pasted into things like LisaWrite. So that's a bit unfriendly.
It doesn't protect the files in a forensic way, you can still read the data, but good luck interpreting it.
I've used the tracelog to capture when LOS tries to open a passworded document, so I have the assembly dump somewhere, just have to read through ~300-500MB worth of logs to find it and then figure out the algorithm it uses. It doesn't seem to be complex, but still, externally from outside of LOS, it would need a lot of info to remove the password. I'd need to figure out all the data that's checkedsummed. Is it just the document bytes, or also parts of the extent, such as the dates? Is the file id also used? etc. Once I can generate a checksum externally, then I can overwrite the password entry and remove the password.
Since the password is also hashed, it may be possible to recover it if it's less than 7 chars, but maybe not.
