Re: cannot load server.crt
От | Tom Lane |
---|---|
Тема | Re: cannot load server.crt |
Дата | |
Msg-id | 25349.1355961838@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | cannot load server.crt ("Sahagian, David" <david.sahagian@emc.com>) |
Список | pgsql-general |
"Sahagian, David" <david.sahagian@emc.com> writes: > We use our own CA implementation inside Java to generate a PEM-encoded certificate chain (server.crt) and key (server.key). > The certificates are, as they should be, base-64 encoded and surrounded by the appropriate delimiters such as > -----BEGIN CERTIFICATE----- > -----END CERTIFICATE----- > They are also line-wrapped at 77 characters. > But the line wrapping code can cause an extra newline char following the final base-64 encoded character of the cert orkey, and before the -----END CERTIFICATE----- delimiter. > When this happens, Postgres rejects the certificate. That would be OpenSSL rejecting the cert; Postgres never touches such files directly. I don't know whether there's an official spec about the contents of cert files, but you'd have to take it up with the OpenSSL folk if you want to lobby for a change in this behavior. regards, tom lane
В списке pgsql-general по дате отправления: