Hmm.. with the newest chilli it can directly do SSL on the "uamuiport". This might be better. We could also add an option to redirect HTTPS (using the same certificate - so it does actually give a security warning).
No, it could not get rid of the warning. For that you have to buy a certificate and have a hostname that matches. What chilli can do now is run an ssl embedded portal without using any external program like stunnel.
"Hmm.. with the newest chilli it can directly do SSL on the "uamuiport". This might be better. We could also add an option to redirect HTTPS (using the same certificate - so it does actually give a security warning)."
...is that the uamuiport will use SSL over the HTTP-protocol? Which means no need for HTTPS-protocol with SSL-warning etc...?
Do you know "how soon" the new release of CoovaAP/CoovaChilli will be?
We haven't fixed the SSL/embedded portal problem, but we did release a test version of CoovaAP, see http://ap.coova.org/coovaap.html . We will address the embedded portal issue before we fully release it.
A new release of chilli and
A new release of chilli and ap and coming soon... in your setup, you use the self-signed ssl cert or do you replace it?
Self signed cert
I used the self signed cert that is part of the CoovaAP-firmware...
It's the forwarding thing to HTTPS (when the cert has been auth by user) that isn't working.
It works fine in 1.07d not in 1.08
Hmm.. with the newest chilli
Hmm.. with the newest chilli it can directly do SSL on the "uamuiport". This might be better. We could also add an option to redirect HTTPS (using the same certificate - so it does actually give a security warning).
Explain...
I'm not totaly following your thoughts here...
I'm using the internal hotspot with the ssl cert inside coovaap (choose HTTPS mode).
Can you explain a little bit deeper what you mean with your previous answer? Sorry...
Will there be HTTPS with ssl without cert warning in web browser? ...
No, it could not get rid of
No, it could not get rid of the warning. For that you have to buy a certificate and have a hostname that matches. What chilli can do now is run an ssl embedded portal without using any external program like stunnel.
OK, so what you mean
OK, so what you mean with:
"Hmm.. with the newest chilli it can directly do SSL on the "uamuiport". This might be better. We could also add an option to redirect HTTPS (using the same certificate - so it does actually give a security warning)."
...is that the uamuiport will use SSL over the HTTP-protocol? Which means no need for HTTPS-protocol with SSL-warning etc...?
Do you know "how soon" the new release of CoovaAP/CoovaChilli will be?
Thanks!
We haven't fixed the
We haven't fixed the SSL/embedded portal problem, but we did release a test version of CoovaAP, see http://ap.coova.org/coovaap.html . We will address the embedded portal issue before we fully release it.
Hi david, Do you have a quick
Hi david,
Do you have a quick changelog somewhere for this version?
kind regards