Peter Parker wrote:
Dave,
Thank you for the quick and thorough response. This is good stuff.
Yes, so the files I will be encrypting will be over 100 bytes. I
am aware of the key size requirements - 1028 was only used as a
placeholder for the
) binaries.
Good luck Dennis and others.
Jeremy Hunt
Zack Weinberg wrote:
On Sun, Jul 29, 2012 at 11:00 AM, Dennis Clarke dcla...@blastwave.org wrote:
After a build of openssl-1.0.1c on Solaris 10 with the Sun Studio 12 compilers
I was very surprised to see this :
# ls -l libcrypto.a
-rw-r--r
The error message is all important.
ar: ../../libcrypto.a: cannot write: Bad address
Bad address is an invalid pointer, cannot write means some access or system
error, which an invalid pointer can be an instance of.
Seeing as you can use ar to read to this file, I assume it is there, even
The Doctor wrote:
On Wed, May 30, 2012 at 08:45:46AM -0400, bhorow...@vai.net wrote:
Quick question for the group? I am running Apache 2.2.22 with OpenSSL
1.0.1c installed. This machine formerly had 1.0.0d and I am noticing that
the apache logs are stating that OpenSSL is still at the earlier
in the crypto algorithm code because that seems to be all that they have in
common. That's why a total scrub cleanup function would be useful ... N
---
Nou Dadoun
ndad...@teradici.com
604-628-1215
-Original Message-
From: jeremy hunt [mailto:jere...@optimation.com.au]
Sent: April 10, 2012 6
On a disconnect check the state of the SSL data structure and call
SSL_free if it is not null.
if (*sslptr != NULL) {
SSL_free (*sslptr);
*sslptr = NULL;
}
Though as you say it is a certificate issue, then perhaps you need to
look at
SSL_CTX_free(*sslctxptr)
Look at the man page for
Hi Terri et al,
I think Jaaron has probably answered the wrong question, let it pass.
Now Terri, you say you attempted to install OpenSSL , perhaps you could
give us some more information and we could help you:
1. Did you build OpenSSL on or for the OS390? Or did you get a copy or
package
Thomas J. Hruska wrote:
On 3/23/2012 12:53 AM, jeremy hunt wrote:
This posting is to help people to build OpenSSL 1.0.1 with Microsoft
Visual Studio. It may also indicate a required change to the build
instructions
for Microsoft Visual Studio.
Summary:
--
I found I needed to install
This posting is to help people to build OpenSSL 1.0.1 with Microsoft
Visual Studio. It may also indicate a required change to the build
instructions for Microsoft Visual Studio.
Summary:
--
I found I needed to install the Windows SDK and manually configure my
build environment to
Dave may be right about there being no direct evidence for a read.
However I have since looked at the code the error is coming from and the error is being
reported at the time the SSL context is being interpreted, which doesn't mean the initial
loading of the SSL context wasn't error free as
You are reading files, see inline for discussion.
On 5/10/2010 7:36 AM, irivas wrote:
I don't even know where those errors come from. As I said before, the same
code under Solaris runs alright.
I'm only connecting to a regular webserver with ssl, nothing more, nothing
less.
I'm not
David wrote:
[safeTgram (safetgram-in) receive status: NOT encrypted, NOT signed.]
After running my app for a couple of iterations for over an hour, I get the
following:
[11:45:42]10 file=stack.c, line=125, thread=15418, number=20,
address=20077768
...
868 bytes leaked in 24
Hi David et al,
On reading the responses so far two new thoughts occur to me:
1. In view of Dr Henson's response, I wonder if removing the
CRYPTO_cleanup_all_ex_data() call in your loop will fix the problem.
Perhaps reusing the context structure after calling it may have the
reverse effect.
Thomas Taranowski wrote:
*[safeTgram (safetgram-in) receive status: NOT encrypted, NOT signed.]*
I think this question may be more general than OpenSSL, and will
expose my SSL n00biness, but I'm not sure where to turn.
I'm working on integrating the use of openssl on an embedded target
Hi David,
Off the top of my head I notice that you do not call this as part of the
cleanup: SSL_CTX_free() [
http://www.openssl.org/docs/ssl/SSL_CTX_free.html# ]
There is also this: [ http://www.openssl.org/support/faq.html#PROG13 ]
Regards,
Jeremy
David wrote:
*[safeTgram
Hi David,
After reading this
[http://www.nlnetlabs.nl/downloads/publications/hsm/hsm_node21.html] ,
it occurs to me that you might need EVP_cleanup() too. You might
consider his clean_up() routine in general, or at least consider his
comments on it.
I think it is true to say that for
./Configure --prefix=/usr --openssldir=/etc/ssl shared os/compiler:gcc
-march=i386 -lnsl -lsocket\
21 | tee log.conf exit $PIPESTATUS)
I have found the best way to pass non-std gcc flags is to set the
os/compiler to gcc -flags. In this case -lnsl and -lsocket are not set
by default and
Hi Srinivas,
Why is this an issue? Is it for an application?
From a library point of view, the version installed on the system
should make no difference unless you are using deprecated (old) or brand
new routines in the library. This should not be an issue, especially as
you are talking
try typing
openssl s_time ?
raj H wrote:
*[safeTgram (optim1) receive status: NOT encrypted, NOT signed.]*
Thanks Jimmy! This command looks to help me for the performance! Only
thing is I have to get it working. I keep on getting errors.
Anyways, thanks! I will go through and get it
Dear General,
Before starting your putty session:
1. go to the Session Logging category
2. select Log SSH packet data
3. make a note of where your putty log is, it is probably best to start
with a new one.
Now attempt a connection to your server. On rejection, peruse your
putty.log file.
Further to the earlier missive suggesting an OpenSSL library clash, as
it was destest that crashed, it is likely there is another DES library
in your path, which may not be from OpenSSL.
Try running destest manually and finding out a little more
information, like where exactly it crashed.
See the license in the Distrib:
bash-2.05$ more LICENSE
LICENSE ISSUES
==
The OpenSSL toolkit stays under a dual license, i.e. both the
conditions of
the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts.
From: Bennett Samowich [EMAIL PROTECTED]
Subject: Certificate management tools
Greetings,
This may or may not be the right place to ask this, but does anyone know of
"canned" utilities for certificate management. A client of ours may want to
start using proprietary certs and I don't
23 matches
Mail list logo
