Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

start session on query? #118

Open
fauno opened this issue May 29, 2015 · 10 comments
Open

start session on query? #118

fauno opened this issue May 29, 2015 · 10 comments

Comments

@fauno
Copy link
Contributor

fauno commented May 29, 2015

would it be ok to put up a hook running /otr start on /query? so if the other end is known to have otr the private chat is encrypted by default.

@Mikaela
Copy link
Contributor

Mikaela commented May 29, 2015

I think you are looking for require_encryption in /otr policy.

Another good one, but not wanted in this case is /set otr.policy.default.send_tag on.

@fauno
Copy link
Contributor Author

fauno commented May 29, 2015

ah ok, but this doesn't let you talk with people who doesn't have otr, so i guess i'm asking for something in between require_encryption and send_tag :P

@mmb
Copy link
Owner

mmb commented May 31, 2015

send_tag should start a session automatically on /query if the other party has OTR. How would this be different from send_tag?

@Mikaela
Copy link
Contributor

Mikaela commented May 31, 2015

Doesn't send_tag send the first message without OTR but ending to the whitespace tag which then makes the OTR-supporting recepient initate OTR?

@mmb
Copy link
Owner

mmb commented May 31, 2015

send_tag will send all messages with the whitespace tags (including the first message) until it receives an untagged plaintext message in response.

@Mikaela
Copy link
Contributor

Mikaela commented May 31, 2015

And what is asked here if I understand correctly is always starting query with the person automatically encrypting all messages.

@tribut
Copy link
Collaborator

tribut commented May 31, 2015

Of course you can send "?OTR?" on every query. However, with send_tags enabled, this is equivalent to sending "Hi" (which then gets the tag appended automatically).

One possible feature might be to automatically set require_encryption for every contact where an OTR session is established. But then, we would have to solve #48.

@fauno
Copy link
Contributor Author

fauno commented May 31, 2015

I'm ok with enabling require_encryption for contacts with past otr sessions :)

@mmb
Copy link
Owner

mmb commented Jun 2, 2015

It seems like the send_tag policy was meant to address the automatic setup of an OTR session if the peer supports it. It only adds whitespace so that peers who don't support OTR don't see strange OTR protocol strings in the message.

The only drawback I can see is that the first message is sent in the clear but as @tribut said you can be aware of that and only send something like "hi". @fauno is this your main objection to using send_tag?

@fauno
Copy link
Contributor Author

fauno commented Jun 2, 2015

you have to send "hi" and wait a few secs. i've seen many people starting to talk before the session is set (using otr in other plugins i admit). as i suggested in #48 plain text messages should be queued, not sent in plain text or dropped.

currently instead of "hi" i'm running /otr start and wait, but i think the're different scenarios:

  • require_encryption won't let you talk in plain text with no one. if the other end has otr, you have to wait until the session is started
  • send_tag allows plain text conversations and an opportunistic otr conversation.
  • require_encryption for people you already had otr sessions with won't let you talk to them until a new session is started

in this case i'll use send_tag with per-contact require_encryption :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants