|
Size: 497
Comment:
|
Size: 3004
Comment: version reference table
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Bitlbee has no native support for OTR but there are custom versions that include OTR functionality (sadly you have to compile your own bitlbee) | |
| Line 4: | Line 3: |
| some versions that include OTR Support: | When using distro packages, there is hopefully a bitlbee-plugin-otr package you can install. When compiling your own !BitlBee, pass --otr=1 or --otr=plugin to the configure script. |
| Line 6: | Line 5: |
| *One current version http://github.com/abbe/bitlbee-otr *and its corresponding blog (?) http://wahjava.wordpress.com/tag/bitlbee-otr/ *Original (outdated!) http://khjk.org/bitlbee-otr/ |
Note that this requires running your own !BitlBee. OTR functionality should not ever be offered on any public server as it only gives a false sense of security! |
| Line 10: | Line 7: |
| == Why is it that OTR is not supported upstream? == | For more information on how to use OTR, see "help otr" and other existing documentation. |
| Line 12: | Line 9: |
| because | == Version reference == |
| Line 14: | Line 11: |
| * ... | Since the OTR versions seem to be a bit confusing, here's a nice table explaining absolutely everything. || Protocol || Library || .so || debian package name || Supported bitlbee releases || Supported bitlbee bzr || || [[https://otr.cypherpunks.ca/Protocol-v2-3.1.0.html|v2]] || libotr 3.2.1 || libotr.so.2.2.1 || [[http://packages.debian.org/sid/libotr2-dev|libotr2-dev]] || 3.0 ... 3.2.1 || <=1000 || || [[https://otr.cypherpunks.ca/Protocol-v3-4.0.0.html|v3]] || libotr 4.0.0 || libotr.so.5.0.0 || [[http://packages.debian.org/sid/libotr5-dev|libotr5-dev]] || ''none yet''' || >=1001 || == OTR-related settings == * {{{otr_policy}}} (global) - see {{{help set otr_policy}}} * {{{otr_color_encrypted}}} makes OTR-Communication colored * {{{otr_does_html}}} if true, bitlbee will strip html in OTR messages * Any others? (And if anyone could update this Wiki page with more useful info on how to use thing thing that'd be great...) == Simple Question and Answer Response == Assuming that you are using a OTR build (see http://geekyschmidt.com/2011/01/02/bitlbee-and-otr-then-add-some-tor if not) then the following steps will walk you through authentication an OTR session: 1. otr connect $buddy 1. i. otr smpq $buddy 2+2 4 i. otr smp $buddy bigsecret 1. If your buddy knows your answer or secret then they will reply correctly 1. Your buddy being a smart cookie will then ask for you to respond to a question: otr smp $buddy answer 1. Done! In step 2 the breakout is question then answer. So if we wanted to do a “Where did we eat lunch 1 Jan” “Taco Bell” then you could do that also. I used 2+2 for simplicity. It is important to note that if you have logging turned on for BitlBee then your OTR messages are in vain. Also they could trace your connections via your network connection. == Issues == OTR does NOT work (well) with offline messages. This scenario was tested using Ubuntu (Oneiric Ocelot/11.10) pidgin-otr-3.2.0-5 and bitlbee-plugin-otr-3.0.3. Without previous or future chat-session, offline messages from either party will not be passed on and no notification will be sent. OTR messages are only being delivered in these scenarios: 1. User "A" and "B" are in an OTR session, when "B" is disconnecting. Messages from "A" are being delivered after "B" reconnects. 1. User "A" is attempting an OTR session with the offline-user "B", when "B" is connecting while "A" is still online. == Wiki-Suggestions == |
Get OTR to work with bitlbee
When using distro packages, there is hopefully a bitlbee-plugin-otr package you can install. When compiling your own BitlBee, pass --otr=1 or --otr=plugin to the configure script.
Note that this requires running your own BitlBee. OTR functionality should not ever be offered on any public server as it only gives a false sense of security!
For more information on how to use OTR, see "help otr" and other existing documentation.
Version reference
Since the OTR versions seem to be a bit confusing, here's a nice table explaining absolutely everything.
Protocol |
Library |
.so |
debian package name |
Supported bitlbee releases |
Supported bitlbee bzr |
libotr 3.2.1 |
libotr.so.2.2.1 |
3.0 ... 3.2.1 |
<=1000 |
||
libotr 4.0.0 |
libotr.so.5.0.0 |
none yet |
>=1001 |
OTR-related settings
otr_policy (global) - see help set otr_policy
otr_color_encrypted makes OTR-Communication colored
otr_does_html if true, bitlbee will strip html in OTR messages
- Any others?
(And if anyone could update this Wiki page with more useful info on how to use thing thing that'd be great...)
Simple Question and Answer Response
Assuming that you are using a OTR build (see http://geekyschmidt.com/2011/01/02/bitlbee-and-otr-then-add-some-tor if not) then the following steps will walk you through authentication an OTR session:
- otr connect $buddy
-
- otr smpq $buddy 2+2 4
- otr smp $buddy bigsecret
- If your buddy knows your answer or secret then they will reply correctly
- Your buddy being a smart cookie will then ask for you to respond to a question: otr smp $buddy answer
- Done!
In step 2 the breakout is question then answer. So if we wanted to do a “Where did we eat lunch 1 Jan” “Taco Bell” then you could do that also. I used 2+2 for simplicity. It is important to note that if you have logging turned on for BitlBee then your OTR messages are in vain. Also they could trace your connections via your network connection.
Issues
OTR does NOT work (well) with offline messages. This scenario was tested using Ubuntu (Oneiric Ocelot/11.10) pidgin-otr-3.2.0-5 and bitlbee-plugin-otr-3.0.3.
Without previous or future chat-session, offline messages from either party will not be passed on and no notification will be sent. OTR messages are only being delivered in these scenarios:
- User "A" and "B" are in an OTR session, when "B" is disconnecting. Messages from "A" are being delivered after "B" reconnects.
- User "A" is attempting an OTR session with the offline-user "B", when "B" is connecting while "A" is still online.