| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
For some reason the protocol was being set to PF_UNIX which is
incorrect. According to the man pages and other sources (like Stevens
Unix Network Programming), the protocol should be '0' which will
use the default for the given domain. This appears to actually
work under Linux (which appears to allow 0 or 1 as the protocol without
error), but fails under Mac OSX (which only allows 0).
|
|
|
|
| |
Defaults to disabled to maintain the status quo.
|
| |
|
| |
|
|
|
|
|
| |
As far as I can see this isn't remotely exploitable (and if it were it
would be just DoS of the child process), but i'm still looking into it
|
|
|
|
|
|
| |
We only support the openldap scheme for now, with users that are
posixAccounts. Moreover, as the plugin cannot be configured directly,
you must configure libldap correctly in /etc/openldap/ldap.conf
|
|
|
|
| |
This backend authenticates users against pam.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of always putting users passwords in XML files, allow site
admins to configure a different authentication method to integrate
authentication with other systems.
This doesn't add any authentication backends yet, merely the
scaffolding. Notably:
- Password checking and loading/removing from storage has been
decoupled. A new auth_check_pass function is used to check passwords.
It does check against the configured storage first, but will handle
the authentication backends as well. The XML storage merely signals
that a user's password should be checked using an authentication
backend.
- If unknown-to-bitlbee users identify using an authentication backend,
they are automatically registered.
- If an authentication backend is used, that fact is stored in the XML
file, the password is not. Passwords are also stored unencrypted in
this case, as the password used to encrypt them can change underneath
us.
- configure and Makefile changes for the backend objects
|
|
|
|
|
|
|
|
|
|
|
| |
It's basically prepending the organization id, appending the default MUC
host from the success packet, and generating a slug based on the name
for the middle part, which is replacing a few characters with
underscores and doing a unicode aware lowercasing.
Includes tests, which are useless other than validating the initial
implementation with the test vectors that i already tested manually.
Guaranteed to detect zero breakages in the future. Good test code.
|
|
|
|
|
|
| |
I'm sure that some day the tests will be useful, not just an annoyance.
Some day.
|
|
|
|
|
|
|
| |
I can't believe the tests did something!
Returning the bare jabber_buddy when asking for GET_BUDDY_EXACT is now
acceptable, since the google talk typing commit.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
* Don't use PIE/PIC on Cygwin/Darwin unless specified as these
platforms don't support it.
* Cleanup warnings for 'make check' build.
* Fix the type issue for getsockopt calls.
* Fix enum warnings in Yahoo libs on Mac OS X.
|
|
|
|
| |
Only took me a few months to write. I even added a test case.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
unexpectedly being set to something already.
|
|
|
|
|
|
| |
completely because events.h doesn't export a way to run a single event loop
iteration.
|
|
|
|
|
|
|
|
|
| |
transliteration to work), which changes the behaviour of isalpha() (turns
out it's not a simple macro). For HTTP-encoding, this sucks, especially
when doing OAuth (which is very picky about the way HTTP encoding is done).
This should fix problems some people were seeing with posting Twitter
messages containing accents.
|
|
|
|
|
| |
the ui-fix works.
|
|
|
|
|
|
| |
build files in there. I need this to properly make Debian package variants
(i.e. libpurple and native).
|
|
|
|
|
| |
of storing full JIDs belongong to a contact.
|
| |
|
|
|
|
|
| |
broken. :-(
|
|
|
|
|
|
|
| |
for them as well. Thanks to cedk@gentoo.org for noticing (Bug #448).
Also including chat.o when building the tests to fix linking issues.
|
|
|
|
|
|
|
| |
since apparently that's how the RFC wants it. (While the rest of the JID
should be case IN-sensitive. Consistency is hard to find these days...) Also
extended the unittests a little bit. Closes #422.
|
| |
|
|
|
|
|
|
|
| |
"\r\r\n", for example, and until now BitlBee only chopped off the \r\n,
leaving the first \r as part of the command, which means it couldn't log
in to BitlBee at all. (Bad character in nickname.)
|
|
|
|
|
| |
be guessed from the encrypted data anymore.
|
| |
|
|
|
|
|
| |
described in RFC 2831 secion 7.1 (the #rule description). Closes bug #362.
|
| |
|
| |
|
|
|
|
|
|
| |
that long messages in groupchats also get wrapped properly (instead of
truncated).
|
|
|
|
|
| |
but at least I added a neat unittest...
|
|
|
|
|
| |
(compatible) ArcFour implementation.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
set when socks5 was used.
|
| | |
|
| | |
|
|/ |
|
| |
|