Comments (12)
magnumripper
commented on June 9, 2024
Once you have files that emit these line 732 errors, try adding -v -v -v to see what actually happens
from john-tests.
jfoug
commented on June 9, 2024
Sometimes this happens when there is no valid scene output. As I find them I fix them, but there always seems to be anouther sometime later.
from john-tests.
jfoug
commented on June 9, 2024
is this still a problem?
from john-tests.
magnumripper
commented on June 9, 2024
What do you mean by "scene output"? Is it just a typo my fuzzer doesn't catch?
Yeah I really wondered what caused that. Maybe the memdbg output we had another issue for?
Anyway @jfoug I think you split the status line on spaces and use things like $orig_show_words[0] for picking the "word" that is the number of cracks. It's a lot safer to use something like m/(\d+) password hashes cracked(?:, (\d+) left)?/ and use $1 and $2.
from john-tests.
frank-dittrich
commented on June 9, 2024
probably I meant s/scene/screen/.
I intend to test today whether I can reproduce the non-numeric counts with -passtru="--fork=8" and a memdbg buils.
from john-tests.
frank-dittrich
commented on June 9, 2024
Yes, the problem can still be reproduced with this build (--enable-memdbg-ex):
(master)test $ ../run/john --list=build-info
Version: 1.8.0.2-jumbo-1-bleeding OMP-memdbg_ex
Build: linux-gnu 64-bit AVX2-autoconf
Arch: 64-bit LE
$JOHN is ../run/
Format interface version: 13
Max. number of reported tunable costs: 3
Rec file version: REC4
Charset file version: CHR3
CHARSET_MIN: 1 (0x01)
CHARSET_MAX: 255 (0xff)
CHARSET_LENGTH: 24
Max. Markov mode level: 400
Max. Markov mode password length: 30
Compiler version: 4.8.3 20140911 (Red Hat 4.8.3-7)
gcc version: 4.8.3
OpenSSL library version: 01000105f
OpenSSL 1.0.1e-fips 11 Feb 2013
GMP library version: 5.1.2
Regex library version: 1.1 (loaded: 1.1.122)
fseek(): fseek
ftell(): ftell
fopen(): fopen
memmem(): System's
Built with these debugging options
memdbg=extra_memory_checks
ASan (Address Sanitizer debugging)
I use --fork=8 on a quad core without HT.
(master)test $ ./jtrts.pl -v -type mssql-utf8 -passthru="--fork=8" -stoponerror
-------------------------------------------------------------------------------
- JtR-TestSuite (jtrts). Version 1.13, Dec 21, 2014. By, Jim Fougeron & others
- Testing: John the Ripper password cracker, version 1.8.0.2-jumbo-1-bleeding_omp [linux-gnu 64-bit AVX2-autoconf]
--------------------------------------------------------------------------------
John Jumbo build detected.
--pot=NAME option is valid
--encoding=NAME option is valid
all.chr (../run/all.chr) not found
alnum.chr found, inc_alnum_ee8763c850dee8e4b88ef547a8ed39b8 added as a capability
Types to filter on:
mssql-utf8
Capabilities in this build of john:
jumbo core inc local_pot_valid encode_valid utf8 cp1252 cp1251 koi8r cp437 cp737 cp850 cp858 cp866 iso8859-1 iso8859-15 inc_alnum_ee8763c850dee8e4b88ef547a8ed39b8
form=mssql-utf8 guesses: 1229 0:00:00:00 DONE [PASSED]
.pot CHK:mssql-utf8 guesses: 922 -show=sswo 0:00:00:00 DONE : Expected count(s) (1229) [!!!FAILED!!!]
Exiting on error. The .pot file ./tst.pot continas the found data
The command used to run this test was:
../run/john -ses=./tst --fork=8 -pot=./tst.pot mssql_tst.in --wordlist=pw3 -form=mssql -enc=utf8
(master)test $ ../run/john -ses=./tst --fork=8 -pot=./tst.pot mssql_tst.in --wordlist=pw3 -form=mssql -enc=utf8 | grep -C 1 ss
Node numbers 1-8 of 8 (fork)
Loaded 1500 password hashes with no different salts (mssql, MS SQL [SHA1 128/128 AVX 8x])
2 154g 0:00:00:00 DONE (2015-01-09 21:20) 15400g/s 15400p/s 15400c/s 21975KC/s PENTIUM__17..REJECTME__18
3 154g 0:00:00:00 DONE (2015-01-09 21:20) 7700g/s 7700p/s 7700c/s 10987KC/s LATE&*NIGHT__17..INKJET__18
4 154g 0:00:00:00 DONE (2015-01-09 21:20) 15400g/s 15400p/s 15400c/s 21975KC/s X-FILES__17..IWASJU$THERE__18
8 153g 0:00:00:00 DONE (2015-01-09 21:20) 15300g/s 15300p/s 15300c/s 21840KC/s SUMMER__18
Press 'q' or Ctrl-C to abort, almost any other key for status
6 153g 0:00:00:00 DONE (2015-01-09 21:20) 15300g/s 15300p/s 15300c/s 21840KC/s HELLO__18
At Program Exit
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checking5 154g 0:00:00:00 DONE (2015-01-09 21:20) 15400g/s 15400p/s 15400c/s 21975KC/s FUKOFF__17..PASSWORD__19
1 154g 0:00:00:00 DONE (2015-01-09 21:20) 15400g/s 15400p/s 15400c/s 21975KC/s LIMIEY__17..START12__18
Waiting for 7 children to terminate
At Program Exit
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checkingAt Program Exit
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 1 checkingAt Program Exit
7 153g 0:00:00:00 DONE (2015-01-09 21:20) 15300g/s 15300p/s 15300c/s 21840KC/s QWERT12345__18
At Program Exit
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checkingAt Program Exit
Passed
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 3 checkingMemDbg_Validate level 0 checkingLETMEIN (32)
Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checking Passed
At Program Exit
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checking Passed
Passed
Passed
Passed
Passed
Use the "--show" option to display all of the cracked passwords reliably
Session completed
At Program Exit
MemDbg_Validate level 0 checking Passed
MemDbg_Validate level 1 checking Passed
MemDbg_Validate level 2 checking Passed
MemDbg_Validate level 3 checking Passed
from john-tests.
magnumripper
commented on June 9, 2024
Thought so. The fix is described in #34 (comment) above
from john-tests.
jfoug
commented on June 9, 2024
I bet this is the stdio being b0rked issue fixed with fflush, and not an issue with the TS.
from john-tests.
jfoug
commented on June 9, 2024
This is one problem:
MemDbg_Validate level 3 checking5 154g 0:00:00:00 DONE (2015-01-09 21:20) 15400g/s 15400p/s 15400c/s 21975KC/s FUKOFF__17..PASSWORD__19
The regex we use will not work if the node# #g time... is not at head of file.
This is happening due to memdbg-ex (memdbg??) outputting multiple times to fprintf to same line, borking the screen output. That one is not a super simple fix, since we may have a very long set of disjoint output, if there were memory leaks (such as a crash). I will look into that some more, but I am not 100% sold that this is a real problem with the TS.
from john-tests.
frank-dittrich
commented on June 9, 2024
If there are memory leaks, I think it is OK for the test suite to fail.
It should, however, not fail if memdbg just prints the summary info of tests that succeeded.
from john-tests.
frank-dittrich
commented on June 9, 2024
Don't we have a non-zero exit code when memdbg detects problems? In that case, the TS will fail anyway.
So it would be sufficient to take care of memdbg output where everyting is OK.
from john-tests.
jfoug
commented on June 9, 2024
Agreed. But it is not as simple as memdbg output. If you hit the space bar (or any key), along with anything else that causes buffered screen IO, in fork mode, if that IO is not done 'well' (and flushed), then it will garble the IO.
But I do not think this is an issue with the TS. It is simply parsing gabled data, and failing to be able to do that. It should not HAVE to process corrupted data. JtR needs fixed.
from john-tests.
Related Issues (20)
- 1 GB systems fail due to use of unique (and it's recent large defaults) HOT 3
- LogFileProtect = Y issue HOT 3
- When no passwords are cracked, --show finds one invalid password HOT 2
- selftest.dic and selftest.in
- jtrts.pl -v -v is showing two stderr redirections HOT 2
- Search john's stderr output for "runtime error:" and threat that as a failed test HOT 7
- jtrts.pl should remove old tst-.log file before starting next test
- -enc=utf8 fails when using a passthru -rules=none or -mask=?w
- Some option replacements required for --show are apparently required in other places as well HOT 3
- Wrong alnum.chr md5sum HOT 1
- Rules test HOT 3
- dynamic_2009 tests need to be adjusted HOT 1
- grep: tst-.log: No such file or directory
- bcrypt-opencl fails on TS HOT 4
- TS must ignore build warnings etc. in JtR output
- TS has hashes made of UTF-16 BOM's but JtR refuses to use such dictionaries.
- TS fails after 6ea7946
- After changes in unique, .a simple /jtrts.pl fails HOT 6
- bcrypt -internal fail HOT 2
- TS doesn't work properly after 915cfcc
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from john-tests.