![]() Sec-WebSocket-Key: zqzl1xxph4Ff7VqcQ7FU2g= Running test #2: certificate trust test with self-signed certificate for user-supplied common name Test failed, client accepted fake certificate, data was intercepted Sec-WebSocket-Key: zvRgQ97fyTccE5daHsvmqQ= Received data: GET /proxy/remotehosts HTTP/1.1 Running test #1: certificate trust test with user-supplied certificate Skipping test: certificate trust test with common name signed by user-supplied CA certificate Skipping test: certificate trust test with user-supplied common name signed by user-supplied CA certificate Sudo qsslcaudit -user-cert /home/quentin/certs/ -user-key /home/quentin/certs/ -server -l 192.168.1.29 -p 443 Any certificate will be accepted, regardless of the host being accessed (,, ,. The excerpt below is representative of all outgoing connections established by the RemotePC client. We checked if the client is resilient to man-in-the-middle attacks by intercepting traffic going to hosts and redirecting it to a running instance of qsslcaudit. We strongly recommend anyone using RemotePC to update to the latest version available at ()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |