When doing a PEAP/TTLS authentication, if the Phase2 passphrase is
not provided, connman crashes due to a NULL pointer.
This patch fixes the crash.
Associated meego bug: bz6841
---
plugins/supplicant.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/plugins/supplican
On 15/09/2010 19:53, Samuel Ortiz wrote:
On Wed, Sep 15, 2010 at 07:25:15PM +0200, Samuel Ortiz wrote:
However, I don't understand why connman is trying to connect to the
network. Note I remove every time default.profile before launching
connman.
Is it the correct behavior ?
No, it's not. I'm
Hi,
I recently updated my meego build. With this build, I have connman 0.59.
I try to do a PEAP authentication. I put my peap.config in
/var/lib/connman folder. (See it below)
[global]
Name = EAP-PEAP
Description = EAP PEAP connman configuration file
[service_peap]
Type = wifi
Name = MYNETWO
From: Fabien Marotte
This patch adds error and info messages in case connman detects
missing parameters when doing a TLS or a PEAP/TTLS authentication.
---
plugins/supplicant.c | 67 ++
1 files changed, 51 insertions(+), 16 deletions(-)
diff
From: Fabien Marotte
Connman reads the *.config files in STORAGE_DIR during its boot but
it looks only for parameters it is interrested in.
The configuration parameters syntax is complex and it is very
simple to make a mistake without getting connman warnings. This
leads the user to think that
From: Fabien Marotte
---
src/config.c | 47 +--
1 files changed, 33 insertions(+), 14 deletions(-)
diff --git a/src/config.c b/src/config.c
index bdbb704..498c97a 100644
--- a/src/config.c
+++ b/src/config.c
@@ -56,6 +56,23 @@ struct connman_config
This patch adds error and info messages in case connman detects
missing parameters when doing a TLS or a PEAP/TTLS authentication.
---
plugins/supplicant.c | 66 ++---
1 files changed, 51 insertions(+), 15 deletions(-)
diff --git a/plugins/supplicant.
Connman reads the *.config files in STORAGE_DIR during its boot but
it looks only for parameters it is interrested in.
The configuration parameters syntax is complex and it is very
simple to make a mistake without getting connman warnings. This
leads the user to think that connman understands the c
Connman reads the *.config files in STORAGE_DIR during its boot but
it looks only for parameters it is interrested in.
The configuration parameters syntax is complex and it is very
simple to make a mistake without getting connman warnings. This
leads the user to think that connman understands the c
Connman reads the *.config files in STORAGE_DIR during its boot but
it looks only for parameters it is interrested in.
The configuration parameters syntax is complex and it is very
simple to make a mistake without getting connman warnings. This
leads the user to think that connman understands the c
In case the user provides configuration files to connman, the
file name must respect some rules. The documentation was not
up to date concerning these rules.
---
doc/config-format.txt |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/config-format.txt b/doc/config-for
EAP-TTLS and EAP-PEAP are similar in terms of options to pass to
wpa_supplicant. So in case of TTLS, the PEAP path is used.
---
doc/config-format.txt | 16
plugins/supplicant.c |3 ++-
2 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/doc/config-format.txt b/d
EAP-TTLS and EAP-PEAP are similar in terms of options to pass to
wpa_supplicant. So in case of TTLS, the PEAP path is used.
---
doc/config-format.txt | 16
plugins/supplicant.c |3 ++-
2 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/doc/config-format.txt b/d
13 matches
Mail list logo