Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

First of all stay cool and try to remember. If you don't remember every detail, a few things you are sure about can help. If you try anything don't do it with the original file, but with a copy.
Did you save to odt?
'Save with password' will encrypt a file with a rather strong algorithm. In specific if the password is not very long, and you remember something about it, there is a chance to attack the encryption using "brute force" algorithms. Unfortunately I cannot recommend a specific software. Hopefully someone else will come with more specific advice.

First of all stay cool and try to remember. If you don't remember every detail, a few things you are sure about can help. If you try anything don't do it with the original file, but with a copy.
Did you save to odt?
'Save with password' will encrypt a file with a rather strong algorithm. In specific if the password is not very long, and you remember something about it, there is a chance to attack the encryption using "brute force" algorithms. Unfortunately I cannot recommend a specific software. Hopefully someone else will come with more specific advice.

Might someone with related experience try to help?
I just know how to test for each one in a collection of probable passwords by user code, and this way pretty much faster than one by one "manually", but I have no evaluated concept of generating the collection from partial knowledge of the PW.

First of all stay cool and try to remember. If you don't remember every detail, a few things you are sure about can help. If you try anything don't do it with the original file, but with a copy.
Did you save to odt?
'Save with password' will encrypt a file with a rather strong algorithm. In specific if the password is not very long, and you remember something about it, there is a chance to attack the encryption using "brute force" algorithms. Unfortunately I cannot recommend a specific software. Hopefully someone else will come with more specific advice.

Might someone with related experience try to help?
I just know how to test for each one in a collection of probable passwords by user code, and this way pretty much faster than one by one "manually", but I have no evaluated concept of generating the collection from partial knowledge of the PW.

In case somebody wants to ease and to also speed-up a bit his (f/m) search for a forgotten password, he may use this provisional spreadsheet for the purpose. On my system it needs about 350 ms to test for a wrong password, and thus about 1 h for the 10000 it is prepared for. I do not know a faster way. The expense in time is due to the 'loadComponentFromUrl' command from the api. It's not a matter of "poor BASIC". If the correct password is found evantually, the delay can be much longer - but that's pure joy then. Proposals concerning support for systematic guessing by user code would be valuable.

First of all stay cool and try to remember. If you don't remember every detail, a few things you are sure about can help. If you try anything don't do it with the original file, but with a copy.
Did you save to odt?
'Save with password' will encrypt a file with a rather strong algorithm. In specific if the password is not very long, and you remember something about it, there is a chance to attack the encryption using "brute force" algorithms. Unfortunately I cannot recommend a specific software. Hopefully someone else will come with more specific advice.

Might someone with related experience try to help?
I just know how to test for each one in a collection of probable passwords by user code, and this way pretty much faster than one by one "manually", but I have no evaluated concept of generating the collection from partial knowledge of the PW.

In case somebody wants to ease and to also speed-up a bit his (f/m) search for a forgotten password, he may use this provisional spreadsheet for the purpose. On my system it needs about 350 ms to test for a wrong password, and thus about 1 h for the 10000 it is prepared for. I do not know a faster way. The expense in time is due to the 'loadComponentFromUrl' command from the api. It's not a matter of "poor BASIC". If the correct password is found evantually, the delay can be much longer - but that's pure joy then. Proposals concerning support for systematic guessing by user code would be valuable.valuable.

(Using the sheet with AOO is basically possible, but there will be some annoying experiences, and the final MATCH will not work. Tested with AOO V4.1.5)

First of all stay cool and try to remember. If you don't remember every detail, a few things you are sure about can help. If you try anything don't do it with the original file, but with a copy.
Did you save to odt?
'Save with password' will encrypt a file with a rather strong algorithm. In specific if the password is not very long, and you remember something about it, there is a chance to attack the encryption using "brute force" algorithms. Unfortunately I cannot recommend a specific software. Hopefully someone else will come with more specific advice.

Might someone with related experience try to help?
I just know how to test for each one in a collection of probable passwords by user code, and this way pretty much faster than one by one "manually", but I have no evaluated concept of generating the collection from partial knowledge of the PW.

In case somebody wants to ease and to also speed-up a bit his (f/m) search for a forgotten password, he may use this provisional spreadsheet for the purpose. On my system it needs about 350 ms to test for a wrong password, and thus about 1 h for the 10000 it is prepared for. I do not know a faster way. The expense in time is due to the 'loadComponentFromUrl' command from the api. It's not a matter of "poor BASIC". If the correct password is found evantually, eventually, the delay can be much longer - but that's pure joy then. Proposals concerning support for systematic guessing by user code would be valuable.

(Using the sheet with AOO is basically possible, but there will be some annoying experiences, and the final MATCH will not work. Tested with AOO V4.1.5)