Try to get closer to Jumbo-2

[magnumripper]

Here's current blockers for a Jumbo-2. Tick off, or add to, this list as needed.

• Unprintable characters in pot file after cracking a dynamic_25 hash #2437 Unprintable characters in pot file after cracking a dynamic_25 hash ( @jfoug )
• Update doc/CREDITS-jumbo and doc/CHANGES-jumbo #1911 Credits, changes ( @magnumripper )

---

Here's all current bugs
Here's everything marked with Jumbo-2 milestone

[magnumripper]

Several of the blockers are depending on @Sayantan2048. I've tried to address them but I don't seem to get anywhere.

[jfoug]

#1428 ?
#1289 ?
#1199 Checked in. I have had mine this way for months. It runs better on all my AVX/AVX2 systems. 1468537
#570 ?

Should we change the other jumbo-2 to jumbo-3 ?

[magnumripper]

Those you list (and some others) should be fixed if possible but are definitely not blockers. They can be tagged J2 for now but may change to J3.

I did change a number of enhancements/new-formats to J3 milestone (or no milestone).

[magnumripper]

BTW I don't care much about JP problems if Solar doesn't bother fixing them. When we're done with our blockers and some more testing, we can suggest to Solar we're ready for a release and he may consider fixing #1199 and others while at it.

(JP is what I suggest we call "John Proper" aka "non Jumbo" from now on - "core" is better used for core code as in cracker.c and loader.c - basically anything but formats)

[jfoug]

That was my reason for including #1199. how about JPr ? :) Or even JB (john base)

There may be a few other that are 'CORE' issues which we should look at possibly. The rules crash, I do have a fix (workaround) for

[magnumripper]

Someone (was it me??) apparently added non-blockers like #883 to the list. I'll let them stand for now, it would be awesome to get all of them fixed but they are definitely not blocking a release of Jumbo 2.

[jfoug]

I added everything to this list which was marked as J2. I know you removed a bunch, but someone else re-marked them. If they are in the search for J2, they are also on this list.

[magnumripper]

I added everything to this list which was marked as J2

That's just weird and 100% redundant. You'd obviously use this link instead which doesn't need manual updates. I wanted to establish a list of blockers. Fixing things like #883 is not important - if it's not fixed we'll just move it to J3. Same goes for many others.

[magnumripper]

I dropped the non-blockers from the list.

[jfoug]

bump!! jumbo 1 is REALLY getting dated, and is what is in all the distro's that install john.

[magnumripper]

We've got lots of bugs to fix: https://github.com/magnumripper/JohnTheRipper/issues?q=is%3Aopen+is%3Aissue+label%3Abug+milestone%3A1.8.0-jumbo-2

[jfoug]

Many of those 'bugs' are far from show stoppers.

[magnumripper]

Sure, but most of them should definitely be fixed before a release.

[kholia]

If we want to make this release, I think we have to drop some "blocker" bugs from this issue.

For example, #1746 doesn't look like a blocker bug to me. #1908 is about performance, doesn't sounds like a blocker.

[kholia]

@Sayantan2048 seems gone for a while. We have a workaround for #1782 which works fine, so it doesn't sound like a blocker.

[magnumripper]

I really think #1746 should be fixed, but in a pinch we could just document it as "some combinations simply won't work right now - but they will fail self-test".

I removed the milestone from #1782 and #1908.

[magnumripper]

I dropped #1938 as well, it's just a variant of #1782.

[claudioandre-br]

There is another critical bug that needs attention: the --restore bug.

• it misses candidates (oh, it is a bad bug).

[magnumripper]

Yeah I was just going to add that we need lots and lots of soft-stop/restore (press q) and hard-stop/restore (kill -9) testing after all changes @jfoug did to resuming. I've found and fixed bugs since that and I suspect there are more. That "restore tester format" doesn't seem very good since he actually introduced bugs when using it 😢

[claudioandre-br]

I know @solardiz and @magnumripper are busy people, but we are seeing "messages", the Fedora 23 issue I just post (no link on purpose) is only the latest, suggest that people might became confused and disappointed about JtR maintenance status.

[solardiz]

We definitely ought to make a new numbered release soon. I'd appreciate it if you folks get jumbo closer to that state. From my side, I intend to release 1.8.1, in part so that jumbo's version number differs from the previous one at least this little bit more. ;-) So let's plan to release a 1.8.1-jumbo-1 soon - perhaps in two months?

[magnumripper]

We have a really nasty blocker in #2817 now. I wish Jim could come back to us for a while again...

[jfoug]

I will be around some shortly, and will look into #2817 I am actually retiring from tech at the end of the year, and moving towards more peace in my life. I am just tired of the corp rat race.

[kholia]

@jfoug Having you back would be awesome. I tried hacking on the dynamic compiler recently but didn't find a good solution for the problem I was trying to solve.

[magnumripper]

Closing this in favor of a new #3513