Hi,
I am using the AES-CCM patch for Openssl with my code and am encountering
some segmentation faults which are happening within the AES_CCM code. I was
hoping you could help me sort out the problem.
Thanks in advance for your valuable time.
I am using the AES-CCM patch given in (
Hi Sebastian,
On Jan 17, 2011, at 4:12 PM, Sebastian Proca wrote:
It's strange for me how comes that, depending on the
specified arguments, I get two different errors:
I case :
# ./dtls_udp_echo 127.0.0.1
SSL_connect: Connection refused
Ok. It's a Firefox Add-on:
https://www.eff.org/https-everywhere
Questions:
1) But: Why can't i find it on the offical Firefox Add-ons site?:
https://addons.mozilla.org/en-US/firefox/
2) Did anyone audited the HTTPS Everywhere code?
3) Can someone trust this Add-on? Is it safe to install/use?
On Wed January 19 2011, S Mathias wrote:
Ok. It's a Firefox Add-on:
https://www.eff.org/https-everywhere
Questions:
1) But: Why can't i find it on the offical Firefox Add-ons site?:
https://addons.mozilla.org/en-US/firefox/
2) Did anyone audited the HTTPS Everywhere code?
3) Can
Ok. It's a Firefox Add-on:
https://www.eff.org/https-everywhere
Questions:
1) But: Why can't i find it on the offical Firefox Add-ons site?:
https://addons.mozilla.org/en-US/firefox/
Because you're looking in the wrong place. It is wrong to assume that
100% of XPIs are hosted at AMO. Most
I trust the EFF. I suppose it comes down to the fact that trust is never
a default decision, nor should it be.
On 01/19/2011 06:29 AM, S Mathias wrote:
Ok. It's a Firefox Add-on:
https://www.eff.org/https-everywhere
Questions:
1) But: Why can't i find it on the offical Firefox Add-ons
koichi sugimoto wrote:
Could you try dNSName ?
-
So, thanks for the suggestion. It does work around the problem.
In addition to the adding the IP address to the cert with
subjectAltName=IP:10.0.0.1; I added the IP address twice (probably didn't
need to), using
