Skip site navigation (1) Skip section navigation (2)

Re: problem with libpq7.3.3/encrypted

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Christian Ruediger Bahls <christian(dot)bahls(at)stud(dot)uni-rostock(dot)de>
Cc: pgadmin-hackers(at)postgresql(dot)org,Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: problem with libpq7.3.3/encrypted
Date: 2003-07-23 18:25:53
Message-ID: 3F1ED331.3070300@pse-consulting.de (view raw or flat)
Thread:
Lists: pgadmin-hackers
So I believe we have a problem with libpq 7.3.3 with encryption. Can 
somebody please verify this, and forward this to pgsql-bugs? I have an 
ancient 7.3.2 libpq without encryption, and 7.4 CVS, and it's already 
difficult to handle that.

Regards,
Andreas


Christian Ruediger Bahls wrote:

>[2003-07-23 17:57] Andreas Pflug <pgadmin(at)pse-consulting(dot)de> wrote:
>  
>
>>I wonder why this fundamental problem comes up at this late stage. 
>>Certainly it works on XP, as it does on W2K, and my SuSE 8.2 (2.4.20) 
>>has no problem either. One common thing is that the non-working systems 
>>use libpq from 7.3.3, maybe that's the problem. I'll be checking now 
>>with 7.4, before I try to ssh/X to snake. I tried snake's libpq.a on my 
>>system, but got unresolved externals.
>>    
>>
>it could be because of the encryption layer
>that postgresql uses .. 
>i think this is because i use the encrypted layer
>an uncomplete stacktrace i have from one
>of these runs:
>#0  0x407659c4 in read () from /lib/libc.so.6
>#1  0x4066db50 in __JCR_LIST__ () from /lib/libpthread.so.0
>#2  0x40668f53 in read () from /lib/libpthread.so.0
>#3  0x400c31cc in BIO_new_socket () from /usr/lib/libcrypto.so.0.9.7
>#4  0x0000000a in ?? ()
>#5  0x08aec778 in ?? ()
>#6  0x00000005 in ?? ()
>#7  0x400c31b6 in BIO_new_socket () from /usr/lib/libcrypto.so.0.9.7
>#8  0x4013bc60 in KRB5_AUTHENT_it () from /usr/lib/libcrypto.so.0.9.7
>#9  0x08ac3e48 in ?? ()
>
>but still i guess i cant trust these traces
>as i got stuff like that as well:
>#0  0x40667a71 in __errno_location () from /lib/libpthread.so.0
>#1  0x40032430 in ssl3_read () from /usr/lib/libssl.so.0.9.7
>#2  0x4004c130 in ssl3_undef_enc_method () from /usr/lib/libssl.so.0.9.7
>#3  0xffffffff in ?? ()
>#4  0x08ad6b80 in ?? ()
>#5  0xbfffee58 in ?? ()
>#6  0x4004c130 in ssl3_undef_enc_method () from /usr/lib/libssl.so.0.9.7
>#7  0x08b77e38 in ?? ()
>#8  0xbfffee18 in ?? ()
>#9  0x4003b7ea in SSL_read () from /usr/lib/libssl.so.0.9.7
>#10 0x08ac0ed8 in ?? ()
>#11 0x08b814f6 in ?? ()
>#12 0x00006942 in ?? ()
>#13 0x4003b795 in SSL_read () from /usr/lib/libssl.so.0.9.7
>#14 0x40153860 in pg_enc2name_tbl () from /usr/lib/libpq.so.3
>#15 0xffffffff in ?? ()
>#16 0x08ad6b80 in ?? ()
>#17 0x40717438 in realloc () from /lib/libc.so.6
>
And Dave wrote:

>Interestingly, I've just tried this on Linux, and when viewing
>pg_description, the empty edit grid appears with 'Refreshing data,
>please wait...' in the task bar and then hangs. 
>
>The pg console shows:
>
>LOG: SSL SYSCALL error: EOF detected
>LOG: pq_recvbuf: Unexpected EOF on client connection
>
>  
>
Regards,
Andreas





In response to

Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2003-07-23 19:28:14
Subject: Re: pgadmin3 stops working when trying to access/show
Previous:From: Andreas PflugDate: 2003-07-23 16:43:45
Subject: Re: pgadmin3 stops working when trying to access/show

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group