gnu-social

History

Mikael Nordfeldth 2a4dc77a63 The overloaded DB_DataObject function staticGet is now called getKV I used this hacky sed-command (run it from your GNU Social root, or change the first grep's path to where it actually lies) to do a rough fix on all ::staticGet calls and rename them to ::getKV sed -i -s -e '/DataObject::staticGet/I!s/::staticGet/::getKV/Ig' $(grep -R ::staticGet `pwd`/* \| grep -v -e '^extlib' \| grep -v DataObject:: \|grep -v "function staticGet"\|cut -d: -f1 \|sort \|uniq) If you're applying this, remember to change the Managed_DataObject and Memcached_DataObject function definitions of staticGet to getKV! This might of course take some getting used to, or modification fo StatusNet plugins, but the result is that all the static calls (to staticGet) are now properly made without breaking PHP Strict Standards. Standards are there to be followed (and they caused some very bad confusion when used with get_called_class) Reasonably any plugin or code that tests for the definition of 'GNUSOCIAL' or similar will take this change into consideration.	2013-08-18 13:13:56 +02:00
..
AuthCryptPlugin.php	The overloaded DB_DataObject function staticGet is now called getKV	2013-08-18 13:13:56 +02:00
README	new plugin to check, store and migrate password hashes to crypt()	2013-08-12 12:54:51 +02:00

Mikael Nordfeldth 2a4dc77a63 The overloaded DB_DataObject function staticGet is now called getKV

I used this hacky sed-command (run it from your GNU Social root, or change the first grep's path to where it actually lies) to do a rough fix on all ::staticGet calls and rename them to ::getKV

   sed -i -s -e '/DataObject::staticGet/I!s/::staticGet/::getKV/Ig' $(grep -R ::staticGet `pwd`/* | grep -v -e '^extlib' | grep -v DataObject:: |grep -v "function staticGet"|cut -d: -f1 |sort |uniq)

If you're applying this, remember to change the Managed_DataObject and Memcached_DataObject function definitions of staticGet to getKV!

This might of course take some getting used to, or modification fo StatusNet plugins, but the result is that all the static calls (to staticGet) are now properly made without breaking PHP Strict Standards. Standards are there to be followed (and they caused some very bad confusion when used with get_called_class)

Reasonably any plugin or code that tests for the definition of 'GNUSOCIAL' or similar will take this change into consideration.

2013-08-18 13:13:56 +02:00

AuthCryptPlugin.php

The overloaded DB_DataObject function staticGet is now called getKV

2013-08-18 13:13:56 +02:00

README

new plugin to check, store and migrate password hashes to crypt()

2013-08-12 12:54:51 +02:00

README

AuthCrypt allows for StatusNet to use crypt() hashing to store password credentials.

Requirements
============
* PHP >= 5.3.2 with php5-mcrypt extension for certain SHA512 support
* lib/authenticationplugin.php in your StatusNet install

Installation
============
Add either of the following configurations to your config.php (see Example below for more options):

    addPlugin('AuthCrypt');

The recommended use is to overwrite old hash values when logging in (hostile mode) and be the authority on password checks when logging in. If you only wish to update entries on password change the default values are enough.

    addPlugin('AuthCrypt', array(
        'authoritative'=>true,
        'hostile'=>true,
    ));

To disable updating to crypt() on password change, simply set the 'overwrite' setting to false:

    addPlugin('AuthCrypt', array(
        'overwrite'=>false,
    ));

Settings
========
Default values in parenthesis. Many settings are inherited from the AuthenticationPlugin class.

authoritative (false): Set to true when all passwords are hashed with crypt()
    (warning: this may disable all other password verification, also when changing passwords!)
hash ('$6$'): Hash signature to use, defaults to SHA512. See all supported strings at http://php.net/crypt
    (warning: set this to something crypt() understands, or you will default to the very weak 2-char DES scheme)
hostile (false): Do we update the password hash entries on login?
    (notice: will check password login against old-style hash and then update using crypt())
overwrite (true): Do we overwrite old style password hashes with crypt() hashes on password change?
    (notice: to make use of stronger security or migrate to crypt() hashes, this must be true)
password_changeable (true): Enables or disables password changing.
    (notice: if combined with authoritative, it disables changing passwords and removes option from menu.)
autoregistration: This setting is ignored. Password can never be valid without existing User.
provider_name: This setting defaults to 'crypt' but is never stored anywhere.

Todo
====
This does not in any way get in touch with common_munge_password, which is 
called upon User::register(...) and RecoverpasswordAction->resetPassword().
Maybe there should be an event like StartMungePassword in the core?