Nelson B Bolyard wrote:
if you send an encrypted message to
someone from whom you have never received a signed S/MIME message, you will
use weak encryption.
Thank you for this useful description.
I feel it would make sense to open a bug to change this default.
Rational : If someone went the
On Fri, Jun 19, 2009 at 03:36:08PM +0200, Jean-Marc Desperrier wrote:
Nelson B Bolyard wrote:
if you send an encrypted message to
someone from whom you have never received a signed S/MIME message, you will
use weak encryption.
huh, is this an official statement?
if this is true this means
I'm running into a problem while using NSS with non-blocking sockets. I
have my own PR_Recv function that does something like this:
static int PR_CALLBACK
my_PR_Recv(PRFileDesc *fd, void *buf, PRInt32 len, PRIntn flags,
PRIntervalTime timeout)
{
...
rc = my_real_read_function(
No, it just means that Thunderbird needs to catch up with the times
and implement a newer version of the specifications, one that was
written after the US's draconian ITAR rules were changed.
-Kyle H
On Fri, Jun 19, 2009 at 6:48 AM, Georgi Guninskigunin...@guninski.com wrote:
On Fri, Jun 19,
On 2009-06-19 12:48 PDT, Rich Megginson wrote:
Does NSS support non-blocking sockets?
Yes.
I'm running into a problem while using NSS with non-blocking sockets. I
have my own PR_Recv function that does something like this:
Although you called it a PR_Recv function, I gather that it is
Nelson B Bolyard wrote:
On 2009-06-19 12:48 PDT, Rich Megginson wrote:
Does NSS support non-blocking sockets?
Yes.
I'm running into a problem while using NSS with non-blocking sockets. I
have my own PR_Recv function that does something like this:
Although you called it a PR_Recv
I wrote:
SSL_ForceHandshake is like a PR_Read or PR_Write call except that it
transfers to data.
make that transfers NO data.
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
7 matches
Mail list logo
