>>>>> "Alban" == Alban Browaeys <[email protected]> writes:
Alban> Have you seen my update on this issue ? Ie the release is
Alban> close. I don't know how to diagnose this issue further (ie
Alban> why LAN domain is not resolved at all by pam_access). And I
Alban> don't think I will be able to devote enough time to learn how
Alban> to diagnose that until the release. Obviously it only
Alban> affects users using pam_access but still it seems it will
Alban> lock them out of their boxes. It could well be an upstream
Alban> issue. It could also be debops setups are the only left using
Alban> pam_access. Or that pam 1.7 is not yet widespread.
Alban> Though the issue should probably be moved to the upstream bug
Alban> tracker.
I don't think pam_access is very widespread, so I do not consider this
release critical.
If we find a code change that makes things better I'd be open to working
on the necessary paperwork to get it into a stable release.
At this point I don't understand the issue well enough to report it to
upstream.
I think what we know is that under some circumstances pam_access does
not work well with reverse resolving the names of local machines when
avahi is running.
At first you thought it was that avaahi was being preferred and .local
ended up getting preferred to .lan.
But now it sounds more complicated.
This is not an issue I'm going to dedicate a lot of time to either.
One thing you could do to help would be to put together a test case to
reproduce--especially if you could do that as a simple container config
or similar.
