|
From: Patrick Y. <kc...@ce...> - 2005-05-17 04:14:58
|
It is for identification of the local MSH when it makes SSL request to=20 other remote MSHs using client authentication. -- patrick Portelli, Joe F wrote: > I=92m setting up Hermes MH as part of a work project and I=92m having=20 > difficulties understanding some of the settings in the section=20 > <MSH><SSL> of msh.properties.xml. I can understand the =93local=94 MH=20 > server (ie the one I=92m setting up) needing to =93know=92 the certific= ates=20 > of the trusted servers it=92s talking to (for remote server=20 > authentication). However I cannot understand why different remote=20 > servers need the local server to have a key for each of them for=20 > authenticating itself (section <MSH><SSL><ClientAuth>). My=20 > understanding is that for a machine to authenticate itself all it=20 > needs is one valid certificate from a =93recognized=94 Certificate Auth= ority. > > Regards > > Joseph F. Portelli > > Telstra Research Laboratories > > ( +61 (0)2 8255 3099 > > 7 +61 (0)2 8255 3153 > > =9C 3/400 George Street, Sydney, NSW 2000 > > =9A _<_mailto:joe...@te....com_>___ > |