Ted is still the man, but the patch I sent earlier had a
typo that prevents correct authorization processing...
To recap, in 4.0 REL, xdm is built with the ability to do
XDM-AUTHORIZATION-1, but, apparently, the servers are not.
This prevents all clients from connecting to the server. The
follo
[EMAIL PROTECTED] said:
:- It took me an hour to figure this out today, and I'll be delighted if
:- it solves your problem. :-)
You da man!
Here is the change I made. Dear core team, please add to
errata! Thanks!
*** xdm-config.orig Thu Apr 13 16:37:35 2000
--- xdm-config Thu Apr 13 16:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Robert Withrow wrote:
>I asked about this in questions...
>
>It appears that authorization is broken in XDM in 4.0 REL. At least
>if I start XDM using the default everything, just the way I have
>for the la
[EMAIL PROTECTED] said:
:- Do you have an up to date /etc?
Yes. This is a virgin installation of 4.0 REL.
bash-2.03$ uname -sr
FreeBSD 4.0-RELEASE
bash-2.03$ grep -A 6 XDM /etc/pam.conf
# XDM is difficult; it fails or moans unless there are modules for each
# of the four management groups; a
On Thu, 13 Apr 2000, Robert Withrow wrote:
> Any other ideas?
Do you have an up to date /etc?
/etc/pam.conf contains:
# XDM is difficult; it fails or moans unless there are modules for each
# of the four management groups; auth, account, session and password.
xdm authrequiredpa
I asked about this in questions...
It appears that authorization is broken in XDM in 4.0 REL. At least
if I start XDM using the default everything, just the way I have
for the last several releases, all attempts to log into the server
fail with authentication rejections.
The only suggestion on
6 matches
Mail list logo