Hi all !
I managed to make what I wanted to work. I would like to thank you for
all you've done. You've been terrific.
Thanks,
Gregory.
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
Gregory BELLIER wrote:
Jean-Marc Desperrier a écrit :
Wan-Teh Chang wrote:
You can use the NSS command-line tool 'ssltap' to inspect the SSL
handshake
messages:http://www.mozilla.org/projects/security/pki/nss/tools/ssltap.html
It's significantly easier to do it with Wireshark.
Is it easier
Nelson B Bolyard wrote:
Sounds like you're not running your build. Are you perhaps still getting
the 'system" libraries in your tests, rather than your own built libs?
I made some progress today.
Damn Nelson, you were right. I got to say I don't know where else it
could have been from but
Wan-Teh Chang wrote:
Without looking at your code, I'm afraid that we won't be able to help much.
Yes, I know it's difficult to guess what I may have done. That's why I
provide in attachment a patch supposed to provide a "new" cipher named
MYC as MYCipher. It is actually SEED.
You probab
On 2010/03/17 09:44 PST, Gregory BELLIER wrote:
> Sorry, my two emails are one after the other.
>
> As I said in the previous one, I copied the SEED. Basically, I did grep
> -i seed $(find mozilla -type f -print) -l followed by a grep -irn 0096 *
> I copied all the occurences of SEED the cipher
I suggest that you also look at the actual SEED or Camellia patch to
see all the necessary changes to mozilla/security/nss/lib/ssl. (I assume
your changes to the rest of NSS are correct because you said you can
use MYC in S/MIME.)
The only difference in mozilla/security/nss/lib/ssl I see is that
Jean-Marc Desperrier a écrit :
Wan-Teh Chang wrote:
You can use the NSS command-line tool 'ssltap' to inspect the SSL
handshake
messages:http://www.mozilla.org/projects/security/pki/nss/tools/ssltap.html
It's significantly easier to do it with Wireshark.
Is it easier than the selfserv and
Wan-Teh Chang wrote:
You can use the NSS command-line tool 'ssltap' to inspect the SSL handshake
messages:http://www.mozilla.org/projects/security/pki/nss/tools/ssltap.html
It's significantly easier to do it with Wireshark.
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
http
On Wed, Mar 17, 2010 at 9:44 AM, Gregory BELLIER
wrote:
>
> So I guess I miss something to add a cipher in NSS. Until now it has worked
> for S/Mime but this bug appears with the need to use TLS.
>
> What should have been done that I didn't ?
Without looking at your code, I'm afraid that we won't
Sorry, my two emails are one after the other.
As I said in the previous one, I copied the SEED. Basically, I did grep
-i seed $(find mozilla -type f -print) -l followed by a grep -irn 0096 *
I copied all the occurences of SEED the cipher and not the ones about
*a* seed and created a new cipher
Robert,
I did what you suggested.
You were right, there is a deeper problem because selfserv doesn't
recognize my cipher if I use the option "-c :0200". I'm told an unknown
cipher has been requested.
But if I use 0084 (which is camellia) it works fine. I used grep to find
every occurrences of
Gregory BELLIER wrote:
As I said I would do, I looked every where in the code where the word
"camellia" appears and my code is very much alike. I really don't know.
Did you have a look at a Wireshark capture of it ?
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists
On 03/15/2010 10:03 AM, Gregory BELLIER wrote:
>
>
> Robert Relyea a écrit :
>>> In sslsock.c, I print ssl3_CipherPrefSetDefault and I can see that my
>>> cipher is not enabled.
>>>
>>> Do you have any hints/tests which could help me ? Some tests I could
>>> do ?
>>> What am I missing ?
>>>
>>
Robert Relyea a écrit :
In sslsock.c, I print ssl3_CipherPrefSetDefault and I can see that my
cipher is not enabled.
Do you have any hints/tests which could help me ? Some tests I could do ?
What am I missing ?
OK, this is your overall problem. If NSS does not have a cipher enabled,
it
Robert Relyea wrote:
this is your overall problem. If NSS does not have a cipher enabled,
it will neither advertise it nor select it, no matter where it is on the
list.
There are two possible reasons for this:
1) New Ciphers are not enabled by default, you need to explicitly turn
on that cip
>
> In sslsock.c, I print ssl3_CipherPrefSetDefault and I can see that my
> cipher is not enabled.
>
> Do you have any hints/tests which could help me ? Some tests I could do ?
> What am I missing ?
OK, this is your overall problem. If NSS does not have a cipher enabled,
it will neither advertise
Hello all !
I added a cipher in NSS and OpenSSL. I would like to create a TLS
session between those two.
In OpenSSL, the tests suite works fine (make tests) and I can get a
working TLS tunnel with my cipher.
I guess my problem is in NSS, that's why I ask for your help. At this
time, the ciph
17 matches
Mail list logo
