Let me try one more time to explain the problem with an unrealistic, but I hope
easy to follow, example. Consider:
A <-> B
Now, imagine A sends a message to B requesting some unit of data. B begins
sending a very, very large chunk of data to A, many tens of MB. After 10 MB or
so, A realizes t
024 / sumS: 1025407
> Server: bytesReceived: 1024 / bytesSent: 1024 / sumS: 1026431
> Server: bytesReceived: 903 / bytesSent: 903 / sumS: 1027334
> 4409:error:140943F2:SSL routines:SSL3_READ_BYTES:sslv3 alert unexpected
> message:s3_pkt.c:1053:SSL alert number 10
>
> Thats the
> please tell me where the deadlock is.
> As far as I know a deadlock arise when one process locks a
> resource an other
> process requests and vice versa.
A deadlock occurs when two or more agents are waiting for each other. Neither
can make forward progress until the other does. This is preci
erpret the message or whatever - thats the last
message which is sent from the client to the repeater.
I do not know why I get SSL alert number 10 though I sniff alert 21
with wireshark but what I describe is consistent and true.
If you want to see the wireshark dump or something else I can give
Okay. SSLv3 is different from TLSv1.0. And you really, really,
REALLY need to give the correct error. Your original message said it
was alert number 10, not alert 21.
Alert 21 is not specified in SSLv3 (see
http://www.freesoft.org/CIE/Topics/ssl-draft/3-SPEC.HTM for the alert
definitions, secti
Hi,
I watched the traffic. There I can see, that the client
sends 'SSLv3: Encrypted Alert / Alert 21 (0x15)' so it seems that the
client have a problem with a message it was sent to him.
Thats right, it is the endpoint of the TLS connections but I use
SSL_read() and SSL_write() allready.
Because
TLS defines alert number 10 to be "unexpected message" (RFC2246,
section 7.2 and 7.2.2). It indicates a protocol error; as the RFC
says, "this alert should never be observed in communication between
proper implementations." Which side is sending the alert, the proxy
or the peer?
The way you desc
Hi,
> Yes, the code is prone to deadlock. The code implements the "I will not
> start doing X until I finish doing Y" logic. This is known to cause
> deadlocks in proxies, as one end or the other of the connection proxied
> inevitably has an "I will not start doing Y until I finish doing X" logic
> Hello list,
>
> I write a application which acts like a proxy/repeater between
> two ssl - endpoints. For my app I use OpenSSL 0.9.8g.
> The two endpoints connect to the app and idenfity themselves
> using a id (Both use the matrixssl implementation for ssl handling).
> Two matching id's sta
t the repeating.
Everything runs fine up to the transfer amount of quite exactly 1 megabyte,
then the connection crashs and in repeat code I get
this errormessage:
30190:error:140943F2:SSL routines:SSL3_READ_BYTES:sslv3 alert unexpected
message:s3_pkt.c:1053:SSL alert number 10
The coresponding code:
On Tue, Jun 27, 2000 at 05:34:57PM +0100, [EMAIL PROTECTED] wrote:
> >Are you using non-blocking sockets?
> >Lutz
>
> No, I am using blocking sockets...
[Source code deleted.]
I run out of ideas at this point.
The error message you posted is only printed
if (SSL_in_init(s) &&
>Are you using non-blocking sockets?
> Lutz
No, I am using blocking sockets...
Ragnar
---
int ClientConnectionType::connectToHost()
{
int err = 0;
struct sockaddr_in sa;
X509* server_cert;
char* str
On Tue, Jun 27, 2000 at 04:48:56PM +0100, [EMAIL PROTECTED] wrote:
> Thank you Lutz, your response gave me an idea i.e. I used "meth =
> TLSv1_client_method();" instead of "meth = SSLv3_client_method();"
>
> My SSL alert number 10 vanished... now I can connect
Thank you Lutz, your response gave me an idea i.e. I used "meth = TLSv1_client_method();" instead of "meth = SSLv3_client_method();"
My SSL alert number 10 vanished... now I can connect without receiving this error.
This seems to work A.OK with the JCSI server, at le
On Tue, Jun 27, 2000 at 04:18:55PM +0100, [EMAIL PROTECTED] wrote:
> >If you are talking about any other peer software, please be more specific
> >and give enough data (IP-address?), so that other people can experiment
> >themselves.
>
> Thank you for the info Lutz :)
>
> My peer software is a s
To: [EMAIL PROTECTED]
cc:
Subject: Re: SSL alert number 10
On Tue, Jun 27, 2000 at 03:45:14PM +0100, [EMAIL PROTECTED] wrote:
> I am wondering why I am getting this error and what it means...¿
>
> "sslv3 alert unexpected message:.\ssl\s3_pkt.c:9
16 matches
Mail list logo
