lp:~gpolitis/bitlbee/devel

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

1 recipe using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1351. By dx on 2016-05-06

load_plugin: Improve g_module_open error message

The previous one seemed to imply a "file not found" error, which is
misleading.

1350. By dx on 2016-05-01

unix.c: Move log_link() calls before plugin initialization

This ensures that plugin load errors are logged instead of thrown away

1349. By dx on 2016-05-01

ssl_gnutls: Replace GNUTLS_STUPID_CAST with (long)

That's what the gnutls code itself uses, in all platforms.

There's a newer method that does this in a cleaner way, but it's not
supported in all the gnutls versions that bitlbee works with, so this is
simpler.

1348. By dx on 2016-04-17

twitter: Fix a couple of leaks of mutes_ids and retweets_ids

Just freeing the list on logout and when removing items from them.

Also remove the "checking mutes" debug which is disproportionately noisy
compared to the rest of the protocol.

1347. By dx on 2016-04-16

Merge remote-tracking branch 'bitlbee/pr/70'

1346. By Marius Halden <email address hidden> on 2016-04-06

Ignore CAP END when received multiple times

This fixes a segfault when CAP END was received after the capabilty
negotiation was already over.

1345. By Marius Halden <email address hidden> on 2016-03-26

Fix use of un-initialized value

1344. By Dennis Kaarsemaker on 2016-03-25

ldap authentication backend

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

1343. By Dennis Kaarsemaker on 2016-03-25

Linux pam authentication backend

This backend authenticates users against pam.

1342. By Dennis Kaarsemaker on 2016-03-25

Authentication: scaffolding for multiple authentication backends

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