Re: can't get rhn_register (and therefore client s) working
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Apr 25, 2002 at 10:40:58AM -0700, Ryan Speed wrote: > On Thu, 25 Apr 2002 17:25:26 +0100 > [email protected] wrote: > > [root@cascia rhn]# openssl s_client -host lada.corp.van.dwave -port 8081 -debug > CONNECTED(00000003) > write to 0814E898 [08152730] (124 bytes => 124 (0x7C)) > 0000 - 80 7a 01 03 01 00 51 00-00 00 20 00 00 16 00 00 .z....Q... ..... > 0010 - 13 00 00 0a 07 00 c0 00-00 66 00 00 05 00 00 04 .........f...... > 0020 - 03 00 80 01 00 80 08 00-80 00 00 65 00 00 64 00 ...........e..d. > 0030 - 00 63 00 00 62 00 00 61-00 00 60 00 00 15 00 00 .c..b..a..`..... > 0040 - 12 00 00 09 06 00 40 00-00 14 00 00 11 00 00 08 ......@......... > 0050 - 00 00 06 00 00 03 04 00-80 02 00 80 9a 31 e3 84 .............1.. > 0060 - 4f bd 79 a6 25 b4 73 e1-d2 00 95 1c 62 52 fa 46 O.y.%.s.....bR.F > 0070 - b9 27 e6 94 3b f1 26 fa-a2 f8 13 66 .'..;.&....f > read from 0814E898 [08157C90] (7 bytes => -1 (0xFFFFFFFF)) > write:errno=104 OK if you are getting the write error check that you have something on the redirect port. I often get this if the other port isn't listening I'd suggest that you try with a known service (eg apache). And run stunnel with: stunnel -d 8081 -r 80 -p /etc/current/current.pem Stunnel is quite fusy about things and takes a bit of getting used to > > openssl s_client -connect https://lada:8081/ -cert CERT-FILE see my other post (my bad but didn't check arguments!) Use: openssl s_client -connect https://lada:8081 -verify /usr/share/rhn/RHNS-CA-CERT It sounds as if current isn't listening properly Paul