From: johny at neuromancer.sk (Jan Jancar)
Subject: Bug: SIGSEGV in OPENSSL_cleanse
Date: Mon, 22 May 2017 22:39:45 +0200 [thread overview]
Message-ID: <81a1dcd7-0b2c-c1b0-738f-0607473fdd87@neuromancer.sk> (raw)
In-Reply-To: <20170522185128.GF7429@john.keeping.me.uk>
On 05/22/2017 08:51 PM, John Keeping wrote:
> Did you compile CGit yourself or are you using a pre-built package?
> What version of libssl-dev is installed?
>
> I wouldn't be surprised if compiling against openssl-1.0 headers but
> linking with openssl-1.1 produces the behaviour you describe above.
>
I am using the distro-provided version:
https://archlinuxarm.org/packages/armv6h/cgit
Name : cgit
Version : 1.1-2
Description : A web interface for git written in plain C
Architecture : armv6h
URL : http://git.zx2c4.com/cgit/
Licenses : GPL2
Groups : None
Provides : None
Depends On : openssl luajit
Optional Deps : python-pygments: syntax highlighting support
python-markdown: about page formated with markdown
mime-types: serve file with correct content-type
header [installed]
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 975.00 KiB
Packager : Arch Linux ARM Build System <builder+xu6 at archlinuxarm.org>
Build Date : Wed 26 Apr 2017 01:39:23 AM CEST
Install Date : Fri 05 May 2017 08:21:33 PM CEST
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
Arch linux doesn't package -dev packages, the headers are part of the
openssl or openssl-1.0 package. So they live in
"/usr/include/openssl/*.h" and "/usr/include/openssl-1.0/openssl/*.h"
respectively.
Currently rebuilding cgit, but that might take a while since it's just a
RaspberryPi so in the meantime, since I run cgit through uWSGI behind
nginx, I fixed this by adding LD_PRELOAD=/usr/lib/libcrypto.so.1.0.0 to
the uWSGI cgit environment. Still don't know how this happened and why
is the coredump reporting a SEGV in the wrong lib(with which in a
LD_PRELOAD it actually works).
Thanks! In the end this is really just a packaging / build bug so not an
upstream problem.
Cheers,
--
Jan
______________________________________________________
/\ # PGP: 362056ADA8F2F4E421565EF87F4A448FE68F329D
/__\ # https://neuromancer.sk
/\ /\ # Eastern Seaboard Phishing Authority
/__\/__\ #
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 862 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20170522/59f07c3a/attachment.asc>
prev parent reply other threads:[~2017-05-22 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 17:54 johny
2017-05-22 18:51 ` john
2017-05-22 20:39 ` johny [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81a1dcd7-0b2c-c1b0-738f-0607473fdd87@neuromancer.sk \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).