|
Message-ID: <19A586784F3241E2ADF3D0D67B88348D@D9VGLK61> Date: Sun, 29 May 2011 14:10:23 -0500 From: "JimF" <jfoug@....net> To: <john-dev@...ts.openwall.com> Subject: Re: John 1.7.7-jumbo-5 I thought incremental restore simply boiled down to charcount ^ length almost like a number stored in base(charcount) where we simply store the 'digits', but that is simply an assumption I have had and I have never really looked at how the code really stores the data into the restore file. I might have a look at it sometime, and see how hard / easy it would be to reload the ETA data from an inc restore. Jim. ----- Original Message ----- From: "magnum" <rawsmooth@...dband.net> To: <john-dev@...ts.openwall.com> Sent: Sunday, May 29, 2011 1:54 PM Subject: Re: [john-dev] John 1.7.7-jumbo-5 > On 2011-05-29 20:04, JimF wrote: >>>> ETA now working for -incremental runs. (magnum) >>> >>> Only until you stop and restore the job, not sure if that needs to be >>> mentioned. >> >> I saw that, but do not understand why it can not live past a -restore. I >> did not figure that information was really needed in a release notice, >> and hopefully that limitation will be able to be corrected. > > It's explained in this thread: > http://www.openwall.com/lists/john-users/2011/02/23/1 > > I do it by adding a counter, but that counter can't be set properly at a > restore until someone writes code to calculate it from the parameters that > are saved/restored. I looked at it but it would take me days to understand > incremental mode to the extent I could pull it off. > > magnum
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.