Hi,
I get the following error when running make install on RedHat Linux 7.3 on 3
different machines...
__SNIP__
/bin/sh: -c: line 1: syntax error near unexpected token `do'
/bin/sh: -c: line 1: `pod2man=`cd ../../util; ./pod2mantest ignore`; for i
in doc/apps/*.pod; do fn=`basename $i .pod`;
I'm using the EVP_Sign and EVP_Verify functions. The
man pages say you need to call EVP_MD_CTX_cleanup to
avoid memory leaks. How do you use this? I am trying:
EVP_MD_CTX_cleanup()
as well as
EVP_MD_CTX_cleanup(md_ctx) (assuming md_ctx was the
context initialized in EVP_SignInit)
but I get "u
Hello,
I have a CA certificate that I use to sign a bunch of client certificates.
My question is, how do I programatically determine if one of the client
certs was signed by the CA? So, if I pass the program a cert that was indeed
singned by my CA, it will say "YES! A valid certificate!" and i
Indeed, I am suspicious that this is why a certificate I created for my mail
server has stopped working for Outlook XP (does work for Outlook versions before
XP). I am really really hoping that someone can answer this
Cheers!
--- Ingo Kappler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> half a yea
Hi,
I'm tried to build openssl-0.9.6f. The following error occurs in "make
install".
making all in tools...
make[1]: Entering directory `/home/kato/src/openssl-0.9.6f/tools'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/kato/src/openssl-0.9.6f/tools'
/bin/sh: -c: line
On Thu, Aug 08, 2002, Jose Gonzalez wrote:
> Hi,
>
> I am using version 0.9.7Beta3 with a locally created configuration file
> to generate a self-signed root certificate. On a RH-7.2 Linux Sytem.
> The install and test of this version of code had no erros reported. Up
> on issue the following
On Fri, 26 Jul 2002 09:56:45 +0100, [EMAIL PROTECTED] wrote:
While Mr. Hruska is wrong, so are you:
>I can't see any difference. Computers are deterministic beasts. If you have
>the initial stage you can predict any stage later and it doesn't matter
>whether it's a static PRNG's interna
Greg,
ssldump gives u the dump of ssl data being send from your
system. it gives u information like ssl handshake negotiation of
all connections...
the best way to overcome the error would be to debug your program
using gdb.
you can download the ssldump from
http://freshmeat.net/projects/ss
Darin,
You are a genius. It worked like a charm. Thanks!
On Thu, 8 Aug 2002 10:16:08 -0400, [EMAIL PROTECTED] said:
>
>
> Greg,
>
> The reason why the program terminates abnormally when you write to a
> closed
> socket is that the operating system issues a SIGPIPE signal in this
> situation
