From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv5 2/2] wireshark: new package
Date: Fri, 15 Feb 2013 22:34:34 +0200 [thread overview]
Message-ID: <511E9BDA.7010904@petroprogram.com> (raw)
In-Reply-To: <20130215122013.GB1249@tarshish>
[snip]
>>>> BTW, Baruch did you manage to compile this version of wireshark against
>>>> that gnutls 3 ?
>>> Nope. I only tried OpenSSL which I already have on my target.
>> Your .mk file needs --with-gnutls=no added to it's configuration in case
>> both OpenSSL and gnutls are installed.
>> And maybe later a submenu of choice what SSL (if any) implementation to
>> use for decrypting.
> Ok. I'll fix that in my next patch iteration.
>
>> I will try later this evening how far I get this time with compiling it.
> Keep me posted.
>
> Thanks,
> baruch
After inspecting the following
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-analyzer/wireshark/wireshark-1.8.5.ebuild?view=markup
http://www.linuxfromscratch.org/blfs/view/svn/basicnet/wireshark.html
and most importantly,
http://wiki.wireshark.org/SSL
I found out that wireshark uses OpenSSL indirectly only when using
kerberos (which buildroot does not currently have), only if the
said kerberos has ssl support compiled in ("krb5-config --libs" spits'
out -lcrypto) and only if you pass --with-ssl to wireshark config.
For decrypting SSL streams the wireshark will use only, and *only*,
GnuTLS and libgcrypt.
So if you want to include SSL decrypting support by default then you should:
1 ) try that gentoo wireshark patch that adds support for compiling
against gnutls v3
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-analyzer/wireshark/files/wireshark-1.8.3-gnutls3.patch?revision=1.1
2) Add --with-gnutls=yes to WIRESHARK_CONF_OPT
3) Add gnutls to wireshark dependencies.
Also, when compiling against uClibc I had to add LIBS="-ldl" to
WIRESHARK_CONF_ENV as a workaround to finish compiling.
Ofcourse the prober fix for this would be a patch to configure.ac that
would check if libdl exists and then add it to LIBS
Regards
Stefan
next prev parent reply other threads:[~2013-02-15 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 6:04 [Buildroot] [PATCH 1/2] libpcap: fixup pcap-config Baruch Siach
2013-02-03 6:04 ` [Buildroot] [PATCHv5 2/2] wireshark: new package Baruch Siach
2013-02-03 12:11 ` Stefan Fröberg
2013-02-14 4:56 ` Baruch Siach
2013-02-14 15:05 ` Stefan Fröberg
2013-02-14 15:43 ` Stefan Fröberg
2013-02-14 15:52 ` Stefan Fröberg
2013-02-15 11:51 ` Baruch Siach
2013-02-15 12:12 ` Stefan Fröberg
2013-02-15 12:20 ` Baruch Siach
2013-02-15 20:34 ` Stefan Fröberg [this message]
2013-02-15 20:38 ` Stefan Fröberg
2013-02-04 22:53 ` [Buildroot] [PATCH 1/2] libpcap: fixup pcap-config Peter Korsgaard
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=511E9BDA.7010904@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.