[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <F88361BB-DECB-4E62-B7E2-AEAB383BA716@shinnok.com>
Date: Thu, 4 Jun 2015 20:57:06 +0300
From: Shinnok <admin@...nnok.com>
To: john-users@...ts.openwall.com
Subject: Re: [john-dev] [RFC] Johnny upcoming release !
> On Jun 3, 2015, at 9:20 PM, Mathieu Laprise <mathlaprise@...il.com> wrote:
>
> We will soon release a new version of Johnny with a nice changelog. Later this summer, we'll also release further new versions of Johnny based on this roadmap http://openwall.info/wiki/john/johnny-roadmap <http://openwall.info/wiki/john/johnny-roadmap>.
>
> We make Johnny for you guys so we'd like to get your feedback regarding which platform(and you'd like us to support for :
> 1. Source build instructions and testing
> 2. Subsequent binary packaging
>
> On which platform are you guys using or will you guys use Johnny the most ? Would having a proper installer help you ? Should we bundle JtR with Johnny to make it easier for you ?
Important clarification, for 1. we'll provide detailed and clear instructions for building on most major desktop platforms, however, for no.2, unless we're going to get explicit x no. of requests for certain platforms now or later along the road, the starting list of platforms which will get an installer are:
1. Windows, .msi along with latest JtR jumbo build for Windows available;
2. OS X, dmg, might include JtR too if feasible or we'll leave that to the likes of Homebrew;
Notably, what's missing is any Linux package. This is partly because no one has offered to take responsibility for those so far and partly because I don't "believe" much in providing non official distro repository rpm's and deb's packages. Another aspect to this is that we can't ship JtR too in the same rpm/deb and thus have to rely on the distribution availability of JtR(which differs a lot in supplied versions and many don't include jumbo) or user build, so this would be a "half assed" solution with much maintenance effort on our side, so it's not worth it.
To conclude, unless somebody hails and takes responsibility for any Linux packages we can't provide any. That being said, the source build shouldn't really be any much hassle than building a jumbo version.
Let's hear your success/failure stories or use cases, it matters to us.
Regards,
Shinnok
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.
