Changeset 823de9d for doc

Timestamp:

2009-03-12T19:10:06Z (16 years ago)

Author:

Sven Moritz Hallberg <pesco@…>

Branches:

master

Children:

673a54c

Parents:

9b55485

Message:

commit updates by ashish shukla <wahjava@…>

Location:

doc

Files:

• CHANGES (modified) (1 diff)
• user-guide/commands.xml (modified) (1 diff)

doc/CHANGES

@@ -3 +3 @@
 
 http://bugs.bitlbee.org/bitlbee/timeline?daysback=90&changeset=on
+
+Version 1.2.3:
+- Fixed one more flaw similar to the previous hijacking bug, caused by incon-
+  sistent handling of the USTATUS_IDENTIFIED state. All code touching these
+  variables was reviewed and should be correct now.
+
+Finished 7 Sep 2008 
+
+Version 1.2.2:
+- Security bugfix: It was possible to hijack accounts (without gaining access
+  to the old account, it's simply an overwrite)
+- Some more stability improvements.
+- Fixed bug where people with non-lowercase nicks couldn't drop their account.
+- Easier upgrades of non-forking daemon mode servers (using the DEAF
+  command).
+- Can be cross-compiled for Win32 now! (No support for SSL yet though, which
+  makes it less useful for now.)
+- Exponential backoff on auto-reconnect.
+- Changing passwords gives less confusing feedback ("password is empty") now.
+
+Finished 26 Aug 2008
 
 Version 1.2.1:

doc/user-guide/commands.xml

@@ -470 +470 @@
         </bitlbee-setting>
 
-        <bitlbee-setting name="auto_reconnect_delay" type="integer" scope="global">
-                <default>300</default>
-
-                <description>
-                        <para>
-                                Tell BitlBee after how many seconds it should attempt to bring an IM-connection back up after a crash. It's not a good idea to set this value very low, it will cause too much useless traffic when an IM-server is down for a few hours.
+        <bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
+                <default>5*3&lt;900</default>
+
+                <description>
+                        <para>
+                                Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
+                        </para>
+
+                        <para>
+                                This can be one integer, for a constant delay. One can also set it to something like &quot;10*10&quot;, which means wait for ten seconds on the first reconnect, multiply it by ten on every failure. Once successfully connected, this delay is re-set to the initial value. With &lt; you can give a maximum delay.
                         </para>