Hi,
I posted the patch as #2158: X509_STORE_set_default_paths also use
lookup by_capi,
but there is no response.
What's going on?
thanks,
2010/1/30 NARUSE, Yui :
> I see.
> I sent it to tracker.
> thanks,
>
> (2010/01/30 8:37), Kyle Hamilton wrote:
>> If you're going to send a patch, please send
I see.
I sent it to tracker.
thanks,
(2010/01/30 8:37), Kyle Hamilton wrote:
> If you're going to send a patch, please send it to r...@openssl.org.
> That gets the patch into the request tracker, and gets it into the
> (relatively) formal review process.
>
> -Kyle H
>
> On Thu, Jan 28, 2010 at 4
If you're going to send a patch, please send it to r...@openssl.org.
That gets the patch into the request tracker, and gets it into the
(relatively) formal review process.
-Kyle H
On Thu, Jan 28, 2010 at 4:54 PM, NARUSE, Yui wrote:
> How about my previous patch, which lookup Windows' store with
How about my previous patch, which lookup Windows' store with CryptoAPI.
http://www.mail-archive.com/openssl-dev@openssl.org/msg27023.html
thanks,
--
NARUSE, Yui
nar...@airemix.jp
__
OpenSSL Project
(2010/01/17 21:12), Roumen Petrov wrote:
> NARUSE, Yui wrote:
>> Hi,
>>
>> (2010/01/12 9:38), Dr. Stephen Henson wrote:
>>> On Mon, Jan 11, 2010, NARUSE, Yui wrote:
So I request X509_STORE_set_default_paths call this.
When this is merge, both Unix user and Windows user can use
> [SNIP]
>>
(2010/01/17 21:12), Roumen Petrov wrote:
> The store name is e_capy configuration paramether and I could not find
> reason to be hard-coded to "ROOT" into code.
As my understanding, X509_STORE_set_default_paths sets default stores of
root certificates. So I hard-coded "ROOT".
> Also why to load
NARUSE, Yui wrote:
Hi,
(2010/01/12 9:38), Dr. Stephen Henson wrote:
On Mon, Jan 11, 2010, NARUSE, Yui wrote:
So I request X509_STORE_set_default_paths call this.
When this is merge, both Unix user and Windows user can use
[SNIP]
Thank you for your comment.
So I rewrite my patch as you said:
On Fri, Jan 15, 2010, Kyle Hamilton wrote:
> My understanding is that OpenSSL doesn't really use the "trusted
> certificate" system, which contains the information about what a
> certificate is trusted for. Further, the bits available for the
> Windows store don't have an isomorphic mapping withi
My understanding is that OpenSSL doesn't really use the "trusted
certificate" system, which contains the information about what a
certificate is trusted for. Further, the bits available for the
Windows store don't have an isomorphic mapping within the trust
parameters that OpenSSL provides.
Is th
Hi,
(2010/01/12 9:38), Dr. Stephen Henson wrote:
> On Mon, Jan 11, 2010, NARUSE, Yui wrote:
>> So I request X509_STORE_set_default_paths call this.
>> When this is merge, both Unix user and Windows user can use
>> the system's default root certificates.
>>
>> I should file this to Request Tracker
On Mon, Jan 11, 2010, NARUSE, Yui wrote:
> (2010/01/10 23:23), Shahin Khorasani wrote:
> > try this
> > (snip)
>
> Thanks, it works.
>
>
> So I request X509_STORE_set_default_paths call this.
> When this is merge, both Unix user and Windows user can use
> the system's default root certificates.
(2010/01/10 23:23), Shahin Khorasani wrote:
> try this
> (snip)
Thanks, it works.
So I request X509_STORE_set_default_paths call this.
When this is merge, both Unix user and Windows user can use
the system's default root certificates.
I should file this to Request Tracker as a bug? (even if thi
try this
#include
static void ossl_x509store_add_certs_win(X509_STORE *store)
{
HCERTSTORE hStore;
PCCERT_CONTEXT pContext = NULL;
X509 *x509;
hStore = CertOpenSystemStore(0, "ROOT");
if(!hStore)
return;
while (pContext = CertEnumCertificatesInStore(hStore,
On Unix, we can use X509_STORE_set_default_paths(store)
to load root certificates provided by the system
But on Windows, its certificates aren't provided as a file.
So it should be required another way.
Following is a concept code (use Crypt32.dll):
#include
/* http://msdn.microsoft.com/en-us/l
14 matches
Mail list logo
