Hi John,
complained about not finding the CA certificate at depth(1). That gave us the clue about hierarchy.We reissued the certs from the root CA and all worked perfectly. Has anyone else experienced this? Can anyone explain why it happens? Is it possible to use *swan with sub CAs? Thanks - John
Just a wild guess - might it be that eiter server or client did not have all certificates installed or had a broken chain file ?
All crypto systems need al certificates up to the one that is "self-signed" to verify a chain and there must be a (application specific) configuration that tells the Software about the chain (so where to find the certificates for Sub and Root)
Oliver -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72
smime.p7s
Description: S/MIME Cryptographic Signature
