On Feb 1, 12:45 am, Robert Relyea wrote:
> If I were you, I'd double check my byte compare code in B. Try
> connecting to A with one cert and to B with another and make sure it
> fails. In our previous example, you clearly had a mangled version of
> certificate C sent to be, but you indicated tha
>> Depends on what you're trying to accomplish, what question you're trying
>> to answer. If the question is merely "are these two certs identical"
>> then comparing both from stem to stern is a very good way. If you're
>> trying to ask "do these two certs identify the same subject", then you
>>
On Jan 30, 11:54 am, Nelson B Bolyard wrote:
> B is going to log about the connection from C before it happens?
> uh ...
Yes; A is in fact a server for a centralized peer-to-peer network and
B and C are peers.
It would be useful if the logs of a given peer contained the common
names of other peer
On 2011-01-29 06:06 PDT, Ambroz Bizjak wrote:
> Hello. I have a problem with NSS. Here's what I'm trying to achieve:
[ If I may paraphrase, system C sends a cert to systems A and B. ]
[ A forwards its copy to B. B must compare the two copies. ]
> Here's how I encoded the certificate (on
4 matches
Mail list logo
