Date: Sun, 18 Jan 2015 01:35:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196674] security/keepassx2 bus error on Message-ID: <bug-196674-13-SvvLGwpRl8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196674-13@https.bugs.freebsd.org/bugzilla/> References: <bug-196674-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196674 Ivan Brawley <ivan@brawley.id.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan@brawley.id.au --- Comment #8 from Ivan Brawley <ivan@brawley.id.au> --- I've been hit with the same bug with 10.1-RELEASE-p3. Problem lies in the compiling of cipher/salsa20.c in libgcrypt and/or keepassx's interaction with the libgcrypt salsa20 routines. If you compile libgcrypt with "USE_GCC= any" set, keepassx works. If you use the default CLANG's cc but with "CFLAGS= -O1", keepassx also works. I've narrowed it down to compiling just the cipher/salsa20.c module in libgcrypt with "-O1" and the rest with "-O2" will allow keepassx to work. I've just sent an email to the new maintainer of libgcrypt with that information (and ugly patch to port's Makefile) as well to consider. Now the finger pointing.. Is it CLANG's optimizations or libgcrypt's salsa20 code or keepassx calling libgcrypt with bad data? ivan. (different ivan). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196674-13-SvvLGwpRl8>