User:B42/OTR - Revision history

imported>B42: Replaced content with "[http://wiki.znc.in/Otr This page has been moved to ZNC wiki.]"

2014-04-12T10:04:17Z

Replaced content with "[http://wiki.znc.in/Otr This page has been moved to ZNC wiki.]"

imported>B42 at 09:53, 11 April 2014

2014-04-11T09:53:54Z

← Older revision		Revision as of 09:53, 11 April 2014
Line 11:		Line 11:
	[https://github.com/mmilata/znc-otr/archive/master/znc-otr-master.tar.gz tarball]		[https://github.com/mmilata/znc-otr/archive/master/znc-otr-master.tar.gz tarball]
	directly if you don't want to use git. Once you have the source code, install the module		directly if you don't want to use git. Once you have the source code, install the module
	by running ''make'' and ''make install'' in ~~the unpacked sour~~		by running ''make'' and ''make install'' in znc-otr's directory. See
	~~follow the instructions for [http://wiki.~~znc.~~in/Compiling_modules compiling]~~		[http://wiki.znc.in/Modules#.28Un.29Loading_Modules Loading modules] for instructions
	~~and~~ [http://wiki.znc.in/Modules#.28Un.29Loading_Modules ~~loading ZNC~~ modules].		for loading the module.

	If your ZNC is running on a virtual server (see		If your ZNC is running on a virtual server (see

imported>B42 at 09:53, 11 April 2014

2014-04-11T09:53:03Z

← Older revision		Revision as of 09:53, 11 April 2014
Line 10:		Line 10:
	download a		download a
	[https://github.com/mmilata/znc-otr/archive/master/znc-otr-master.tar.gz tarball]		[https://github.com/mmilata/znc-otr/archive/master/znc-otr-master.tar.gz tarball]
	directly if you don't want to use git. Once you have the source code,		directly if you don't want to use git. Once you have the source code, install the module
			by running ''make'' and ''make install'' in the unpacked sour
	follow the instructions for [http://wiki.znc.in/Compiling_modules compiling]		follow the instructions for [http://wiki.znc.in/Compiling_modules compiling]
	and [http://wiki.znc.in/Modules#.28Un.29Loading_Modules loading ZNC modules].		and [http://wiki.znc.in/Modules#.28Un.29Loading_Modules loading ZNC modules].

imported>B42 at 21:01, 10 April 2014

2014-04-10T21:01:50Z

← Older revision		Revision as of 21:01, 10 April 2014
Line 109:		Line 109:
	This command is also used to reply to authentication requests started by the other side.		This command is also used to reply to authentication requests started by the other side.

	Example:		Example (you are alice):
	<pre>		<pre>
	<alice> Let's authenticate with the answer to following question: what is my favorite book?		<alice> Let's authenticate with the answer to following question: what is my favorite book?
Line 165:		Line 165:
	<*otr> carol		<*otr> carol
	<*otr> elvis		<*otr> elvis
	/msg otr ignore ~~foo~~		/msg otr ignore Guest
	<otr> Added ~~foo~~ to OTR ignore list.		<otr> Added Guest to OTR ignore list.
	/msg *otr ignore --remove carol		/msg *otr ignore --remove carol
	<*otr> Removed carol from OTR ignore list		<*otr> Removed carol from OTR ignore list
	/msg *otr ignore		/msg *otr ignore
	<*otr> elvis		<*otr> elvis
	<otr> ~~foo~~		<otr> Guest
	</pre>		</pre>

imported>B42: test

2014-04-10T20:50:31Z

test

← Older revision		Revision as of 20:50, 10 April 2014
Line 56:		Line 56:
	Example:		Example:
	<pre>		<pre>
	~~<alice>~~ info		/msg *otr info
	<*otr> +-------+-----------+----------------------------------------------+-----+---------------+		<*otr> +-------+-----------+----------------------------------------------+-----+---------------+
	<*otr> \| Peer \| State \| Fingerprint \| Act \| Trust \|		<*otr> \| Peer \| State \| Fingerprint \| Act \| Trust \|
Line 84:		Line 84:
	Example:		Example:
	<pre>		<pre>
	~~<alice>~~ trust bob		/msg *otr trust bob
	<*otr> [bob] Fingerprint 94A1353B 60A58E73 82CE8999 CBBD7B92 5E9EBB87 trusted!		<*otr> [bob] Fingerprint 94A1353B 60A58E73 82CE8999 CBBD7B92 5E9EBB87 trusted!
	~~<alice>~~ trust 378A8445 3FC3933C 73C917C8 BFE4C18B 5CE65CFC		/msg *otr trust 378A8445 3FC3933C 73C917C8 BFE4C18B 5CE65CFC
	<*otr> [carol] Fingerprint 378A8445 3FC3933C 73C917C8 BFE4C18B 5CE65CFC trusted!		<*otr> [carol] Fingerprint 378A8445 3FC3933C 73C917C8 BFE4C18B 5CE65CFC trusted!
	</pre>		</pre>
Line 116:		Line 116:
	</pre>		</pre>
	<pre>		<pre>
	~~<alice>~~ auth bob the old man and the sea		/msg *otr auth bob the old man and the sea
	<*otr> [bob] Initiated authentication.		<*otr> [bob] Initiated authentication.
	(bob now does something similar in his client)		(bob now does something similar in his client)
Line 135:		Line 135:
	Example:		Example:
	<pre>		<pre>
	~~<alice>~~ authq bob [What is my favorite book (no caps)?] the old man and the sea		/msg *otr authq bob [What is my favorite book (no caps)?] the old man and the sea
	<*otr> [bob] Initiated authentication.		<*otr> [bob] Initiated authentication.
	(bob's client displays the question and he types the answer)		(bob's client displays the question and he types the answer)
Line 161:		Line 161:
	Example:		Example:
	<pre>		<pre>
	~~<alice>~~ ignore		/msg *otr ignore
	<*otr> OTR is disabled for following nicks:		<*otr> OTR is disabled for following nicks:
	<*otr> carol		<*otr> carol
	<*otr> elvis		<*otr> elvis
	~~<alice>~~ ignore foo*		/msg otr ignore foo
	<otr> Added foo to OTR ignore list.		<otr> Added foo to OTR ignore list.
	~~<alice>~~ ignore --remove carol		/msg *otr ignore --remove carol
	<*otr> Removed carol from OTR ignore list		<*otr> Removed carol from OTR ignore list
	~~<alice>~~ ignore		/msg *otr ignore
	<*otr> elvis		<*otr> elvis
	<otr> foo		<otr> foo

imported>B42: add ignore

2014-04-10T20:46:53Z

add ignore

@@ Line 1: / Line 1: @@
-This module allows you to encrypt private conversations using the [https://otr.cypherpunks.ca/ OTR protocol].
+This module allows you to encrypt private conversations using the
-Several popular [https://otr.cypherpunks.ca/software.php IRC clients] support OTR (usually requiring a plugin).
+[https://otr.cypherpunks.ca/ OTR protocol]. Several popular
 For more information about OTR, see https://otr.cypherpunks.ca/ and https://otr.im/.
@@ Line 20: / Line 21: @@
 == Usage ==
 To request OTR-encrypted conversation with someone, send them the message
 ''?OTR?'' in a private conversation. If the request succeeds the module informs
@@ Line 95: / Line 97: @@
 Terminates the OTR conversation with ''nick''. They are notified that the conversation ended.
-Note that when ''nick'' terminates the conversation first, you have to use this command as well (or start new OTR session). This is to prevent the situation when the other side ends the OTR session just before you hit Enter and send in plaintext something you assumed will be encrypted.
+Note that when ''nick'' terminates the conversation first, you have to use this command as well
 ==== auth <nick> <secret> ====
@@ Line 147: / Line 151: @@
 Use with the '''--overwrite''' parameter to throw away the old key and generate
 a new one.
 == Security considerations ==

imported>B42: /* Bugs */

2014-04-10T13:03:54Z

Bugs

← Older revision		Revision as of 13:03, 10 April 2014
Line 156:		Line 156:

	== Bugs ==		== Bugs ==
	The quality of OTR implementation in IRC clients varies greatly. Sometimes the OTR conversation can get to a state where OTR needs to be restarted by using the finish command and then sending ''?OTR?'' to your peer.		The quality of OTR implementation in IRC clients varies greatly. Sometimes the OTR conversation can get to a state where OTR needs to be restarted by using the ''finish'' command and then sending ''?OTR?'' to your peer again.

	You can report bugs on https://github.com/mmilata/znc-otr/issues or by contacting ''b42'' on freenode.		You can report bugs on https://github.com/mmilata/znc-otr/issues or by contacting ''b42'' on freenode.

imported>B42: /* Security considerations */

2014-04-10T13:02:59Z

Security considerations

← Older revision		Revision as of 13:02, 10 April 2014
Line 150:		Line 150:
	== Security considerations ==		== Security considerations ==
	* In most cases it is best not to use this ZNC module and use OTR directly on the client you use to connect to the bouncer instead. This way you don't have to rely on the security of the server, which might be difficult to achieve.		* In most cases it is best not to use this ZNC module and use OTR directly on the client you use to connect to the bouncer instead. This way you don't have to rely on the security of the server, which might be difficult to achieve.
	* Use SSL to connect to the bouncer, otherwise the messages ~~are sent in~~ the ~~plaintext~~.		* Use SSL to connect to the bouncer, otherwise the messages can be intercepted between ZNC and the client.
	* Make sure to turn off logging BOTH on the bouncer (disable the [http://wiki.znc.in/Log log] module) AND at the client you use to connect to the bouncer!		* Make sure to turn off logging BOTH on the bouncer (disable the [http://wiki.znc.in/Log log] module) AND at the client you use to connect to the bouncer!
	* It is recommended to only use this module if you are in full control of the ZNC server and are its only user. The bouncer admin, root user of the machine it runs on and the admin of the host ~~machine~~ (in case you are running on a VPS) all have access to your conversations and your private keys, which they can give to other people, either intentionally or by making mistakes with regard to security.		* It is recommended to only use this module if you are in full control of the ZNC server and are its only user. The bouncer admin, root user of the machine it runs on, and the admin of the virtual host (in case you are running on a VPS) all have access to your conversations and your private keys, which they can give to other people, either intentionally or by making mistakes with regard to security.
	* By disregarding these security measures, you compromise your conversation partner's security as well as yours.		* By disregarding these security measures, you compromise your conversation partner's security as well as yours.

imported>B42: /* Security considerations */

2014-04-10T13:00:57Z

Security considerations

← Older revision		Revision as of 13:00, 10 April 2014
Line 150:		Line 150:
	== Security considerations ==		== Security considerations ==
	* In most cases it is best not to use this ZNC module and use OTR directly on the client you use to connect to the bouncer instead. This way you don't have to rely on the security of the server, which might be difficult to achieve.		* In most cases it is best not to use this ZNC module and use OTR directly on the client you use to connect to the bouncer instead. This way you don't have to rely on the security of the server, which might be difficult to achieve.
	* Use SSL to connect to the ~~server~~, otherwise the messages are sent in the plaintext ~~between you and the bouncer~~.		* Use SSL to connect to the bouncer, otherwise the messages are sent in the plaintext.
	* Make sure to turn off logging BOTH on the bouncer (disable the [http://wiki.znc.in/Log log] module) AND at the client you use to connect to the bouncer!		* Make sure to turn off logging BOTH on the bouncer (disable the [http://wiki.znc.in/Log log] module) AND at the client you use to connect to the bouncer!
	* It is recommended to only use this module if you are in full control of the ZNC server and are its only user. The bouncer admin, root user of the machine it runs on and the admin of the host machine (in case you are running on a VPS) all have access to your conversations and your private keys, which they can give to other people, either intentionally or by making mistakes with regard to security.		* It is recommended to only use this module if you are in full control of the ZNC server and are its only user. The bouncer admin, root user of the machine it runs on and the admin of the host machine (in case you are running on a VPS) all have access to your conversations and your private keys, which they can give to other people, either intentionally or by making mistakes with regard to security.

imported>B42: /* authq */

2014-04-10T12:59:56Z

authq

← Older revision		Revision as of 12:59, 10 April 2014
Line 121:		Line 121:
	==== authq <nick> <[question]> <secret> ====		==== authq <nick> <[question]> <secret> ====
	This is similar as ''auth'' except that the question is sent as part of the		This is similar as ''auth'' except that the question is sent as part of the
	authentication request. This allows ~~some~~ graphical ~~client~~ to e.g. display the		authentication request. This allows graphical clients to e.g. display the
	question in a dialog box asking for the answer.		question in a dialog box asking for the answer.