631d334 everything that sounds like lucipam renamed to sasl2auth

Authored and Committed by jpokorny 13 years ago
    everything that sounds like lucipam renamed to sasl2auth
    
    - this is because that plugin had originally nothing to do with PAM and
      therefore the name was misleading (whether the PAM at the backend will
      be used in fact depends on how the saslauthd service is configured)
    - options of SASL server created on sasl2auth plugin are now fully
      and only configurable through /etc/sasl2/luci.conf file which can
      be used to change the backend from PAM to e.g. a SASL native database,
      Kerberos or any other mechanism that can be found by sasl libraries
      (/usr/lib[64]/sasl2/ or similar path)
      - according to
        http://www.postfix.org/SASL_README.html#server_cyrus_location,
        /ect/sasl2 location for searching SASL server configuration was
        introduced as of version 2.1.22 so requirement in spec file changed
        accordingly
    - removed unneeded "factory" function from sasl2auth plugin as this only
      passed its arguments to main object's constructor and this can be done
      directly
    
        
file modified
+2 -2
extensions/sasl2auth.c sasl_module/lucisasl.c
file renamed
+31 -17
extensions/sasl2auth.h.in sasl_module/lucisasl.h.in
file renamed
file was renamed with no change to the file
file modified
+4 -2
luci/lib/plugin_sasl2auth.py luci/lib/pamplugin.py
file renamed
+8 -13
file modified
+11 -8