[prev in list] [next in list] [prev in thread] [next in thread]
List: xml-security-dev
Subject: RE: Problem with WinCAPICryptoProvider
From: "Milan Tomic" <milan () setcce ! org>
Date: 2005-08-21 13:29:10
Message-ID: 01ed01c5a654$501e64c0$ce018ac1 () Majestix
[Download RAW message or body]
I doubt someone will need those keys.
As much as I understand it:
- they are not needed for XML decryption process.
- they are created by XSEC C++ lib.
- they are not used in any other app beside XSEC C++ lib.
Best regards,
Milan
> -----Original Message-----
> From: Berin Lautenbach [mailto:berin@wingsofhermes.org]
> Sent: Saturday, August 20, 2005 11:22 AM
> To: security-dev@xml.apache.org
> Subject: Re: Problem with WinCAPICryptoProvider
>
>
> What about if someone doesn't want their keys deleted? Is there any
> case where the error could happen but the keys are OK?
>
> Cheers,
> Berin
>
> Milan Tomic wrote:
> > I have already commited this today into XSEC C++ lib. :)
> >
> > Keys might become corrupted because someone with admin
> rights run your
> > app, and after that someone with lesser rights run it again on the
> > same PC (two users). Or something like that.
> >
> > In the WinCAPICryptoProvider ctor there is another call to
> > CryptAcquireContext(), but before this one, and it works fine. It
> > never reports corrupted keys error. It uses NULL as a
> second parameter
> > which means it acquires keys for current user, and not
> > s_xsecKeyStoreName value which is the same for all users on that PC.
> >
> > Best regards,
> > Milan
> >
> >
> >
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic