Skip to content

Conversation

@pkubatrh
Copy link

@pkubatrh pkubatrh commented Jan 8, 2018

Originally reported via Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1520601

@thkukuk
Copy link
Owner

thkukuk commented Jan 9, 2018

I don't like the patch at all, since this introduces special behavior based on the map names. But especially if you look at Solaris, the maps can have different names.

I have to dig deeper into the Code to find out what is correct, at least the Solaris Client code does no lower conversation of the key. But since this is the first report since over 20 years, I really doubt that this is a real issue.

@pkubatrh
Copy link
Author

pkubatrh commented Jan 9, 2018

Thanks for looking into this.

I have to dig deeper into the Code to find out what is correct, at least the Solaris Client code does no lower conversation of the key.

I have to say I have no knowledge about the Solaris version of the code but this issue was hit by one of our users trying to move from Solaris NIS client (not sure if they are still using Solaris server). So the issue is there, although I am not sure now if this is the correct place to fix it...

The culprit of this is actually (ypserv's) ypMakefile, which calls makedbm with -l when creating the map:
https://github.com/thkukuk/ypserv/blob/407890129e53c301be9cf6e5552f59f72996dd0d/scripts/ypMakefile.in#L209
So all of the host keys are converted to lowercase over there. However, making the code change in the (default) ypMakefile might break existing configurations that depend on lowercase keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants