Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update idmap config syntax #47

Closed
wants to merge 1 commit into from
Closed

update idmap config syntax #47

wants to merge 1 commit into from

Conversation

aaptel
Copy link

@aaptel aaptel commented Jul 25, 2016

idmap uid/gid is obsolete

samba tools like smbclient now warn about it:

linux-fp5a:~ # smbclient //localhost/users -U aaptel-ad%'xyz'
WARNING: The "idmap gid" option is deprecated
WARNING: The "idmap uid" option is deprecated

This commit simply changes what is written to the new syntax.

It probably needs more work to detect the old syntax in the case of reading a old smb.conf but I'm not even sure this is actually a usecase we have to handle? (we always overwrite the file no?)

Signed-off-by: Aurelien Aptel <aaptel@suse.com>
@aaptel
Copy link
Author

aaptel commented Jul 25, 2016

This issue has an open ticket on bugzilla bsc#873981

@jreidinger
Copy link
Member

@ddiss can you please check it?

@aaptel changelog entry + version increase is needed. BTW will it work also on SLE12SP2 ( or opensuse 42.2 as it have same code base )? we currently share code between these two.

@aaptel
Copy link
Author

aaptel commented Aug 16, 2016

I can confirm it works on SLE12SP2 but this probably needs more work because:

  • the yast UI lets user choose different ranges for uid and gid (proposed change uses the same for both). we need to either remove that choice from the UI or add equivalent config
  • if there is an existing smb.conf file with the deprecated syntax it will add the new one (and not remove the old one)

@ddiss
Copy link
Contributor

ddiss commented Aug 17, 2016

I think changing the UI to only offer a single range would make sense here. Existing "idmap uid/gid" configs with matching ranges (a likely occurrence) could be safely converted to use the new parameter.
configs with non-matching ranges should not be affected by the change, but instruct administrators that manual configuration is required.

@teclator
Copy link
Contributor

teclator commented Apr 5, 2017

@aaptel what is the state of this PR?, do you plan to change the UI or work on it?

@teclator
Copy link
Contributor

teclator commented Apr 6, 2018

@aaptel @noelpower @ddiss almost two years have passed since the PR was created, could you please check if it is valid and add the missing changelog + version increase for being able to merge it? If not we will probably close it as no response from a while.

@ddiss
Copy link
Contributor

ddiss commented Apr 6, 2018

It's still valid IMO, but needs work as per my last comment. I've updated the bug to track this for future releases

@ddiss ddiss closed this Apr 6, 2018
@teclator
Copy link
Contributor

teclator commented Apr 6, 2018

@ddiss thnx for taking care

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants