On Fri, Apr 23, 2010 at 21:35, James Mansion
ja...@mansionfamily.plus.comwrote:
Amit Ben Shahar wrote:
One of the crucial ingredients is ssl using OpenSsl. but we are
encountering a problem with the 'no OPENSSL_Applink' error.
as this is a .Net project, there is no way (i can think of) to
Hello Amit,
Maybe you can explore the IJW way...
I use Visual C++ 6 to build my aWin32 pplications and I had to use some
.NET Crypto functions such as RSA to communicate with a customer.
I've used Visual C++ 2005 Express, in which I add the Win32 environment
(from a platform SDK. Express don't
Patrice,
I think your have misunderstood me (or i did you),
From what you wrote i gather that you are talking about using .Net dlls in
native applications, which is not the case here, i need it the other way
around.
Our server is a .Net application and so we'd either have to somehow get the
Would anyone happen to know how i can eliminate the requirement of the
applink implementation? why would we actually need it?
Amit Ben Shahar
On Sat, Apr 24, 2010 at 13:25, Amit Ben Shahar amit.b...@gmail.com wrote:
Patrice,
I think your have misunderstood me (or i did you),
From what you
Amit,
No, I don't misunderstand you.
The (real) example I gave is in fact similar (I think so)
In a classic Win32 application, when mixing different compiler setting,
different compilers between application and the OpenSSL dll and use some
functions involving FILE* parameters, applink is used
Patrice,
Thank you for the clarification, i'll try just that and post back with my
results.
Thanks!
Amit Ben Shahar
2010/4/24 Patrice Guérin guer...@magic.fr
Amit,
No, I don't misunderstand you.
The (real) example I gave is in fact similar (I think so)
In a classic Win32 application,
Amit Ben Shahar wrote:
The .Net.Security.SslStream is not working in asynchronous calls,
meaning we'd have to implement it in a thread-per-connection paradigm,
which is obviously not an option.
Why 'obviously'? You might be surprised by how many threads can be
managed by Windows before it all
On Sat, Apr 24, 2010 at 18:29, James Mansion
ja...@mansionfamily.plus.comwrote:
Amit Ben Shahar wrote:
The .Net.Security.SslStream is not working in asynchronous calls, meaning
we'd have to implement it in a thread-per-connection paradigm, which is
obviously not an option.
Why 'obviously'?
Hi guys,
I am working on a .Net HTTP(s) server in .Net, which is released is driving
(as a component) a commercial service and is also release in an openSource
project (nettp: http://sourceforge.net/projects/nettp/).
One of the crucial ingredients is ssl using OpenSsl. but we are encountering
a
Amit Ben Shahar wrote:
One of the crucial ingredients is ssl using OpenSsl. but we are
encountering a problem with the 'no OPENSSL_Applink' error.
as this is a .Net project, there is no way (i can think of) to compile
with the applink.c file.
1) Why is that crucial? Microsoft provide crypto
10 matches
Mail list logo
