On Wed, 2004-02-11 at 20:30, John L. Singleton wrote: > Hello all, > > I have a quick question for which I can't seem to find a reasonable answer. > > I understand that by default MaxDB does not support authentication at > the operating system level if the shadow file is encrypted with MD5. I > also understand that a possible solution for this is to remove the "md5" > line from /etc/pam.d/login, /etc/pam.d/passwd, et al, and then reset the > passwords. > > Unfortunately, this is terribly inconvenient, and in some situations > infeasible, as it requires one to reset all passwords. Does anyone know > of a way to work around this? > > The only idea I've had would be to use some sort of PAM stacking > approach. But, is MaxDB PAM aware? I checked a few of the binaries with > "ldd <binary> | grep pam" but no luck. Could anyone point me at some > documentation for MaxDB's authentication process at the operating system > level (ie, the process/steps MaxDB takes from allowing a connection from > x_server to performing authentication?)?
I may be completely wrong, but which auth do you mean ? As a linux only guy I only see 2 auths : - my standard pam auth to login as the sapdb user to perform maintenance operations like a database kernel upgrade - my database users, that have nothing to do with pam/linux/your os but are stored in the databases system tables You may be talking of the broken maxdb installer that fails in lots of situations (no shadow passwords, forcing user creation in /home for example). -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
