Differences

This shows you the differences between two versions of the page.

Link to this comparison view

john:wishlist [2014/02/20 15:49]
z038 [Features/enhancements]
john:wishlist [2014/02/20 16:21] (current)
magnum Deleted stuff that are in GitHub issues or already implemented
Line 1: Line 1:
 ======Wish-list for JtR====== ======Wish-list for JtR======
 +
 +THIS PAGE IS DEPRECATED. Use https://​github.com/​magnumripper/​JohnTheRipper/​issues instead.
  
 Add stuff that you think would enhance JtR to this list. Also consider writing to the mailing list about the details and link to that in here. Add stuff that you think would enhance JtR to this list. Also consider writing to the mailing list about the details and link to that in here.
  
 If you start working on one of the items, add a note on it, listing who is doing the work, i.e. (in progress, magnum) If you start working on one of the items, add a note on it, listing who is doing the work, i.e. (in progress, magnum)
- 
-See also [[to-do list for 1.7.9-jumbo-8]]. 
  
 ------ ------
  
 ===== New formats ===== ===== New formats =====
-  * OpenCL implementation for krb5pa-md5:​[[http://​www.openwall.com/​lists/​john-users/​2012/​12/​10/​1|krb5pa-md5-opencl]] 
   * Support for kerberos etype 1 (des-cbc-crc) and etype 3 (des-cbc-md5) ([[http://​www.openwall.com/​lists/​john-users/​2013/​03/​12/​3|ref]])   * Support for kerberos etype 1 (des-cbc-crc) and etype 3 (des-cbc-md5) ([[http://​www.openwall.com/​lists/​john-users/​2013/​03/​12/​3|ref]])
   * [[http://​www.openwall.com/​lists/​john-dev/​2012/​01/​23/​10|M$ Office <= 2003 password support, only XOR encryption is left to be done]]   * [[http://​www.openwall.com/​lists/​john-dev/​2012/​01/​23/​10|M$ Office <= 2003 password support, only XOR encryption is left to be done]]
-  * Java KeyStore cracker (partially done, patches welcome!) 
   * Cracker for [[http://​oss.codepoet.no/​revelation/​wiki/​Home|Revelation Password Manager]]   * Cracker for [[http://​oss.codepoet.no/​revelation/​wiki/​Home|Revelation Password Manager]]
-  * GNOME Keyring OpenCL format 
-  * KeePass OpenCL format 
   * The Bat! cracker   * The Bat! cracker
   * Intuit Quicken   * Intuit Quicken
-  * RAR5 support (partially done, patches welcome!) 
   * SIMD support in scrypt format   * SIMD support in scrypt format
   * RipeMD-320(HMAC),​ used by Lenel OnGuard, PasswordPro supports this already ​ NOTE, ripemd320 is now supported in JtR.   * RipeMD-320(HMAC),​ used by Lenel OnGuard, PasswordPro supports this already ​ NOTE, ripemd320 is now supported in JtR.
-  * 7-Zip Archives (partially done, patches welcome!) 
   * Apache Derby   * Apache Derby
  
Line 28: Line 22:
   * Add Unicode support for is_mixedcase() in inc.c (not performance critical).   * Add Unicode support for is_mixedcase() in inc.c (not performance critical).
   * Add generic tag-alias handling to dynamic, so eg. a thin format or a user defined or preloaded one could specify its format_tag. It would enable a format to recognize both "​$dynamic_nn$"​ and "​$postgre$"​ in input files as well as pot files but always output the latter.   * Add generic tag-alias handling to dynamic, so eg. a thin format or a user defined or preloaded one could specify its format_tag. It would enable a format to recognize both "​$dynamic_nn$"​ and "​$postgre$"​ in input files as well as pot files but always output the latter.
-  * Re-write wordlist.c, possibly using [[https://​hashcat.net/​forum/​thread-1912.html|fgets-sse2]] while at it. 
   * Try to interleave the BLAKE2 code, just like done with MD4/​MD5/​SHA1 in sse-intrinsics.c.   * Try to interleave the BLAKE2 code, just like done with MD4/​MD5/​SHA1 in sse-intrinsics.c.
-  * Re-work and enhance the Unicode/​codepage stuff: 
-     - Instead of options.ascii,​ options.utf8,​ options.iso-8859-1 and so on, use a bit-field or an array. This is a need for #3. 
-     - Instead of static arrays, allocate and initialize dynamic arrays as needed (when possible). Especially for #3: 
-     - In addition to just enc_to_utf8() and utf8_to_enc(),​ implement enc1_to_enc2(). 
-     - Implement a --hashed-encoding option, using #3. The current --encoding option basically specifies the encoding of the wordlist. This new option would specify what encoding was used when the passwords were hashed. This would make it possible to, for example, use an ISO-8859-1 wordlist as input for an 8-bit format that needs cp850. 
-     * Usual rules apply: Do not alter default behaviors, and do not impact performance when not used. 
   * [[http://​www.openwall.com/​lists/​john-dev/​2012/​01/​27/​7|Make unique able to use >2 GB of RAM]]   * [[http://​www.openwall.com/​lists/​john-dev/​2012/​01/​27/​7|Make unique able to use >2 GB of RAM]]
-  * make changes so that md5-mmx.S and sha1-mmx.S 32 bit asm are thread safe. Then we can use OMP on all SSE builds. ​ MD5 should be pretty easy to add thread safety to.  SHA1 may be possible, but probably more difficult. ​ Also, change these to have the SAME interface as the intrinsic interface. 
-  * add OMP to '​dynamic'​ format, if possible. 
-  * If/when implementing fork/node as seen in the experimental "​j5c4"​ contest edition, we should export node_min, node_max and node_count to external modes. 
-  * -verbose=x command line switch, and audit logging and fprintf(stderr...) logic. ​ Mail list: [[http://​www.openwall.com/​lists/​john-dev/​2011/​08/​31/​2]] 
   * '​Auto'​ Optimization of Rules at run-time prior to running rules (at rules init).   * '​Auto'​ Optimization of Rules at run-time prior to running rules (at rules init).
   * argc/argv for external modes   * argc/argv for external modes
   * john.conf item for default mem-file-size (see [[wishlist#​Comments|comment]] below)   * john.conf item for default mem-file-size (see [[wishlist#​Comments|comment]] below)
   * john.conf item for default field-separator-char (see [[wishlist#​Comments|comment]] below)   * john.conf item for default field-separator-char (see [[wishlist#​Comments|comment]] below)
-  * new rules: convert (if possible) the whole word from/to UTF-8 to/from the currently selected encoding. This will be slow but in some cases powerful. 
-  * complete Unicode support for the rules engine (some ideas in [[http://​www.openwall.com/​lists/​john-dev/​2011/​07/​26/​4|this post]]) 
-  * Add functions in unicode.c for conversion between composed (NFC) and decomposed (NFD) versions of characters. [[http://​www.fileformat.info/​info/​unicode/​char/​e4/​index.htm|Example:​]] Decomposed version of LATIN SMALL LETTER A WITH DIAERESIS (U+00E4) is LATIN SMALL LETTER A (U+0061) COMBINING DIAERESIS (U+0308) 
-  * Once the above is in place, add rules for calling them (for the whole word), 
-  * and possibly add NFC to a couple of Unicode formats (if we confirm this is what happens IRL) 
-  * Lower prio [[http://​en.wikipedia.org/​wiki/​Character_encoding#​Common_character_encodings|encodings]]:​ for Windows "​OEM"​ & Windows "​ANSI"​ (also see [[http://​msdn.microsoft.com/​en-us/​library/​dd317756%28v=vs.85%29.aspx|this link]]), Unices (ISO-8859-*) and possibly (older?) Mac. See [[tutorials/​add-codepage]] for how to add them. 
   * Evaluate the possibility of implementing (at command line and/or in Rules section of john.conf) "rules x rules" - eg. one ruleset who's resulting candidates go through **another** ruleset. Two rulesets of 100 rules each will produce up to 10,000 candidates. This is currently possible using "john ... -ru:first -stdout | john -pipe -ru:second ...".   * Evaluate the possibility of implementing (at command line and/or in Rules section of john.conf) "rules x rules" - eg. one ruleset who's resulting candidates go through **another** ruleset. Two rulesets of 100 rules each will produce up to 10,000 candidates. This is currently possible using "john ... -ru:first -stdout | john -pipe -ru:second ...".
   * If easily implemented,​ allow multiple --rules=xx --rules=yy that will be just like using "​.include [yy]" as last line of rule xx in john.conf.   * If easily implemented,​ allow multiple --rules=xx --rules=yy that will be just like using "​.include [yy]" as last line of rule xx in john.conf.
-  * Consider [[http://​www.openwall.com/​lists/​john-dev/​2011/​09/​27/​1|enhancing the self-tests]]. 
-  * Consider [[http://​www.openwall.com/​lists/​john-dev/​2011/​09/​24/​1|implementing some of the ideas in this thread]] about emitting a status line whenever a password is cracked 
-  * Add a rule that performs "​stripping"​ of codepage characters like é -> e and č -> c. This is easy using Unicode decomposition and just using the base character. 
-  * Secure Mode so clear text passwords are not stored or displayed. Mail list: [[http://​www.openwall.com/​lists/​john-users/​2014/​02/​20/​8]] 
- 
- 
-=====Comments===== 
-(magnum) A while ago, I did the john.conf changes for "​mem-file-size"​ and "​field-separator-char",​ but they failed because john.conf was not yet parsed when my code did the calls to options.c functions. This is probably fairly trivial but I just got tired and ditched it for now. 
----- 
-(jimf) ​ I think we will have to attack this, in this manner: 
-  - Load options from command line. Do NOT perform any work based upon these options, NOR any validation. Simply load them blindly. 
-  - Load the john.conf file data.  The location of john.conf '​may'​ have been set in loading the options from command line. 
-  - Update options from john.conf using any '​defaults'​ in the john.conf file. 
-  - '​Re'​ load the options from the command line. This is so we override '​defaults'​ from the john.conf with command line overrides. 
-  - Now, perform option validations,​ and setup, memory allocation, code page setup, etc, based upon the options. 
- 
-We are sort of catch-22. ​ We need to load options prior to being able to load the john.conf. ​ If we try to load john.conf then process options, then how do we specify a different location for john.conf ? 
- 
  
  
 ======Issues/​bugs needing a look====== ======Issues/​bugs needing a look======
   * BUG in dynamic. ​ If there are $$Fx which pull data from some of the fields, this $$Fxdata is NOT written to the hash line, written into the john.pot file.  Thus, the data to crack is lost!!! ​  Not sure how to work around this.  It does appear, if the $$U is used (user name in the format), but the $$U is not in the salt provided (thus the user name is read from array element 0), This DOES get written into the found hash line (as a $$Uuser string in the salt). Thus, this is fine.  However, the $$Fx's seem to be broken. ​ These are things '​added'​ to dynamic, but I am not sure anyone uses them.   * BUG in dynamic. ​ If there are $$Fx which pull data from some of the fields, this $$Fxdata is NOT written to the hash line, written into the john.pot file.  Thus, the data to crack is lost!!! ​  Not sure how to work around this.  It does appear, if the $$U is used (user name in the format), but the $$U is not in the salt provided (thus the user name is read from array element 0), This DOES get written into the found hash line (as a $$Uuser string in the salt). Thus, this is fine.  However, the $$Fx's seem to be broken. ​ These are things '​added'​ to dynamic, but I am not sure anyone uses them.
-   * BUG in MANY formats. ​ valid / prepare / split are way too promiscuous for many formats. This allows mis dectections,​ and worse allows garbage to pass as valid, to cause all sorts of problems, like memory overwrites, crashes, etc, when the data is later loaded. ​ There is a wiki page added with many examples: ​ [[JtR-valid-bugs]] 
  
  
john/wishlist.txt · Last modified: 2014/02/20 16:21 by magnum
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate to DokuWiki Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki Powered by OpenVZ Powered by Openwall GNU/*/Linux