Makes sense. Thanks for unblocking me.
On Wed, Jul 24, 2019, 10:23 PM Florin Coras wrote:
> Hi Praveen,
>
> Glad it helped!
>
> Actually the one complaining is openssl. We enforce strict certificate
> verification only if the server hostname was provided at connect time.
>
> Florin
>
> On Jul 24
Hi Praveen,
Glad it helped!
Actually the one complaining is openssl. We enforce strict certificate
verification only if the server hostname was provided at connect time.
Florin
> On Jul 24, 2019, at 7:41 PM, Praveen Kariyanahalli
> wrote:
>
> Thanks a lot. That tip helped a lot. My app_
Thanks a lot. That tip helped a lot. My app_index was not set properly
while adding my cert.
I see my client complains about the self signed certificate. Is this
expected? See logs below
Regards
-Praveen
Jul 25 02:39:02 myvpp1 vnet[1468]: create_api_loopback:330:
ecm->my_client_index 256
Jul 25
I havent changed anything in the listener handler (this is latest vpp code
as is). Just changed the certs thats all. I will sprinkle debugs and run it
under gdb and get back to u. Thanks!
ᐧ
On Tue, Jul 23, 2019, 10:43 PM Florin Coras wrote:
> Hi Praveen,
>
> It looks like the tls listener was
Hi Praveen,
It looks like the tls listener was not properly initialized. I’d recommend
running a debug image from gdb to get more info.
Probably openssl complained about the parameters on listen but the error was
not handled. If I’m right, this [1] should better handle the failed listen.
Fl
Hi All
I replaced the testca/certs with my CA chain (self signed) and my server
client certs. When I run it I am seeing some weird assert on the server
side. Can anyone please throw some light on this?
Thanks in advance
Praveen
Jul 24 04:56:11 myvpp1 vnet[1299]:
/home/pk/vpp/src/plugins/tlsopens
