Bug ID 940498
Summary john segfault in sha1_block_data_order (function of openssl) on PowerPC
Classification openSUSE
Product openSUSE Factory
Version 201505*
Hardware PowerPC-64
OS SUSE Other
Status NEW
Severity Normal
Priority P5 - None
Component Other
Assignee bnc-team-screening@forge.provo.novell.com
Reporter normand@linux.vnet.ibm.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

john segfault in sha1_block_data_order on PowerPC

As reported in OBS tumbleweed build is failing for john the reaper package (1)
Adding debuginfo during local build and executing gdb allow to identify
the backtrace pointing to failure in openssl as detailed in (2) 


(1) https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/john
===
[   82s] Benchmarking: WPA-PSK PBKDF2-HMAC-SHA-1 [32/64]... Makefile:1791:
recipe for target 'check' failed
[   82s] make: *** [check] Segmentation fault
[   82s] error: Bad exit status from /var/tmp/rpm-tmp.EeG8Gb (%check)
===
(2) backtrace in chroot env: 
===
[michel@vm64:~/work/openSUSE:Factory:PowerPC/john]
$osc build  -x gdb -x glibc-debuginfo -x  libopenssl1_0_0-debuginfo -x
libz1-debuginfo
$osc chroot
...
abuild@vm64:~/> cd rpmbuild/BUILD/john-1.8.0/src
abuild@vm64:~/rpmbuild/BUILD/john-1.8.0/src> gdb ../run/john
(gdb)r --make_check
...
Benchmarking: WPA-PSK PBKDF2-HMAC-SHA-1 [32/64]... 
Program received signal SIGSEGV, Segmentation fault.
sha1_block_data_order () at sha1-ppc.s:235 
235     sha1-ppc.s: No such file or directory.
(gdb) bt
#0  sha1_block_data_order () at sha1-ppc.s:235
#1  0x00003fffb7d4cc28 in SHA1_Update (c=0x1034a770, data_=<optimized out>,
len=<optimized out>) at ../md32_common.h:342
#2  0x00003fffb7e1fbcc in update (ctx=<optimized out>, data=<optimized out>,
count=<optimized out>) at m_sha1.c:78
#3  0x00003fffb7e15554 in EVP_DigestUpdate (ctx=<optimized out>,
data=<optimized out>, count=<optimized out>) at digest.c:294
#4  0x00003fffb7d55538 in HMAC_Update (ctx=<error reading variable: value has
been optimized out>, data=<optimized out>, len=<optimized out>) at hmac.c:171
#5  0x00003fffb7d55968 in HMAC (evp_md=0x3fffb7f78840 <sha1_md>, key=<optimized
out>, key_len=<optimized out>, d=0x101abf98 <hccap+112> "\002\003",
n=2030043136, md=0x3fffffffcf68 "", md_len=0x0)
    at hmac.c:239
#6  0x00000000100874b0 in wpapsk_postprocess (keys=<optimized out>) at
wpapsk.h:262
#7  crypt_all (count=<optimized out>) at wpapsk_fmt.c:150
#8  0x00000000100d1384 in fmt_self_test (format=0x10164518 <fmt_wpapsk>) at
formats.c:104
#9  0x00000000100c6b58 in benchmark_format (format=0x10164518 <fmt_wpapsk>,
salts=<optimized out>, results=0x3ffffffff3c0) at bench.c:138
#10 0x00000000100c759c in benchmark_all () at bench.c:453
#11 0x00000000100d8574 in john_run () at john.c:1163
#12 0x00000000100d8e58 in main (argc=2, argv=0x3ffffffff9b8) at john.c:1392
===


You are receiving this mail because: