oh...@cox.net wrote:
>
> oh...@cox.net wrote:
> > Hi,
> >
> > I want to preface this by first saying that I know that this question is
> > probably pretty broad, but I'm hoping that someon on this list might be
> > able to help.
> >
> > We are working with web services our SOAP me
Whoa,
A thing to keep in mind when you're mixing run-time libraries (and
static linking to a DLL is mixing RTLs, even when you use the same
(threading/etc.) flags for the main app build):
two risks:
1) malloc in one, free in other
2) the FILE * APIs (fopen, etc.)
3) file handl based APIs
#1 is
On Mon, Oct 5, 2009 at 9:21 PM, Dr. Stephen Henson wrote:
> On Mon, Oct 05, 2009, Srirang Doddihal wrote:
>
> > Hi Steve,
> >
> > On Mon, Oct 5, 2009 at 5:11 PM, Dr. Stephen Henson >wrote:
> >
> > > [snipped]
> > >
> > > Does this simpler version help:
> > >
> > > http://www.openssl.org/support/f
On October 4, 2009 11:25:51 pm sandeep kiran p wrote:
> Hi All,
> A very quick question regarding Certificate path validation. RFC5280
> mentions that path validation begins at the trust anchor and proceeds
> towards the end entity certificate. The public key from ith certificate is
> used in verif
hi,
is someone here using DSA-SHA256? i am get into trouble now and need
help.
The document of Openssl-1.0.0 said support DSA-SHA2. So i got some test
using DSA_sign(),but i got the error "data too large for key size". Skipping
into the dsa_ossl.c, i found sa_do_sign() allow the digest
On Mon, Oct 05, 2009, Srirang Doddihal wrote:
> Hi Steve,
>
> On Mon, Oct 5, 2009 at 5:11 PM, Dr. Stephen Henson wrote:
>
> > [snipped]
> >
> > Does this simpler version help:
> >
> > http://www.openssl.org/support/faq.html#PROG15
> >
>
> Thank you for pointing me to this. I understand it bette
Hi Steve,
On Mon, Oct 5, 2009 at 5:11 PM, Dr. Stephen Henson wrote:
> [snipped]
>
> Does this simpler version help:
>
> http://www.openssl.org/support/faq.html#PROG15
>
Thank you for pointing me to this. I understand it better now. However the
problem is still unresolved.
>From the FAQ I unders
On Mon, Oct 05, 2009, Srirang Doddihal wrote:
> Hi all,
>
> I have some base64 encoded data in my own buffer (a character array).
> I want to decode this.
>
> >From the man pages it appeared to me that I should
> 1) create a memory bio,
> 2) populate it with my base64 encoded data.
> 3) Create a
Hi,
I recompile ntdll with /MT swith and yes, output dlls now
little bigger:
libeay32.dll: 1 036 288 -> 1 122 304
ssleay32.dll: 212 992 -> 274 432
Looks like something linked...
I will try to test it on machine without VC 2008 redistr installed.
Thank you very much for your help !
---
With
Hi,
You can build OpenSSL dlls that don't require runtime redistribuable
using MS Visual Studio. For that, follow the build instruction and
before calling nmake -f ms\ntdll.mak, edit the file ntdll.mak and
replace the switch /MD by /MT. After the build, you will have dlls that
are statically
Hi,
I suspect BC will have its own runtime libraries to provide similar
generic C runtime functionality.
Yes, but BC can link it inside output .dll.
MS VS should link to but I don't know what compiler option
must be set for it.
__
Max Terentiev wrote:
How to build OpenSSL DLLs using Borland C++ Builder 6 ?
I can successfuly compile and get libeay32.lib/ssleay32.lib files,
but can't understand how to get .dlls ? I was read INSTALL.W32
many times :-)
I can't help with BC specific stuff, but... DLL's are created by a
li
Hi all,
I have some base64 encoded data in my own buffer (a character array).
I want to decode this.
>From the man pages it appeared to me that I should
1) create a memory bio,
2) populate it with my base64 encoded data.
3) Create a base64 filter bio
4) Create a chain like this:
[base64_bio]
Hi,
How to build OpenSSL DLLs using Borland C++ Builder 6 ?
I can successfuly compile and get libeay32.lib/ssleay32.lib files,
but can't understand how to get .dlls ? I was read INSTALL.W32
many times :-)
I want to re-build OpenSSL because default binaries from
http://www.slproweb.com/products/W
14 matches
Mail list logo
