MS CryptoAPI

[Scott Crosby]

> Don't know if you got any hits with this.  I've been playing around
> with implementing gpg via outlook (exchange) extensions, but I really
> haven't gotten too far as I'm working to much for a living. :)
>
> What advantages/disadvantages would there be to implementing gpg
> through the cryptoAPI stuff?  Have you looked into the suitability of
> MS's architecture?

The cryptoAPI seems to be extendable, though I've never done any serious
development under windows.  I've already got a shell and am working on
"putting it all together."  The problem is with bringing the GnuPG code
over to Visual Studio... it ain't easy.  I'm evaluating other development
environments right now, though haven't made much progress.

Scott F. Crosby
E-Mail : skroz at skroz.net
Web : http://www.skroz.net

"Science is like sex: sometimes something useful comes out, but that is
not the reason we are doing it" -- Richard Feynman

I can accept encrypted messages enciphered with Verisign or GPG/PGP.  Both
public keys can be found below or at http://www.skroz.net

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBDmPm5ERBACnEMaMdpB8fEQaOBmzsJtn2fPKRy6si7140x2sevGeBC2GHsFS
qaKCUgyglofaf2sIlPXdqPxjfc8R24e5vQ5qlSyUi0QJdlOWrygQ6NJGAX0ptNRr
wv29QHjrsXvbLndBmkaeyqpLzionA0HkYm79eKSsHf6ob6Svrg3BODep7wCg7lK/
05HNSo5cQvsy4dKUAmhnwg0D/1pmi2dQyYj8UQhaUeX9FzeGiNzXkTZTQWt2hEU0
s2Vgv9hkMC9wseJmKrr5tX+M7J0ArWyxWQqEwWTxKHVkIyTI1+ls3GmUWhB0eQ65
bsR5ttwcYKMFFq+ReigKzBBc/8SxnwHkjMg+0IRpmfH5E7aN4yT8Dytq65naI2OB
oK9bBACE/i8yKjIuJ3hf8xm/47TuogUug2jX5N1d1z5IBTYxr7m8qSuFy8haRkar
ZlWExbTdaADGUtukOWWLhGHXCXNZU/0jjzLMlLn066NijOruI7V3vCKRT/StfFl5
bsu2GmnOly8LqlRmJUVhUHmQBXZ1plO0Rtry9RE9Hrtd0nmMnbQwU2NvdHQgRi4g
Q3Jvc2J5IChTdGFuZGFyZCBLZXkpIDxza3JvekBza3Jvei5uZXQ+iFwEExECABwF
AjmPm5EFCQHhM4AECwoEAwMVAwIDFgIBAheAAAoJEKTwLT3Yvg4t374AoLzp7x0T
GPUWnhemIW9Ivqxg4CdkAKCA+x0dM+dKDdOM1kpO/MVkZJ0UirkBDQQ5j5uwEAQA
8nWAG53Bh9DBWnbI2Oeg7F+BlzIPf+HcxGAfAjHpqK0cYktOzqjeJo2B75eY9t5g
L8T1p9tk089yTa6u2oSHoGxSNW/HbOgnndJTodCoxP41waINr66r7COWMOYNmSRW
Bt6C2yaHYWNjNuUGWiSe5XPWPYceIri8by/jTy+eaXcABRMEALv2+/j6yiHsxJJh
16za285Zv7kyMdRB1ClIK/GLIP4mMjNBUxsNIRntIhaON4ONucVRM6nb2Y4iA5Eg
prFrhziZB+UPBuipSeTLJaM2wXTPdBFMsAibuF2Tv1EbampIqR9wYOfYiKQetHXX
JSqg8cS+z6bLqx94enyfr9Su3j3xiEwEGBECAAwFAjmPm7AFCQHhM4AACgkQpPAt
Pdi+Di0W6ACgxLO1S4jNayJgm++dchfIBSzCC2QAoKw/28CyxAu1eUUleiG49Ae0
Zp1m
=zxK6
-----END PGP PUBLIC KEY BLOCK-----




-----Original Message-----
From: Jonathan Lupa [mailto:jjlupa at jamdata.net]
Sent: Friday, August 18, 2000 10:49 PM
To: Scott F. Crosby
Subject: Re: MS CryptoAPI


On Mon, Aug 14, 2000 at 11:20:58PM -0400, Scott F. Crosby wrote:
> I've undertaken a project to port GnuPG to a windows friendly format by
> extending the Windows CryptoAPI.  This would allow GnuPG to be used
> anywhere within any application that supports the API, including
outlook,
> IE, etc.  I'm not very far along (basically, I've got the shell for the
> extension,) and could use a little help, as I've never done any serious
> windows programming before.  Great way to learn!

Don't know if you got any hits with this.  I've been playing around
with implementing gpg via outlook (exchange) extensions, but I really
haven't gotten too far as I'm working to much for a living. :)

What advantages/disadvantages would there be to implementing gpg
through the cryptoAPI stuff?  Have you looked into the suitability of
MS's architecture?

-Jonathan Lupa

--
jjlupa at jamdata.net
GPG public key available from http://lupavista.jamdata.net/gpg.asc
------------------------------------------------------------------
Lament 1750: "If I only had a radioactive decay source and a fast
free-running oscillator..."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2921 bytes
Desc: not available
Url : /pipermail/attachments/20000819/df0ace9a/smime.bin