From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wpa-supplicant: Compile without CONFIG_GNUTLS_EXTRA
Date: Fri, 06 Jan 2012 01:39:21 +0100 [thread overview]
Message-ID: <4F0642B9.20104@opendreambox.org> (raw)
In-Reply-To: <1325799041-3640-1-git-send-email-andrei@gherzan.ro>
On 05.01.2012 22:30, Andrei Gherzan wrote:
> From: Andrei Gherzan <andrei.gherzan@windriver.com>
>
> CONFIG_GNUTLS_EXTRA is needed as support for TLS/IA which was designed to be used
> in the EAP-TTLSv1. As we don't see any requirement for that protocol today we decided
> to remove it from wpa-supplicant .config file.
With this option removed, is there any reason to prefer GnuTLS over
OpenSSL? OpenSSL is wpa-supplicant's default, and at least Ubuntu uses
OpenSSL with it, too. I guess it's tested more thoroughly than GnuTLS.
Regards,
Andreas
next prev parent reply other threads:[~2012-01-06 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 21:30 [PATCH] wpa-supplicant: Compile without CONFIG_GNUTLS_EXTRA Andrei Gherzan
2012-01-05 21:48 ` Denys Dmytriyenko
2012-01-06 0:39 ` Andreas Oberritter [this message]
2012-01-06 13:07 ` Phil Blundell
2012-01-06 7:47 ` Saul Wold
2012-01-06 15:21 ` Andrei Gherzan
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=4F0642B9.20104@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.org \
/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