Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Henning Heinold <heinold@inf.fu-berlin.de>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: wpa-supplicant & EAP-TLS
Date: Tue, 14 Aug 2012 15:59:47 +0200	[thread overview]
Message-ID: <20120814135946.GA5597@mi.fu-berlin.de> (raw)
In-Reply-To: <502A3C00.6010609@mlbassoc.com>

On Tue, Aug 14, 2012 at 05:52:32AM -0600, Gary Thomas wrote:
> On 2012-08-14 05:46, Phil Blundell wrote:
> >On Tue, 2012-08-14 at 05:44 -0600, Gary Thomas wrote:
> >>Does anyone know why the recipe for wpa_supplicant is using gnutls
> >>and not the default OpenSSH for TLS services?  It seems that gnutls
> >>is somehow broken and EAP-TLS does not work with this configuration.
> >>Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS
> >>work fine.
> >>
> >>Would a patch to make this change be entertained?  or should I just
> >>keep it in my own layer?
> >
> >I don't think a patch to just flip the default would be a good idea.  A
> >patch to make it be a DISTRO_FEATURE, on the other hand, would be
> >excellent.
> 
> Thanks, I'll see about working one up.

Btw. You mean openssl not openssh, which uses openssl too.

And a problem with using openssl for wpa_supplicant was license incompatibilities.

Mabyee it is fixed meanwhile.

Bye Henning



  reply	other threads:[~2012-08-14 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 11:44 wpa-supplicant & EAP-TLS Gary Thomas
2012-08-14 11:46 ` Phil Blundell
2012-08-14 11:49   ` Saul Wold
2012-08-14 11:52   ` Gary Thomas
2012-08-14 13:59     ` Henning Heinold [this message]
2012-08-14 14:13       ` Koen Kooi
2012-08-14 14:47         ` Gary Thomas
2012-08-14 20:30           ` Phil Blundell
2012-08-15 10:47             ` Gary Thomas
2012-08-15 10:52               ` Phil Blundell

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=20120814135946.GA5597@mi.fu-berlin.de \
    --to=heinold@inf.fu-berlin.de \
    --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