-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS support in V4l2rtspserver #341
Comments
Did the file contain private keys and certificate ? Best Regards |
Yes,The attached file, server.includesprivatekey.pem, is a valid TLS certificate containing both the private key and certificate. Could you provide a step-by-step guide on how to test TLS connectivity using this certificate? |
Any inputs? |
Hi @manivalaguru |
Hi @manivalaguru |
Hi,
I'm working on enabling streaming with TLS, but I'm encountering issues with the proper initialization.
OS:ubuntu 22.04
server pipeline:
sudo ./v4l2rtspserver /dev/video0 -fMJPG -W1920 -H1080 -P443 -F60 -u routecam -x server.includesprivatekey.pem
client pipeline:
gst-launch-1.0 rtspsrc location=rtsps://192.168.1.126:443/routecam tls-validation-flags=generic-error protocols=tls latency=0 ! rtpjpegdepay ! jpegdec ! videoconvert ! fpsdisplaysink
While debugging, we identified that the issue occurs because the fTLS.tlsAcceptIsNeeded flag is being set to True even after it has been set to False following the SSL acceptance in the call acceptResult = fInputTLS->accept(fOurSocket);.
The following functions are repeatedly setting the flag. Could you clarify why this function is being called multiple times? what could be the reason
GenericMediaServer::ClientConnection
::ClientConnection(GenericMediaServer& ourServer,
int clientSocket, struct sockaddr_storage const& clientAddr,
Boolean useTLS)
On the client side, this issue keeps recurring.
Progress: (open) Retrieving media info
Progress: (connect) Connecting to rtsps://192.168.1.126:443/routecam
I have attached the client-side log and the Wireshark log to help you better understand the issue.
tls_failre.zip
Regards,
Manikandan
The text was updated successfully, but these errors were encountered: