Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[pcp\]\s+SSL\/TLS\s+and\s+IPv6\s+for\s+PCP\s+via\s+NSS\/NSPR\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[pcp\]\s+SSL\/TLS\s+and\s+IPv6\s+for\s+PCP\s+via\s+NSS\/NSPR\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Max Matveev <makc@xxxxxxxxx>; Date: Thu, 21 Jun 2012 23:20:18 +1000; brolley> The use of NSS/NSPR on its own does not provide SSL/TLS brolley> connections. The client and server must both agree to and brolley> expect the use of a secure connection. The idea would be t; /archives/pcp/2012-06/msg00037.html (9,767 bytes)
2. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Nathan Scott <nathans@xxxxxxxxxx>; Date: Fri, 22 Jun 2012 14:07:25 +1000; Hi Max! I've seen two (out of two possible) potential use cases so far for it when doing some initial event trace based PMDAs. In those cases, the event parameters contain potentially sensitive infor; /archives/pcp/2012-06/msg00039.html (9,740 bytes)
3. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Nathan Scott <nathans@xxxxxxxxxx>; Date: Fri, 22 Jun 2012 15:10:52 +1000; Hi Dave, Thanks for looking into this. Diving straight in with random comments here... While the pmcd/client channel I can definitely see needing encryption at times, I'm not sure there is any case w; /archives/pcp/2012-06/msg00040.html (11,249 bytes)
4. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>; Date: Fri, 22 Jun 2012 17:15:42 +1000; Welcome ... I spent 3 winters in Alberta, and our twin daughters were born in Edmonton, so I have a long-standing association with Canada. And your stint at Red Hat commenced just a few years after w; /archives/pcp/2012-06/msg00041.html (18,770 bytes)
5. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Dave Brolley <brolley@xxxxxxxxxx>; Date: Mon, 25 Jun 2012 11:32:22 -0400; Hi Nathan, Thanks for the constructive feedback. Responses to your comments below ... On 06/22/2012 01:10 AM, Nathan Scott wrote: While the pmcd/client channel I can definitely see needing encryption; /archives/pcp/2012-06/msg00045.html (14,440 bytes)
6. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Dave Brolley <brolley@xxxxxxxxxx>; Date: Mon, 25 Jun 2012 12:08:13 -0400; On 06/22/2012 03:15 AM, Ken McDonell wrote: Welcome ... I spent 3 winters in Alberta, and our twin daughters were born in Edmonton, so I have a long-standing association with Canada. And your stint a; /archives/pcp/2012-06/msg00046.html (17,625 bytes)
7. Re: [pcp] SSL/TLS and IPv6 for PCP via NSS/NSPR (score: 1): Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>; Date: Tue, 26 Jun 2012 07:41:32 +1000; Thanks for the detailed response Dave. Let me just focus on the "int fd" issue. The IPC table may be the right place, provided we change the semantics for that data structure. I'll use the IPC table; /archives/pcp/2012-06/msg00047.html (10,395 bytes)

Current List: 1 - 7
Page: [1]