| Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Some clients (Revolution) mistakenly believe they are not connected
until a MOTD has been received. Sending this is harmless, I guess.
|
|
This should make it easier to modify if needed.
|
|
I still hate that any of this is necessary...
|
|
Copied and expanded from catgirl.
|
|
Duration is set to INT_MAX since pounce will never accept cleartext
connections.
|
|
|
|
So the spec doesn't say I can use cap values in CAP REQ. But it also
doesn't explicitly say I can't.
|
|
|
|
It should indicate the position after having seen the tagged message.
|
|
|
|
Authors in order listed on IRCv3.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"Tag skip" like it's a speedrun :3
|
|
I think for some caps we need to filter messages without origins.
|
|
|
|
Filter functions are dealing with lines not including CRLF, so they
already have extra space. serverFormat is using snprintf which wants to
always write a NUL at the end of the string.
|
|
If a line was produced by another client, it won't have one from the
server.
|
|
|
|
Yikes.
|
|
This doesn't yet, but it will break the "robustness principle" according
to which a server "SHOULD NOT" assume that a client capable of parsing
one tag is capable of parsing all tags. In future, TagCaps will have all
other caps that use tags ORed into it, and only if the client supports
none of them will tags be filtered out.
|
|
I still think this limit is unreasonably large in comparison to 512 for
the actual message.
|
|
If there's no room left in the buffer, tls_read will return 0 (since we
gave it zero length to read into) and cause client->error to be set.
|
|
This commit introduces a '-S' command line option and a "bind" configuration
file option for selecting the source address when making outbound TCP
connections (similar to the corresponding option in catgirl(1)).
|
|
|
|
|
|
|
|
|
|
I'm pretty sure any kind of "renewing" of these is going to suck, so
just set it long enough that the world will probably be ash by then.
|
|
|
|
|
|
This disambiguates client-ca and client-pass from client-cert and
client-key, which apply to opposite sides of the program.
The old option names will continue to work.
|
|
Required for the rewind call when loading the CA.
|
|
This is a little bit messy. Allows setting either -A or -W or both.
Implements SASL EXTERNAL for clients that expect that when connecting
with a client certificate.
Need to test that reloading still works inside capsicum, since I suspect
that rewind call may be blocked.
|
|
This way things like litterbox can do it automatically without having to
be configured with a hyphen-prefixed username, which is usually invalid
anywhere else.
|
|
The other upper-case options are related to the listening side of
things, not the server side, so this is more consistent.
This is incompatible, but will fail loudly, and I expect these options
are more likely set in a configuration file, if they are set at all. I
also want to free up -A for setting a client CA, but assuming your away
message is not also an existing file path, that will continue to fail
loudly.
|
|
Oops! Clients could get pounce to quit if they didn't send a message.
|
|
Oops, thought I did this already.
|
|
|
|
Turns out the more likely thing is that the fd will just continue to be
POLLIN and produce zero-length reads.
This reverts commit 5707b15920a1ce57f01db0d592487d833218be9d.
|
|
This should maybe gracefully inform clients of what happened, but for
now this is much better than the infinite poll loop that happened
previously.
|