Re: 0.24 not serving puppet provided certificate

[Chris Phillips <chris@xxxxxxxxxxxx>]

Hi,

As is the way, I made *some* progress after posting. Func was expecting a short hostname, but puppet created fqdn certs, so I sorted that, and it's now hopefully got the certificate it wants (it is at least loading the appropriately named pem and cert files... however still nothing, with s_client, I'm now seeing something on the server side:

[...]

    self.raw_requestline = self.rfile.readline()

  File "/usr/lib/python2.3/socket.py", line 338, in readline

    data = "">

  File "/usr/lib/python2.3/site-packages/certmaster/SSLConnection.py", line 150, in recv

    raise e

Error: [('SSL routines', 'SSL3_GET_CLIENT_HELLO', 'length mismatch')]

with the openssl client agreeing on something:

CONNECTED(00000003)

>>> TLS 1.0 Handshake [length 006c], ClientHello

    01 00 00 68 03 01 4d de 2c f3 4b de 48 cf 75 08

    1e b2 2c 42 57 ee ad b6 39 cc 0e 40 bb 02 ce a9

    81 fa 06 0a 5f bd 00 00 3a 00 39 00 38 00 88 00

    87 00 35 00 84 00 16 00 13 00 0a 00 33 00 32 00

    9a 00 99 00 45 00 44 00 2f 00 96 00 41 00 05 00

    04 00 15 00 12 00 09 00 14 00 11 00 08 00 06 00

    03 00 ff 02 01 00 00 04 00 23 00 00

<<< SSL 3.0 Alert [length 0002], fatal handshake_failure

    02 28

140325371447112:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:674:

---

Thanks

Chris

On 26 May 2011 11:17, Chris Phillips <chris@xxxxxxxxxxxx> wrote:

Hi,

I've rolled out an environment where func is using the puppet certs. I have a handful of old el4 boxes and *thought* func was OK on them until I came to use than and found that 0.24 doesn't support the puppet certs, and the chances of upgrading the whole chaining of dependencies (including python 2.3 -> 2.4) is just a no go.

So instead I commented out the attempt to hit certmaster, which is obviously not being used, and sylinked the puppet certs to the normal func locations. After doing this, the func daemon does start and listen, but doesn't actually do anything with no sign of server side errors with DEBUG enabled in the log.

It seems that it just doesn't serve the cert at all. Using openssl -s_client on it, I just get:

openssl s_client -connect hostname:51234

CONNECTED(00000003)

140144621885256:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:674:

---

no peer certificate available

---

No client certificate CA names sent

---

SSL handshake has read 7 bytes and written 113 bytes

---

New, (NONE), Cipher is (NONE)

Secure Renegotiation IS NOT supported

Compression: NONE

Expansion: NONE

---

ANyone have any ideas about any way to nudge func into life with these alternative certs? I suppose it has to be some attribute of the certificate as created by openssl libraries on an el6 server, being used on an el4 client, but I've not a clue what, and would doubt it's possible to change the attributes of the certs.

Thanks

Chris

_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list