|
Message-ID: <20241008002906.GA2378@openwall.com> Date: Tue, 8 Oct 2024 02:29:06 +0200 From: Solar Designer <solar@...nwall.com> To: john-users@...ts.openwall.com Subject: Re: slow progress after --restore On Mon, Oct 07, 2024 at 04:23:54PM -0700, jeff wrote: > >Well, I can only confirm that what you observe is unexpected. We > >checkpoint often, and moreover if you interrupt a session cleanly then > >the latest state is saved at that time. > > > >This could be a bug, or it could be something specific to your usage. > > Is it possibly related to the --fork=22 on the command line? If it's a bug, then of course it could be related to anything, until we know what it is. However, --fork isn't supposed to cause this problem. > Is it possible that the 'rule' starts running from the start when restarted? This isn't supposed to be the case - we record both the rule and the place in the wordlist. However, even if it were the case, it would not cause the exact behavior you observe - with fast hashes like NT, it doesn't take long (not anywhere near as long as 8000 seconds) for one rule to complete and advance to the next one. > I know the behavior is odd, which is why I am reporting it, and would > like t see it fixed. > I have observed it several times. > This is for my 64 core amd epyc milan system, if that matters. > > Tomorrow, (patch tuesday) I will be restarting my computer and restoring > the john session > and I am pretty confident I will see the same issue again :-( Please let us know of your results after the restore tomorrow. When you later start an entirely new session, you may want to omit the --no-log option and examine the log files. Unfortunately, there's no user-friendly way to do that for an existing session you --restore, if you had specified this option when you first started the session. Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.