Using TCP client, open an SSL/TLS socket to a service listening on a specific port. Program in VB.NET.

- In VB.NET 2005 ONLY . Write a software to open an SSL/TLS socket to a service listening on a specific port and send / receive formatted messages. - Use only native VB.NET source code. No DLL or unlicensed libraries. Here are the specs, full documentation will be provided upon request: [login to view URL] a TCP, SSL/TLS socket to a service listening on a specific port to send / receive bytes. No client certificate necessary. Use whatever SSL library you have available [login to view URL] an X.509 self-signed SSL certificate. Use RSA 1024. Set the CN value on the certificate to what is specified in the documentation. Use whatever library you want to do this, such as OpenSSL. 4. Provide the public key for your self-signed SSL certificate, in PEM format, to Kroll to load into the respective service. 8. Be capable of sending a 4-byte integer specifying the number (N) of the byte to follow, followed by (N) arbitrary bytes of data. 9. Be capable of reading 4 bytes, converting that to an integer (N), and then reading (N) bytes. 10. protos file will be available 11. download a protocol buffers library ex: , VB.Net, .Net use [login to view URL] 12. Using the protocol buffers library that you chose, compile all the .proto files into real code in your chosen programming language. 13. Be capable of instantiating a MessageWrapper object/struct and setting the properties/fields on it based on the protocol documentation. 14. Using the protocol buffers library, be capable of serializing the MessageWrapper to an array of bytes. 15. Using the protocol buffers library, be capable of deserializing an array of bytes to a MessageWrapper object/struct. 16. Instantiate a PingRequest object/struct and set its properties/fields to any arbitrary value. 17. Using the protocol buffers library, serialize the PingRequest to a byte array, and place it in your MessageWrapper’s MessageContent field. 18. Set the MessageWrapper’s MessageName property to “PingRequest”, and MessageVersion property to “1.0” 19. Using the protocol buffers library, serialize the MessageWrapper, with corresponding serialized PingRequest bytes, to an array of bytes. 20. Send the length-prefix and serialized MessageWrapper bytes over a TLS connection to the Kroll service. 21. Wait for a response on the socket, read the message length, and response message bytes. 22. Using the protocol buffers library, deserialize the response message bytes into a MessageWrapper object/struct. 23. Compare the MessageId field in your request MessageWrapper to the MessageId field in your response MessageWrapper to ensure the response corresponds to your request. 24. Check the MessageName field in the response MessageWrapper a. If the MessageName is “ErrorResponse”, then an error occurred. Using the protocol buffers library, deserialize the MessageContent field into an ErrorResponse object/struct, and handle the error accordingly in your code. The details of the error will be in the ErrorResponse object/struct. b. If the MessageName is “PingResponse” then the request was successful. Using the protocol buffers library, deserialize the MessageContent field into a PingResponse object/struct. Compare the values in the PingRequest and the PingResponse to ensure they match. They should. If they don’t, then something is wrong with your implementation. 26. The files that you just compiled all form messages, similar in structure to the PingRequest/PingResponse that you just finished building. You should be able to send API message requests by replacing PingRequest/PingResponse with the message names of the API calls.