[3392] in WWW Security List Archive
RE: Entrust and Microsoft ISAPI
daemon@ATHENA.MIT.EDU (Lester Waters)
Mon Oct 28 14:56:41 1996
From: Lester Waters <lesterw@microsoft.com>
To: "'WWW-Security Mailing List'" <www-security@ns2.rutgers.edu>,
"'Dave K. Kythe'" <davek@healthmagic.com>
Date: Mon, 28 Oct 1996 09:17:47 -0800
Errors-To: owner-www-security@ns2.rutgers.edu
FYI: Entrust technology is part of Microsoft Exchange Server.
>----------
>From: Dave K. Kythe[SMTP:davek@healthmagic.com]
>Sent: Wednesday, October 23, 1996 11:19 AM
>To: 'WWW-Security Mailing List'
>Subject: Entrust and Microsoft ISAPI
>
>We are thinking about using Nortel's Entrust in a web
>application that would use Microsoft's ISAPI and IIS web
>server. But how well does Entrust work with ISAPI?
>Does anyone have experience with calling the Entrust
>toolkit APIs from an ISAPI filter?
>
>If we build the web app using a different API set than
>Entrust's, how interoperable are X.509 certificates generated
>by Nortel's Entrust CA product with applications developed on
>a security framework like Microsoft's CryptoAPI? Are there
>any major caveats with "mixing and matching" security products
>of different vendors like Entrust and Microsoft?
>
>Thanks!
>
>Dave K. Kythe, Senior Architect
>http://www.HealthMagic.com
>phone: 803-748-9444 x107
>email:davek@healthmagic.com
>
>
>
