Skip to content
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

net.java.sip.communicator.service.gui.ALWAYS_TRUST_MODE_ENABLED is se… #35

Merged
merged 1 commit into from
Jun 7, 2016

Conversation

psaavedra
Copy link
Contributor

@psaavedra psaavedra commented Jun 4, 2016

net.java.sip.communicator.service.gui.ALWAYS_TRUST_MODE_ENABLED is set in sip-communicator.properties

I could suggest this trivial change in the jigasi code as consequence of the topic discussed on this thread: http://lists.jitsi.org/pipermail/users/2016-June/011191.html (http://lists.jitsi.org/pipermail/users/2016-June/thread.html#11191)

The reason: move the configuration of the ALWAYS_TRUST_MODE_ENABLED property to the sip-communicator.properties, so as sysadmin you can take the decision of trust or not in all the certificates. By default, I considered the ALWAYS_TRUST_MODE_ENABLED=false as a more secure option in order to prevent MiM attacks.

@@ -122,6 +122,16 @@ public void start(BundleContext bundleContext)
ConfigurationService config
= ServiceUtils.getService(
bundleContext, ConfigurationService.class);

Boolean always_trust_mode = config.getBoolean(
"net.java.sip.communicator.service.gui.ALWAYS_TRUST_MODE_ENABLED",false);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This changes the current default behaviour.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This changes the current default behaviour. By default this should be enabled.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damencho I strongly disagree with that. The default should be secure. If someone needs to connect with TLS insecurely, he should have the option to set that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I see your point and I agree.

@damencho
Copy link
Member

damencho commented Jun 4, 2016

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

@psaavedra
Copy link
Contributor Author

Signed.

@damencho damencho merged commit 2246590 into jitsi:master Jun 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants