Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:lsmcd:new_sasl [2019/11/07 22:23] Robert Perper [Creating a User Database Just for LSMCD] |
litespeed_wiki:lsmcd:new_sasl [2019/11/27 14:32] Robert Perper [LSMCD Security Using SASL] |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| As for Memcached, if you enable SASL, text telnet commands will no longer work as there is no security mechanism in telnet. The client program ''memcapable'' will fail all tests as it does not properly handle SASL. If you wish to use this program to validate functionality, a customized version of the program is available in the distribution and can be built using instructions specified in the README. | As for Memcached, if you enable SASL, text telnet commands will no longer work as there is no security mechanism in telnet. The client program ''memcapable'' will fail all tests as it does not properly handle SASL. If you wish to use this program to validate functionality, a customized version of the program is available in the distribution and can be built using instructions specified in the README. | ||
| + | |||
| + | To allow existing programs to run with SASL enabled, the Anonymous user, described in [[litespeed_wiki:lsmcd:sasl_secure_user_data|LSMCD Secure User Data Using SASL]] will allow ASCII and telnet access to an independent data area. | ||
| ===== Configuring SASL ===== | ===== Configuring SASL ===== | ||
| Line 39: | Line 41: | ||
| The sasldb database must have permissions which allow the LSMCD user read access to it (typically 640 in most environments). Since this allows read access to any user in the root group, this may not meet your security requirements. This can be circumvented by creating a SASL managed database which is accessible only to the LSMCD user. | The sasldb database must have permissions which allow the LSMCD user read access to it (typically 640 in most environments). Since this allows read access to any user in the root group, this may not meet your security requirements. This can be circumvented by creating a SASL managed database which is accessible only to the LSMCD user. | ||
| - | As above you will use the saslpasswd2 program. However, specify a database name with the `-f` parameter. For example, to create a user `user1` in the `/etc/sasllsmcd` program specify: | + | As above you will use the saslpasswd2 program. However, specify a database name with the `-f` parameter. For example, to create a user `user1` in the `/etc/sasllsmcd` database specify: |
| <code> | <code> | ||