UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36

Steps to reproduce the problem:
1: Enable minimal TLS_1.2 supported in chromium client code.
1. Trying to access TLS1_2 only supported site.
2. After a successful connect with server no handshaking done.
3. If I enable TLS1_1 and TLS1_2 both on server site then handshaking is done using TLS1_1 and after that rest communication is done using TLS1_2.

What is the expected behavior?
If server site has only TLS1_2 enabled then handshaking should also be done using TLS1_2 from client side. Client code is written using chromium version 41.0.2272.76.

What went wrong?
After analyzing the chromium (version 41.0.2272.76) code found that for some reason PK11_TokenExists(CKM_NSS_TLS_MASTER_KEY_DERIVE_DH_SHA256) ( written in the file: src\net\socket\ssl_client_socket_nss.cc) always returning false.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 41.0.2272.76  Channel: n/a
OS Version: 10.0
Flash Version: 

Also noticed that exports_win.def does not contain any PK11_* methods. I tried with adding PK11_* methods in exports_win.def but still no luck.