| 1 |
9 Mar 2016: |
| 2 |
- Release 4.1.1 |
| 3 |
- Fix an integer overflow bug that can cause a heap buffer overflow (and |
| 4 |
from there remote code execution) on 64-bit platforms |
| 5 |
- Fix possible free() of an uninitialized pointer |
| 6 |
- Be stricter about parsing v3 fragments |
| 7 |
- Add a testsuite ("make check" to run it), but only on Linux for now, |
| 8 |
since it uses Linux-specific features such as epoll |
| 9 |
- Fix a memory leak when reading a malformed instance tag file |
| 10 |
- Protocol documentation clarifications |
| 11 |
|
| 12 |
21 Oct 2014: |
| 13 |
- Release 4.1.0 |
| 14 |
- Modernized autoconf build system |
| 15 |
- Use constant-time comparisons where needed |
| 16 |
- Use gcrypt secure memory allocation |
| 17 |
- Correctly reject attempts to fragment a message into too many pieces |
| 18 |
- Fix a missing opdata when sending message fragments |
| 19 |
- Don't lose the first user message when REQUIRE_ENCRYPTION is set |
| 20 |
- Fix some memory leaks |
| 21 |
- Correctly check for children contexts' state when forgetting a context |
| 22 |
- API Changes: |
| 23 |
- Added API functions otrl_context_find_recent_instance and |
| 24 |
otrl_context_find_recent_secure_instance. |
| 25 |
|
| 26 |
24 Aug 2012: |
| 27 |
- Release 4.0.0 |
| 28 |
- Support v3 of the OTR protocol |
| 29 |
- The main new feature: sensibly handle the case where a user is logged |
| 30 |
in multiple times to the same IM account |
| 31 |
- API changes: |
| 32 |
- instance tags, to support multiple simultaneous logins |
| 33 |
- support for asynchronous private key generation |
| 34 |
- the ability to provide an "extra" symmetric key to applications |
| 35 |
(with forward secrecy) |
| 36 |
- applications can supply a formation conversion callback if they do |
| 37 |
not natively use XHTML-style UTF8 markup |
| 38 |
- error messages formerly provided by libotr are now handled using |
| 39 |
callbacks to the application, for better i18n support |
| 40 |
- otrl_message_sending now handles message fragmentation internally |
| 41 |
|
| 42 |
27 May 2008: |
| 43 |
- Added support for one-way authentication using an explicit question, |
| 44 |
based on the SOUPS 2008 user study. |
| 45 |
|
| 46 |
1 Aug 2007: |
| 47 |
- Released 3.1.0 |
| 48 |
|
| 49 |
24 Jul 2007: |
| 50 |
- Added fragmentation support for large messages |
| 51 |
- Added new method for buddy authentication which does not require the |
| 52 |
(explicit) use of fingerprints. |
| 53 |
|
| 54 |
02 Nov 2005: |
| 55 |
- Released 3.0.0 |
| 56 |
|
| 57 |
16 Oct 2005: |
| 58 |
- Major overhaul with implementation of version 2 of the protocol. |
| 59 |
|
| 60 |
24 Jun 2005: |
| 61 |
- Remove the "confirm_fingerprint" callback which requires the user to |
| 62 |
acknowledge the new fingerprint before it can be used. Replace it |
| 63 |
with a "new_fingerprint" callback which merely informs the user that a |
| 64 |
new fingerprint has been received. |
| 65 |
- Allow the app to set a "trust level" for fingerprints. This is an |
| 66 |
arbitrary string, intended to indicate whether (or possibly by what |
| 67 |
means) the user has verified that this fingerprint is accurate. |
| 68 |
- Clarify that, if the user requests to see the secure session id in |
| 69 |
the middle of the conversation, the value displayed should be the one |
| 70 |
calculated at the time the private connection was established (the |
| 71 |
last Key Exchange Message that caused a rekeying), _not_ the DH secure |
| 72 |
id calculated from DH keys in more recent Data Messages. |
| 73 |
|
| 74 |
03 May 2005: |
| 75 |
- Released 2.0.2 |
| 76 |
|
| 77 |
16 Feb 2005: |
| 78 |
- Released 2.0.1 |
| 79 |
- Don't send encrypted messages to a buddy who has disconnected his |
| 80 |
private connection with us. |
| 81 |
- Don't show the user the "the last message was resent" notice if the |
| 82 |
message has never actually been sent before. |
| 83 |
- Fix a crash bug that happened when messages were retransmitted under |
| 84 |
certain circumstances. |
| 85 |
|
| 86 |
08 Feb 2005: |
| 87 |
- Released 2.0.0 |
| 88 |
- Keep track of whether a given message is eligible for retransmission |
| 89 |
|
| 90 |
02 Feb 2005: |
| 91 |
- Released 1.99.0, the first preview release of 2.0.0 |
| 92 |
|
| 93 |
31 Jan 2005: |
| 94 |
- Machine-readable records can now be attached to Data Messages inside |
| 95 |
the private channel. |
| 96 |
|
| 97 |
30 Jan 2005: |
| 98 |
- New OtrlUserState datatype encapsulates private keys and known |
| 99 |
fingerprints, instead of having a single global list. |
| 100 |
- Added libotr.m4 for helping to autoconfiscate packages that use |
| 101 |
libotr. |
| 102 |
- Resend the last message if it caused a re-keying. |
| 103 |
- New OtrlPolicy datatype allows you to specify a per-connection OTR |
| 104 |
policy: never use OTR, OTR only if manually requested, automatically |
| 105 |
start OTR if possible, refuse to *not* use OTR. |
| 106 |
- New callbacks: display_otr_message, policy, is_logged_in |
| 107 |
|
| 108 |
22 Jan 2005: |
| 109 |
- Released 1.0.4 |
| 110 |
- Log, but otherwise ignore, unrecognized OTR messages. |
| 111 |
- Initial autoconfiscation, thanks to Greg Troxel <[email protected]>. |
| 112 |
|
| 113 |
18 Jan 2005: |
| 114 |
- Released 1.0.3 |
| 115 |
- Split gaim-otr and libotr into separate packages. |
| 116 |
|
| 117 |
13 Jan 2005: |
| 118 |
- Generate private keys automatically, if needed. Show a Please Wait |
| 119 |
dialog while this is happening. |
| 120 |
- We may as well try to use the "tag" method of checking for OTR, even |
| 121 |
when we don't already know a fingerprint for the correspondent. |
| 122 |
- Add version checking to the otrl_init() call. |
| 123 |
|
| 124 |
12 Jan 2005: |
| 125 |
- Refactored the logic parts of gaim-otr into libotr, so they can be |
| 126 |
shared by other libotr-enabled apps. |
| 127 |
|
| 128 |
21 Dec 2004: |
| 129 |
- Released 1.0.2 |
| 130 |
- If a Man-in-the-Middle steals both Alice's and Bob's DSA private keys, |
| 131 |
he can perform a birthday attack to try to get his session id with |
| 132 |
each end to match. Since the session id was only 64 bits long, his |
| 133 |
work was only 2^32, which is not enough. We now make the session id |
| 134 |
the whole SHA-1 hash, instead of truncating it. |
| 135 |
- Made otr_sesskeys output the calculated public key as well, for added |
| 136 |
ease of forging messages when you don't know any plaintext. |
| 137 |
|
| 138 |
14 Dec 2004: |
| 139 |
- Released 1.0.1 |
| 140 |
- Added a more sensible error message in the event that we receive our |
| 141 |
own OTR Key Exchange messages. |
| 142 |
- If we're about to send a plaintext message to a correspondent for whom |
| 143 |
we've got a fingerprint, append a special (whitespace) OTR tag |
| 144 |
sequence. The other side (if in fact running OTR) will recognize it |
| 145 |
and start a Key Exchange. |
| 146 |
|
| 147 |
12 Dec 2004: |
| 148 |
- Released 1.0.0 |
| 149 |
|
| 150 |
11 Dec 2004: |
| 151 |
- OTR button now gets sensitized and desensitized along with the other |
| 152 |
buttons in the conversation window when you log in and out of |
| 153 |
accounts. |
| 154 |
|
| 155 |
10 Dec 2004: |
| 156 |
- Released 0.9.9rc2 |
| 157 |
- Heartbeats now only get sent if (1) we have just received a message, |
| 158 |
and (2) we haven't sent one to that user in over a minute. |
| 159 |
|
| 160 |
09 Dec 2004: |
| 161 |
- Back out of the sending of heartbeats. They were causing too many |
| 162 |
problems. It seems some networks don't let buddies know when you |
| 163 |
log out, and then you get a dialog box "unable to send message" each |
| 164 |
minute. :-( |
| 165 |
|
| 166 |
08 Dec 2004: |
| 167 |
- Released 0.9.9rc1 |
| 168 |
- Removed the 100 private connection limit, by not using a fixed amount |
| 169 |
of secure memory. Unfortuantely, this means that *no* memory is |
| 170 |
pinned any more, but pinning only ever happened before in the unlikely |
| 171 |
event you ran gaim as root. |
| 172 |
- Changed the "Private connection with (username) refreshed" dialog at |
| 173 |
Paul's request so that it's no longer in "scary" "evil" bold, and |
| 174 |
rephrased it so it's less likely to be misread as "refused" instead of |
| 175 |
"refreshed". ;-) |
| 176 |
- We now send heartbeats (OTR Data Messages with an empty message part) |
| 177 |
once a minute, to anyone we're confident is still online. If both |
| 178 |
sides are doing this, then keys get rotated regularly, even if one |
| 179 |
or both sides aren't actively typing. This aids perfect forward |
| 180 |
secrecy. |
| 181 |
|
| 182 |
04 Dec 2004: |
| 183 |
- Fixed a bug wherein multi-person chat windows would get the OTR button |
| 184 |
in their button bar if the OTR plugin was enabled when one of them was |
| 185 |
active. |
| 186 |
|
| 187 |
03 Dec 2004: |
| 188 |
- Released 0.9.1 |
| 189 |
|
| 190 |
02 Dec 2004: |
| 191 |
- Clicking "OTR: Private" when you're already private will display an |
| 192 |
info dialog letting you know the connection was refreshed (assuming it |
| 193 |
actually is; if the other side isn't running OTR at all, the dialog |
| 194 |
doesn't show, and if the other side had lost its private connection, a |
| 195 |
new one will be established, with the "new private connection" dialog |
| 196 |
displayed to each side (as before)). |
| 197 |
- The toolip for "OTR: Private" is now "Refresh the private connection". |
| 198 |
- "make install" now depends on "make all". |
| 199 |
- Added man page for OTR toolkit programs |
| 200 |
- Log a debug message when we receive and discard a heartbeat |
| 201 |
|
| 202 |
1 Dec 2004: |
| 203 |
- Fixed the Makefiles so that "make clean" also removes the binaries |
| 204 |
- Fixed the Makefiles so that they install into DESTDIR |
| 205 |
- Added packaging/debian |
| 206 |
|
| 207 |
30 Nov 2004: |
| 208 |
- Released 0.9.0 |
| 209 |
- Included the OTR Messaging Toolkit. See the README for details. |
| 210 |
|
| 211 |
28 Nov 2004: |
| 212 |
- Finished the Protocol document |
| 213 |
- Changed the name of the plugin binary from "otr-plugin.so" to |
| 214 |
"gaim-otr.so". *** NOTE: this means you'll have to (1) remove the |
| 215 |
old otr-plugin.so file from your plugins directory, and (2) re-enable |
| 216 |
the Off-the-Record Messaging plugin in the Preferences panel. |
| 217 |
- Included MAC keys used to create messages in the revealed MAC section |
| 218 |
of the Data message, in addition to MAC keys used to verify messages. |
| 219 |
- Set all exported symbols to start with otrl_ (for the library) or |
| 220 |
otrg_ (for the gaim plugin), in preparation for moving the pieces |
| 221 |
into their own directories. |
| 222 |
- If we receive a Data message with no actual message in it, don't |
| 223 |
display it to the user. This may eventually be useful for doing |
| 224 |
"heartbeat" key rotations. |
| 225 |
- Separated libotr and gaim-otr into their own directories. |
| 226 |
|
| 227 |
27 Nov 2004: |
| 228 |
- Switched from using gaim_notify_* to a slightly modified version that |
| 229 |
doesn't grab the focus |
| 230 |
|
| 231 |
26 Nov 2004: |
| 232 |
- Put all the cipher operations in secure memory. This makes each |
| 233 |
private connection take 9472 bytes of secure memory, so we up the |
| 234 |
available amount of secure memory to 100 times that. Eventually, |
| 235 |
we'd like to make this dynamically grow. |
| 236 |
|
| 237 |
25 Nov 2004: |
| 238 |
- Released 0.8.3 |
| 239 |
- Don't put the DSA keys in libgcrypt secure memory, since (a) we read |
| 240 |
them off disk anyway, and (b) we want to avoid running out of secure |
| 241 |
memory. |
| 242 |
- Removed the "Do you want to start a private conversation" dialogs when |
| 243 |
one side in encrypted and the other side isn't, and instead just try |
| 244 |
to start one if we know for sure the other side supports it. |
| 245 |
- Sped up the DH computations by using a 320-bit exponent. |
| 246 |
|
| 247 |
23 Nov 2004: |
| 248 |
- Released 0.8.2 |
| 249 |
- There was a crash if you received an OTR Query before setting up a |
| 250 |
private key. Fixed. |
| 251 |
- The fingerprint in the UI is now selectable, for cut/paste. |
| 252 |
- *** Protocol change. We're no longer backward compatible. |
| 253 |
- The "revealed MAC keys" moved out of the MAC'd region of the data |
| 254 |
packet. It's not wrong where it is, but it's more obviously |
| 255 |
correct in the new place. |
| 256 |
|
| 257 |
22 Nov 2004: |
| 258 |
- Released 0.8.1 |
| 259 |
- Jabber wasn't working, for two reasons: |
| 260 |
- it sticks <tags>...</tags> around the message |
| 261 |
- it refers to the same user by multiple names; e.g. "[email protected]" |
| 262 |
vs. "[email protected]/Gaim" |
| 263 |
Both are now fixed: we look for the OTR message anywhere in the packet |
| 264 |
now, not just at the beginning, and we normalize all usernames. |
| 265 |
- Each account now has its own private key / fingerprint |
| 266 |
- This is so you don't automatically leak the information that the |
| 267 |
accounts are owned by the same person |
| 268 |
- There's a better indicator of private / not private status in the |
| 269 |
conversation window, which you can click to start the private |
| 270 |
communication. |
| 271 |
|
| 272 |
21 Nov 2004: |
| 273 |
- Initial 0.8.0 release |