Bug 595 - wbinfo cannot display non-ascii user names
Summary: wbinfo cannot display non-ascii user names
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Extended Characters (show other bugs)
Version: 3.0.0
Hardware: All All
: P3 normal
Target Milestone: none
Assignee: Alexander Bokovoy
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-10 00:43 UTC by Shiro Yamada
Modified: 2003-12-10 22:19 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shiro Yamada 2003-10-10 00:43:39 UTC
wbinfo cannot handle non-ascii chars, but getent can.

Here is the steps to reproduce this bug:

0. Prepare a PDC server, which has a domain user with non-ascii name,
   belonging to a non-ascii group.

1. link 'libnss_winbind.so' library
	# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2

2. edit /etc/nsswitch.conf so that NSS retrieve user info from winbindd  
	-- nsswitch.conf  -------
	passwd:     files winbind
	shadow:     files
	group:      files winbind
	-------------------------

3. load in ldconfig cache
	# ldconfig -v | grep winbind

4. stop nscd
	# killall nscd

5. edit smb.conf
	-- smb.conf ---------------
	[global]
	  security = domain
	  winbind separator = +
	  idmap uid = 10000-20000
	  winbind gid = 10000-20000
	  winbind enum users = yes
	  winbind enum groups = yes
	  template homedir = /home/%D/%U
	  template shell = /bin/bash
	---------------------------

6. join Samba server to existing NT domain as a member server
	# net rpc join -S _NT4SVR_ -U Administrator%_PASSWD_

7. start up smbd, nmbd and winbindd
	# smbd -D
	# nmbd -D
	# winbindd -B

8. retrieve user/group information using getent
	$ getent passwd
	$ getent group

9. extract user/group information using wbinfo
	$ wbinfo -u
	$ wbinfo -g
Comment 1 Shiro Yamada 2003-12-10 21:24:41 UTC
I have tested this functionality again, and this time it seems to work.
It seems as though my bizarre configuration was at the root of this problem.
Please invalidate it, from next time around I would spent more time on
verifications in prior to reporting.
Comment 2 Alexander Bokovoy 2003-12-10 22:19:34 UTC
Invalidated per reporter request