| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only plain, no other methods. We don't have built-in SSL to implement
EXTERNAL (certfp) and nothing else is worth implementing.
The actual authentication is pretty much like sending a server password
(when the server's authmode isn't closed), which means it happens in
cmd_identify, but this code also calls storage_check_pass() to send the
required success/failure replies.
SASL doesn't give us much benefit other than standards compliance, but
some clients might appreciate it.
And having a fifth way to do the same thing doesn't hurt! Now we have:
- identify in &bitlbee
- identify to nickserv (alias for root)
- 'nickserv' and 'ns' irc commands
- server password
- sasl plain
|
|
|
|
|
|
|
|
|
| |
We can't actually have multiple prefixes internally, so the only thing
missing for multi-prefix compliance is actually having the prefix in the
WHO reply, which is a rfc1459 thing.
Note to future self: check irc logs for the implementation I threw away.
The one that actually handled multiple prefixes. I hope that's useful.
|
| |
|
| |
|
|
|
|
|
| |
Mostly no-op for now. Puts registration on hold, supports the basic
commands, and NAKs everything
|
|
|
|
| |
Fixes the test suite. I guess it's useful for something.
|
|
|
|
| |
Also split underscore_dedupe from nick_dedupe.
|
|
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
|
|
|
|
|
|
|
|
|
|
| |
With similar commands being supported, such as INVITE, the KICK command
should be supported as well. The key motivation behind supporting KICK
is having for having a way to remove users from group chats. As of now,
there is no way for a bitlbee user to remove a user from a group chat.
With no current KICK implementation, it made using this command a prime
candidate for the UI side of this implementation. In addition, the KICK
command has been supported in the control channel as well. This is to
keep the INVITE/KICK pair consistent.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows for users to be declared as being special, which does not
have any specific meaning. The meaning of being special is different
from protocol-to-protocol, which many protocols do not even implement.
This functionality is mainly geared towards a special user state which
only some protocols may actually need to define. For example, with the
third-party Steam plugin, this can be used for denoting a user which is
actively playing a game.
By default, this mode will not actually be used by any plugin. However,
it does default to the half-operator user mode.
|
| |
|
|
|
|
|
| |
"securely". Patch from Flexo, bug #1117.
|
| |
|
|
|
|
|
|
|
| |
my copyright mentions since some were getting pretty stale. Left files not
touched since before 2012 alone so that this change doesn't touch almost
EVERY source file.
|
|
|
|
|
|
| |
separate control channel with all contacts *not* in a certain group/from
a certain IM account/network, etc.
|
|
|
|
|
| |
Patch from trac3r, bug #814.
|
| |
|
|
|
|
|
|
| |
add new irc_usermsg, irc_usernotice.
deliver user-specific messages from libotr as notices to that user.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
well (and enter it using /OPER instead).
This is a gross hack and indeed still not solid: In irssi one can still
use /RAWLOG SAVE to find the OPER line sent to BitlBee (and of course not
everyone uses SSL to talk to remote BitlBee servers). This only works
within 10-30 minutes after entering the password though.
|
| |
|
|
|
|
|
| |
a user's message in, instead of just &bitlbee by default.
|
|
|
|
|
|
| |
in BitlBee settings that automatically end up in the existing .xml files
(or whatever storage is used), but I realise this is non-trivial.
|
|
|
|
|
|
| |
so well yet, at least when testing with Pidgin on the other side. Not sure
where the bug is.
|
|
|
|
|
| |
sense of the word, more in a way that core files don't have to include otr.h.
|
|\ |
|
| |
| |
| |
| |
| | |
channel the user can easily /join.
|
| | |
|
|\ \
| |/
|/|
| |
| | |
and parts I want to/have to redo (because of ui-fix).
|
| |\ |
|
| |\ \ |
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
replace it with a process-based stub
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- implement 'otr forget fingerprint' and 'otr forget context' commands
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- add 'otr trust' user command
- support non-otr messages during keygen
- run otr messages through strip_html
- interpret <b> and <i> tags in html messages
- record max message size in prpl
- add 'encrypted' flag to user_t
- cosmetics
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
in the current channel.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
the last_channel variable, like for any other user.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
show_offline and away_devoice and possibly other ideas into one setting
called show_users. Documentation will come soon. :-P
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
connection a quit message instead of just breaking the connection.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
IPC master.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
what the older version also did so that Irssi won't clean up the window.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
groupchats not reimplemented yet but that's the next step.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
old-style BitlBee. This so that the IRC client will show the notification
in query windows as well. Make it a setting though, for bug #539.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If someone has two MSN accts and wants contacts from both in one channel,
this is now possible.
|