OTR encryption cracked #477

Closed
opened 2018-05-30 00:07:28 +00:00 by ghost · 2 comments
ghost commented 2018-05-30 00:07:28 +00:00 (Migrated from github.com)

See bitmessage's general chan

See bitmessage's general chan
ghost commented 2018-05-30 09:08:27 +00:00 (Migrated from github.com)

Oops, sorry. Misinformation.

[chan] privacy (BM-2cUJvFYHhXpBHyd96KHfjxsgTYi44BajdE)

There's a thread named "Re: OTR Interception", posted 2 days ago.

Oops, sorry. Misinformation. [chan] privacy (BM-2cUJvFYHhXpBHyd96KHfjxsgTYi44BajdE) There's a thread named "Re: OTR Interception", posted 2 days ago.
Kcchouette commented 2018-12-20 09:20:21 +00:00 (Migrated from github.com)

Quote from https://github.com/nylira/prism-break/issues/1976#issuecomment-393581507:

No one has broken OTR, and it's very unlikely that would ever happen (messages are just AES-CTR encrypted with session-specific symmetric key, maybe there could be a flaw in key negotiation but no one has pointed out one in this thread.

Can you close the issue @privacytoolsIO @Shifterovich? Thank you.

Quote from https://github.com/nylira/prism-break/issues/1976#issuecomment-393581507: > No one has broken OTR, and it's very unlikely that would ever happen (messages are just AES-CTR encrypted with session-specific symmetric key, maybe there could be a flaw in key negotiation but no one has pointed out one in this thread. Can you close the issue @privacytoolsIO @Shifterovich? Thank you.
This repo is archived. You cannot comment on issues.
No Label
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#477
No description provided.