I have the encrypted .wallet file
And I'm guessing no paper backup?
Using btcrecover with my RTX GPU to bruteforce any possible typos, typos-maps, word combinations, tokens etc.
This stuff supports Armory? Have you tested it? (i.e. create a wallet, give it to btcrecover with 1-2 characters off of the password and see if it can figure it out)
Gave a try to the Finder Outer nice tool to recover root key but since I don't have any characters from it, it would take billion of years to crack
Same test applies.
Look for vulnerabilities with Armory, I could find a fragmented backup vulnerability that indeed impact the version of the wallet (0.88.1). Not sure if it can be exploited or not. If someone could help exploiting this vulnerability or giving pointers, that would be really appreciated.
The fragmented backup vulnerability doesn't erode the security that much. It messes up the SSS setup but there is no real world attack against that. This is all theoretical. The recommendation I stickied here was for people using SSS to proactively redo their backups with the fixed implementation.
At any rate, to even begin exploring this angle, it would mean you have a set of fragmented paper backups. If that's the case, you don't have to crack anything in the first place.
I have a list of possible passwords but its been so long, I'm not sure anymore if its really within the list I could think of
Once you've established that the bruteforce software you're using actually works on these specific Armory wallets, you can start building a strategy to brute force whatever you remember. If you use a typical pattern across all your passwords or use a password manager, that can be useful too. First ensure you aren't wasting energy getting false negatives.