Ignore:
Timestamp:
2013-01-06T23:36:17Z (12 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
106f19c
Parents:
a906b77
Message:

Require StartTLS from all Jabber servers by default, like most clients do
these days.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/user-guide/commands.xml

    ra906b77 r955aad8  
    15181518
    15191519        <bitlbee-setting name="tls" type="boolean" scope="account">
    1520                 <default>try</default>
    1521 
    1522                 <description>
    1523                         <para>
    1524                                 Newer Jabber servers allow clients to convert a plain-text session to a TLS/SSL-encrypted session. Normally (with this setting set to <emphasis>try</emphasis>) BitlBee will do this, if possible.
    1525                         </para>
    1526 
    1527                         <para>
    1528                                 If you want to force BitlBee to use TLS sessions only (and to give up if that doesn't seem to be possible) you can set this setting to <emphasis>true</emphasis>. Set it to <emphasis>false</emphasis> if you want the session to remain plain-text.
     1520                <default>true</default>
     1521
     1522                <description>
     1523                        <para>
     1524                                By default (with this setting enabled), BitlBee will require Jabber servers to offer encryption via StartTLS and refuse to connect if they don't.
     1525                        </para>
     1526
     1527                        <para>
     1528                                If you set this to "try", BitlBee will use StartTLS only if it's offered. With the setting disabled, StartTLS support will be ignored and avoided entirely.
    15291529                        </para>
    15301530                </description>
Note: See TracChangeset for help on using the changeset viewer.