> From: owner-openssl-us...@openssl.org On Behalf Of Michael S. Zick
> Sent: Sunday, 30 October, 2011 06:36
> On Sun October 30 2011, Ananthasayanan Kandiah wrote:
> > #include
> > #include
> > #include
> > #include
> >
> > #define KEY_SIZE 16
> Ask the compiler to help you:
>
> mszick@wol
> From: owner-openssl-us...@openssl.org On Behalf Of Akanksha Shukla
> Sent: Monday, 31 October, 2011 08:48
> {
>FILE * pFile1;
>char mystring [500];
>pFile1 = fopen ("result.txt","a");
>i
Hi,
I am sorry if I misunderstood things. I went through the text quoted by him.
Also, I did google search for that and what I understood was:
ERR_load_crypto_strings() registers the error strings for all libcrypto
functions. SSL_load_error_strings() does the same, but also registers the
libssl er
> From: Akanksha Shukla [mailto:akshu...@cisco.com]
>
> Hi Carl,
>
> I added the API's call as mentioned by you in the else part to get the
> dump
> of the error. But this time also, I am not successful.
> else
> {
> SSL_load_error_strings();
> SSL_li
Hi Carl,
I added the API's call as mentioned by you in the else part to get the dump
of the error. But this time also, I am not successful.
else
{
SSL_load_error_strings();
SSL_library_init();
FILE * pFile1;
pFile1 = fopen ("
On Mon, Oct 31, 2011, Bin Lu wrote:
> Hi Steve,
>
> Is it still disabled by default? In build 1.0.1-stable-SNAP-20111028, I do
> not see that line in ssl/ssl_lib.c as you mentioned, meaning enabled by
> default going forward?
>
It is enabled by default in newer snapshots now.
Steve.
--
Dr St
Our "monolithic" program (which runs in well under a meg including
the program and all memory it uses) is monitored for correct hash (an
algorithm we have to give a 21 byte hash total of files for which I
have never seen two different files with the same hash) from an
off-site program AND onsit
Ciao.
I use MinGW to build OpenSSL and it has always worked very well.
Steps: a) perl Configure mingw shared enable-capieng --prefix=/mingw
--openssldir=C:/OpenSSL
b) make
After a while, you'll have openssl.exe and a couple of DLLs. At this stage,
you'll be able to access Windows
Hi Steve,
Is it still disabled by default? In build 1.0.1-stable-SNAP-20111028, I do not
see that line in ssl/ssl_lib.c as you mentioned, meaning enabled by default
going forward?
Thanks,
-binlu
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openss
Sergio, how to set this option building OpenSSL? I didn't find any
suggestions in documentation. And can you give a link to the documentation
on the site openssl.org where there are functions of API to work with
Windows CERT Stores?
From: Sergio NNX
Sent: Monday, October 31, 2011 1:02 PM
To:
> On Mon 31/10/11 4:25 PM , "Akanksha Shukla" akshu...@cisco.com sent:
> Hi Michael,
>
> Thanks for the reply. But I think the issue is not from the C perspective.
> As I already mentioned, that if I use fputs to directly write a string to
> file, then I am able to do that successfully. But when I
Hi,
This was what I tried today to isolate the issue. But if you look into
earlier mail chains, then you would find that I have tried to write the
error in pFile1. Please refer to that.
Thanks
Akanksha Shukla.
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl
On Mon October 31 2011, Akanksha Shukla wrote:
> ERR_print_errors_fp(stderr);
>
Because your writing to stderr rather than pFile?
Mike
__
OpenSSL Project http://www.openssl.org
Use
Hi Michael,
Thanks for the reply. But I think the issue is not from the C perspective.
As I already mentioned, that if I use fputs to directly write a string to
file, then I am able to do that successfully. But when I try to write the
error code thrown by Bio_do_connect() API, then nothing is gett
On Mon October 31 2011, Akanksha Shukla wrote:
>
> Could you please have a look and help me here.
> I am not able to proceed further.
>
Sorry, I do not have the required experience in either
"C" or "C like" languages to be of any help.
And you really need the help of a beginner's coding forum.
Hi,
I tried with some different logic in the else part to get the dump of the
error returned by Bio_do_connect() API, but no luck. File is getting created
but nothing is getting written over there.
else
{
FILE * pFile1;
char mystring [500];
Thanks, that was the option I was just suggesting, but I could not
remember the name.
Thanks for finding the name for me, hope it helps the OP.
On 10/31/2011 10:02 AM, Sergio NNX wrote:
Ciao Andrejs.
I don't know much about the source code you posted previously but if you build
OpenSSL with
Ciao Andrejs.
I don't know much about the source code you posted previously but if you build
OpenSSL with the 'enable-capieng' option you'll be able to access every single
store and all the certs stored in Windows.
I hope it helps.
Sergio.
> Date: Mon, 31 Oct 2011 09:44:11 +0100
> From: jb-
In that case look for the CryptoAPI engine for openssl, not sure of its
official name though.
On 10/29/2011 8:21 AM, Andrejs Štrumfs wrote:
Duh... I was sure these were the needed parts. Now, I tried to call
CryptExportKey with PRIVATEKEYBLOB flag, and of course it returned error,
because the
Duh... I was sure these were the needed parts. Now, I tried to call
CryptExportKey with PRIVATEKEYBLOB flag, and of course it returned error,
because the certificate was imported to store without Mark as Exportable
option. But there has to be way to use certificate and private key somehow with
I'm using libssl0.9.8 0.9.8o-3 on Debian Lenny 5.0.3. When I use
SSL_CTX_use_certificate then SSL_CTX_add_extra_chain_cert, I get random
seg faults when calling SSL_accept for subsequent connections that reuse
the SSL_CTX. However, I stopped getting the errors when I replaced
SSL_CTX_add_extra_
21 matches
Mail list logo
