-
Notifications
You must be signed in to change notification settings - Fork 692
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
Linphone does not offer acceptance of unknown TLS certificate (Bounty) #947
Comments
Hi, |
@Viish |
Hi @sercan447, sorry but I don't do direct email support. |
Hi, I have implemented such stuff here for a different App: There are settings to
Take what you need. The licenses are compatible anyway. |
Oh wow. Spectacular. This would be create to create a PR for. Linphone mainline is definitely lacking this sort of thing. |
You can just add this check verify_server_certs = 0 in linphonerc_default file that will be in assets of linphone project. This check will disable the certificate verification on client side and then TLS will be configured. Now the certificate verifcation will only be on server side. |
The problem with this is now you're completely ignoring any kind of verification. And if the server certificate changes suddenly, the client will have no idea. Ad-hoc per-certificate allow is the preferred method across the board. (Web browsers do this) |
Is it expected to work for android version linphone installed from the play store by providing a remote configuration file named as linephonerc_default such as http://192.168.1.2/linphonerc_default? It does not work for me at this point. Maybe something else needs to be provided such as HTTPS with a bundle cert that linphone accepts or a different file name? Thank you!! |
Similar to BelledonneCommunications/linphone-desktop#323
But for Android!
Will pay a reasonable bounty to fix:
Expected Behavior:
1- Warn user about unrecognized certificate
2- User is able to accept and trust certificate and connect
3-Warn user if remote certificate changes in the future, and proceed to step 1
Bonus: Ability to include trusted certificates in remote provision xml file
The text was updated successfully, but these errors were encountered: