It looks like v2 is now fully released. Any idea on how I can get this
working? Is it a bug?
On Friday, April 15, 2016 at 7:43:32 AM UTC-5, Drew Miranda wrote:
>
> I tested removing the extra characters before BEGIN
>
> This STILL did not help. I'm at a loss.
>
--
You received this message
I tested removing the extra characters before BEGIN
This STILL did not help. I'm at a loss.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Okay, quick update, I did some quick searching and found this,
https://community.oracle.com/thread/1534464?start=0 which sounds exactly like
the issue. My cert chain file does have extra characters in it. I'll test this
tomorrow.
--
You received this message because you are subscribed to the
Thanks for that command. So I'm able to extract my private key from the
original Java keysyore (because this is where the original private key was
created) and convert it to p12 and then pkcs8. I can verify the key is ASCII
readable and is encoded and passes checked when viewing via openssl.
I used this format to convert existing keys, seems to work ok.
openssl pkcs8 -nocrypt -topk8 -in /etc/pki/tls/private/graylog-server.key
-out /etc/pki/tls/private/graylog-server.pk8
On Wednesday, April 13, 2016 at 4:13:15 AM UTC+10, Drew Miranda wrote:
>
> Any quick tips on the command to use
Any quick tips on the command to use with openssl to output the correct format?
I found enough documentation to interchange formats but an unclear on the exact
switches.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from
Hi Drew,
you're right, the migration path from Graylog 1.x to 2.x isn't very clearly
documented yet. We'll eventually fix that once Graylog 2.0.0 has been
released.
The private key has to be in PKCS#8 format stored as PEM (not DER). The
X.509 certificate has also be to be stored in PEM
