jeroen-80
commented
5 years ago And a stack smashing variant after a john --restore:
3: Warning: Only 17 candidates buffered for the current salt, minimum 48
needed for performance.
3: Warning: Only 38 candidates buffered for the current salt, minimum 48
needed for performance.
3: Warning: Only 17 candidates buffered for the current salt, minimum 48
needed for performance.
3: Warning: Only 38 candidates buffered for the current salt, minimum 48
needed for performance.
3: Warning: Only 6 candidates buffered for the current salt, minimum 48
needed for performance.
3: Further messages of this type will be suppressed.
Almost done: Processing the remaining buffered candidate passwords, if any
4: Warning: Only 6 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 26 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 38 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 6 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 38 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 17 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 38 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 17 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 38 candidates buffered for the current salt, minimum 48
needed for performance.
4: Warning: Only 6 candidates buffered for the current salt, minimum 48
needed for performance.
4: Further messages of this type will be suppressed.
3 8512g 0:17:34:05 99.91% (ETA: 12:00:29) 0.1345g/s 381983p/s 797709c/s 365814KC/s <removed>
4 15103g 0:23:18:01 99.91% (ETA: 12:00:47) 0.1800g/s 284296p/s 853408c/s 272868KC/s <removed>
2 12264g 0:20:43:05 99.91% (ETA: 12:00:39) 0.1644g/s 325343p/s 830205c/s 311142KC/s <removed>
1 23805g 1:05:43:04 99.91% (ETA: 12:01:07) 0.2225g/s 222219p/s 920292c/s 213521KC/s <removed>
*** stack smashing detected ***: ./john terminated
*** stack smashing detected ***: ./john terminated
Aborted (core dumped)
bofh@dev:/opt/JohnTheRipper-bleeding-jumbo/run$ *** stack smashing detected ***: ./john terminated
*** stack smashing detected ***: ./john terminatedPlease note that all of four threads except one were already finished for quite some time but do not indicate 100% or DONE. Maybe waiting for a final check or perhaps related to the issue?
jfoug
magnumripper
As a follow-up for #3417. Just finished full test of the fix. No more stack smashing errors but a segfault when the session is almost completed:
Any advice about how to supply you with useful debug info? Thank you.