On 10 December 2012 02:42, shawn wilson <[email protected]> wrote: > On Sun, Dec 9, 2012 at 7:42 AM, Christian Brabandt <[email protected]> wrote: > >> Possibly you can write a script, that feeds various combinations to vim >> and checks, whether the file got decrypted. That sounds like a fun >> exercise. >> > > Don't write a script to do this. Don't use vim to test the crypt. I > had a brief thought about writing a simple c program but here's the > thing, If you can download a program that goes through x passwords per > second and your program goes through x-100 passwords per second, and > you're looking at a length of only 4 with ~96 keyboard keys, you're > looking at 4^96 possibilities. So do the math for the difference that > can make. If an optimized script does 1 million per second and your > does 999,999,000 per second - and that's .000001% of a difference in > algorithm - you're liable to be much worse.
Is it not 96^4 possibilities? A much smaller number: ~85 million. A quicker and dirtier approach might suffice. Or you could try to socially engineer yourself, a tired vimmer might have the capslock on and type ':X' instead of ':x' and not notice the prompts, so it might be worth trying ':X', ':x' or similar. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
