i can't compile openssl on ym debian etch amd64 box.
neither the source package from etch nor the current 0.9.8e from the
webpage will cmpile, both giving exactly the same error.
any help is really appreciated.
for further info: it worked once untill some etch update ...
i pasted the last part
* David Schwartz wrote on Wed, Aug 29, 2007 at 08:07 -0700:
and a blocking write should return as soon as at
least one byte has been written.
No. A blocking write should block until all the requested data cen be
written.
ahh, interesting. Why should it?
Because this is what
Hello Mailinglist,
I want to use RSA for encryption. So I need to know how to create a RSA key
pair and how to De- Encrypt. Both must be done within the RAM. I want to use
the OpenSSL Api, but all I can find was this page:
http://www.openssl.org/docs/crypto/rsa.html#
1. Is somewhere explained
Thanks to the responses I was able to get openssl compiled in debug mode.
Once I removed the optimization flag from the make file my compiler error
went away. I've since traced through the code and it leaves me pretty much
just as puzzled as before.
The function ssl3_client_hello in s3_clnt.c is
Suggest you pick up a copy of Secure Programming Cookbook. It has
exactly what you are looking for in chapters 7.10 and 7.11.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin Salo
Sent: August 30, 2007 7:37 AM
To: openssl-users@openssl.org
Hello,
Thanks to the responses I was able to get openssl compiled in debug
mode. Once I removed the optimization flag from the make file my
compiler error went away. I've since traced through the code and it
leaves me pretty much just as puzzled as before.
Without optimization library may
Hello,
In the application I'm currently working on which uses OpenSSL via
Ruby, I seem to be having a problem with the handshake when a client
connects to my server, though my client to their server works fine.
From an ssldump, it appears that my server's certificate request does
not
Hi Folks,
I've compiled the FIPs module and OpenSSL 0.9.7m without problems.
However, when I try to compile OpenSSL 0.9.7m with the shared option I
get the following error:
Canister: /usr/local/ssl/lib//fipscanister.o
8811:error:25066067:DSO support routines:DLFCN_LOAD:could not load the
Hi,
Thanks for the reply. The test program works only if I put it in the
main() or if I create a global function then call it in the main(). It
fails if I pack the function as a member function of a cpp class in a
shared library xxx.so, then call it from the main(). I know the context
initialized
@Bill: Thanks, but I hope it is not necessary.
Can someone help me with this code? Why doese my program crash on executing
RSA_print_fp()? I'm using WindowsXP and Visual Studio 6.
I found some postings on this mailinglist with the advice to look into the FAQ.
But the only topic that matches my
Martin: I couldn't get your code to compile. However, I could get this
to work:
#include openssl/rsa.h
#include stdio.h
int main() {
// Do some init:
RSA *oRsaKey = NULL;
int iLength=2048;
// Generate the key:
oRsaKey = RSA_generate_key(iLength, 65537, NULL, NULL);
// Write key to hard disk
Hello,
In the application I'm currently working on which uses OpenSSL via
Ruby, I seem to be having a problem with the handshake when a client
connects to my server, though my client to their server works fine.
From an ssldump, it appears that my server's certificate request does
Marek Marcola wrote:
Hello,
In the application I'm currently working on which uses OpenSSL via
Ruby, I seem to be having a problem with the handshake when a client
connects to my server, though my client to their server works fine.
From an ssldump, it appears that my server's
Hi,
I have been working on a httpsd for the past week.
It does the following :
StartupThreads are getting a incomming connection, create a
SSL_new(ctx), create a BIO_new(BIO_s_socket()), BIO_set_fd, and
SSL_set_bio. Then they SSL_accept(ssl), and SSL_read what is comming
in.
So far so good.
I'm looking at using non-blocking I/O in some places in my code, and I
have a question. The 'BIO_set_nbio_accept' says it will set the
underlying socket to blocking/non-blocking mode, but all the examples
and stuff I see say to use
'BIO_socket_ioctl(SSL_get_fd(ssl),FIONBIO,sl)'. Can
This is acceptable for Perl, but not for C :-) Even if most
people would want a write contradicting its man page, I'd still
consider it wrong :)
I don't follow you.
If you tried to write two bytes, why would you want to wait
until the first one could be written but not wait until the
16 matches
Mail list logo
