I am trying to connect to my PostgreSQL server but psql is complaining that I don't have a valid client certificate. Here is how I create my certificates:
Self-signed server certificate:
Client certificate:
Configuring the Client. Using SSL without Certificate Validation; Custom SSLSocketFactory; Configuring the Server. Configuring the PostgreSQL™ server for SSL is covered in the main documentation, so it will not be repeated here. Before trying to access your SSL enabled server from Java, make sure you can get to it via psql. You should see.
After copying the necessary files (client.crt, client.key, root.crt) onto the client machine and changing permission (i.e., chmod og-rwx client.key), I do the following:
and then I get:
Am I doing the client certificate signing process wrong?
Thanks,
I tried:
and I get:
Using Wireshark, here is the capture I got for the communication between the client (192.168.0.103) and the server (192.168.0.100):
Just wanted to add that if you want to just change it without binding a key to it go into userMy GamesBorderlandsWilloGameWilloInput and add the command line bSetCameraFOV=xxx (put in number) and it will set the FOV permanently. Feb 22, 2015 In this video, I show you guys how to change the FOV (Field of View) for Borderlands 1 on PC!! Thanks for Watching! Key Bindings: http://pastebin.com/CFA94tA. Borderlands 1 how to change fov. How can the answer be improved? Jan 24, 2014 Borderlands How To Change The FOV Settings On PC! Borderlands GOTY Steam PC FOV Increase Tweak Mod! Top 7 Best Eridian Guns and Weapons in Borderlands 1 #. Things that Must Change for.
Do you know how to make sense of this?
Okay, I did what you said, and it seems like the server does not send the CertificateRequest message to the client. as you can see below:
but this is weird because in pg_hba.conf, I have:
What do you think?
I changed the pg_hba.conf to contain:
and changed postgresql.conf to add in the 'Security and Authentication' section:
AND IT WORKED! Thank you so much!
In this situation I tend to pull out Wireshark and snoop the SSL negotiation to make sure the client certificate is really being offered by the client.
I suggest using openssl to verify the client->root signing link, too.
Edit: It's necessary to specify clientcert=1
even when cert
authentication is chosen. Yes, that's weird.