Feature #4488
Support mcabber
| Status: | Feedback | Start date: | 02/02/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Component: |
Description
Hello,
mcabber is a curse jabber client, supporting OTR. It would be great if we could import/export keys as it's done with gajim and other (graphical) clients.
OTR keys are, by default, in this location:
~/.mcabber/otr
Name is <accountaddress>.key
There's also an <accountaddress>.fpr containing contact OTR fingerprint in this display:
<contact address> <accountaddress> <protocol> <fingerprint> [trust]
The key file contains stuff like that:
(privkeys
(account
(name "<accountaddress>")
(protocol jabber)
(private-key
(dsa
(p #…#)
(q #…#)
(g #…#)
(y #…#)
(x #…#)
)
)
)
)
Which looks like the needed stuff in order to create the private key (I'm no cryptographer).
Cheers,
C.
History
#1 Updated by hans almost 3 years ago
If mcabber is based on libotr, then it should be easy for you to make keysync support mcabber. Just start with another app that is based on libotr, and modify it for mcabber. For example, otrapps/pidgin.py or otrapps/irssi.py. Then when have it working, and passing the test suite, submit a pull request and I'll happily include it.
#2 Updated by hans almost 3 years ago
- Status changed from New to Feedback
#3 Updated by Tengu almost 3 years ago
Hello Hans,
Seems it's using libotr, I'll give a try. Hopefully this week.
Cheers,
C.