From: Dan Kegel [EMAIL PROTECTED]
dank that sense). I have asked for it quite some time ago, see
dank http://www.opeenssl.org/thoughts/MT-mutexes.txt
dank
dank I think you meant
dank http://www.openssl.org/~levitte/thoughts/MT-mutexes.html
Nope, I meant
On Sun, Dec 17, 2000 at 03:09:16AM +, Dr S N Henson wrote:
When mentioning features that don't exist in current releases of
OpenSSL (such as the new undocumented '-prexit' option to s_client),
the FAQ should point out that they don't: The FAQ is not just part
of the release, it's
On Fri, Dec 15, 2000 at 09:05:14AM -0500, Rich Salz wrote:
Please don't try to make objects themselves safe across threads.
We have to. E.g., it is not usual to have multiple threads use SSL
structures created from a single SSL_CTX, and access to this SSL_CTX
and dependent objects (such as
On Sun, Dec 17, 2000 at 04:22:17PM -0800, Dan Kegel wrote:
I think it is a fool's errand to try to make it possible to
"share" every data structure across threads.
Noone has said "every", but some have asked for "some".
And then there are the contrarians who ask for "none".
It ought to
I came across this bug while i found our SSL server was coring a few times a
day. I used dmalloc (www.dmalloc.com) to help trace it down to a client
using MSIE with SSLv3 off and using SSLv2. I have not tried but i assume
any SSLv2 client will cause the same results. It comes down to calculating
Hi,
this feature are not supported? Why?
Is there way reach it direct through BUF_MEM in this readonly mem BIO?
thanks Martin
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Bodo Moeller wrote:
On Sun, Dec 17, 2000 at 03:09:16AM +, Dr S N Henson wrote:
When mentioning features that don't exist in current releases of
OpenSSL (such as the new undocumented '-prexit' option to s_client),
the FAQ should point out that they don't: The FAQ is not just
1 how can I send my "sos"message?
2 where to find the examples about writing program
upon openssl?
3 how can i search my interested
questiona?
Hello, I'm having problems with the EVP_Encrypt/Decrypt interface.
The following program doesn't work as expected. It does simple
data-encrypt-decrypt-in. Specifically, I get some garbage mixed with
the plaintext in the final buffer.
It seems like the EVP_DncryptUpdate decrypts (n-1) blocks of 8
See below...
Pawe³ Krawczyk wrote:
Hello, I'm having problems with the EVP_Encrypt/Decrypt interface.
The following program doesn't work as expected. It does simple
data-encrypt-decrypt-in. Specifically, I get some garbage mixed with
the plaintext in the final buffer.
It seems like the
Martin Szotkowski wrote:
Hi,
this feature are not supported? Why?
Is there way reach it direct through BUF_MEM in this readonly mem BIO?
This is largely because there's no real way to support it without
extending the internal structure to something more complex than a
BUF_MEM. Now there's
Okay, I went and looked at Appendix E of the SSL v3 spec,
to find out why ssl23_accept() does special handling on
ClientHello messages with v2 headers that are marked as
version 3.
First it says "Version 3 servers should accept either
ClientHello format". That's understandable for the
since
On 18 Dec, dhw wrote:
1 how can I send my "sos"message?
dd if=/dev/zero of=/dev/null bs=1
2 where to find the examples about writing program upon openssl?
http://www.openssl.org/related/apps.html
http://www.openssl.org/source/cvs/apps/?hideattic=1sortbydate=0
2069446 wrote:
READ DATA
EVP_EncryptInit(...)
for(;;)
{
EVP_EncryptUpdate(...)
/* until end of data*/
}
EVP_EncryptFinal(...)
If the data can be large something other would be better:
EVP_EncryptInit()
while(Read_Data_Block())
{
EVP_EncryptUpdate()
}
EVP_EncryptFinal()
It
I have set up a web-page on elliptic curve extensions to OpenSSL.
See http://users.pandora.be/stes/ecc.html for further information.
The "patch" for OpenSSL, available at that web-page, includes a new
command :
stes@gecko./openssl ecc
c47n23r1:secp112r1:secp384r1:sect113r1:sect163k1
This
+ rm -f libcrypto
+ rm -f libssl
Undefined first referenced
symbol in file
bn_sub_part_words ../libcrypto.a(bn_mul.o)
openssl: fatal error: Symbol referencing errors. No output written to openssl
collect2: ld returned 1 exit
Bodo Moeller wrote:
On Sun, Dec 17, 2000 at 04:22:17PM -0800, Dan Kegel wrote:
I think it is a fool's errand to try to make it possible to
"share" every data structure across threads.
Noone has said "every", but some have asked for "some".
And then there are the contrarians who ask for
Hi Bodo (and anyone else interested),
Just a thought I was having about locking and things. Rather than us
worrying so much about how to do per-object locking (as opposed to our
current per-class locking), I wonder if it's worth considering how to
minimize the number and complexity of operations
18 matches
Mail list logo
