i have a similar configuration, i trust the yellopages to do the
authentication.
basically, there are two major ways for authentication: group and name.
you can demand that the user has a certain name (with the key word
require) , and you verify it by a
passwd.
you can demand that a user is in a
On Sun, Jun 30, 2002, Orna Agmon wrote about Re: Apache vs. Samba authentication:
...
main disadvantages: the passwd file is not protected in /etc/shadow, and
is created once a (day?). on the other hand, the script which extracts the
passwd file from the database also runs under regular user
On Sun, 30 Jun 2002, Nadav Har'El wrote:
On Sun, Jun 30, 2002, Orna Agmon wrote about Re: Apache vs. Samba authentication:
...
main disadvantages: the passwd file is not protected in /etc/shadow, and
is created once a (day?). on the other hand, the script which extracts the
passwd file
I thought about totally different solution :
Add an option to AuthType option (Currently Basic and Digest).
Using some plugin that utilize some smb utility to check validity.
Where do I start from ? I am new to Apache.
i have a similar configuration, i trust the yellopages to do the
