Red Hat Bugzilla – Bug 1016122
/usr/bin/smbpasswd in "samba-client"
Last modified: 2015-01-05 10:44:03 EST
[root@rh:~]$ rpm -q --file /usr/bin/smbpasswd
that is IMHO a mistake because i refuse to understand why i need to install the client package on a server to add a samba-user or change it's password
It is unclear what are you suggesting here.
How would you want this to happen differently?
move it to "samba" or "samba-common"?
i had yesterday to install "libsmbclient" and "samba-client"
to change one users password on a *server*
Oct 05 18:34:23 Installed: 2:libsmbclient-4.0.9-1.fc18.x86_64
Oct 05 18:34:23 Installed: 2:samba-client-4.0.9-1.fc18.x86_64
it makes really no sense that you need to install "samba-client" to get the "smbpasswd" command on a *server* where you need it to add a samba-user or change his password
until we came to conclusion how to deal with this, can you use the "pdbedit -a" tool to add and change passwords of users ? pdbedit is already in samba-common.
for now i simply added "samba-client" to my meta-packages containing "samba", but as i not that often need to add/change users and obviously cleaned up the machines proper i really wondered where the command went
I had the same problem today (F20). Samba server, users added with pdbedit and now I have to change a password. No idea how to do this with pdbedit and smbpasswd is not available even though there's a manpage installed:
$ rpm -ql samba-common-4.1.9-4.fc20.x86_64 | grep pass
So now what? Do I have to delete my smb user with pdbedit and re-add it again just to change the password? This makes no sense.
Please add smbpasswd to samba-common (or remove the smbpasswd manpage there). Thanks.
that is a *major* packaging bug and i don't get that nobody fixes this - there is no valid reason that you need "samba-client" to change a password on a server
(In reply to stadtkind2 from comment #6)
> I had the same problem today (F20). Samba server, users added with pdbedit
> and now I have to change a password. No idea how to do this with pdbedit and
> smbpasswd is not available even though there's a manpage installed:
> $ rpm -ql samba-common-4.1.9-4.fc20.x86_64 | grep pass
> So now what? Do I have to delete my smb user with pdbedit and re-add it
> again just to change the password? This makes no sense.
This is not a bug:
- The smbpasswd.so is the shared object that implements the
smbpasswd backend to the passdb pluggable subsystem in Samba.
This is used by both server and client commands.
- The smbpasswd.5 manpage is the manpage for the smbpasswd file.
This belongs to the implementation of the backend, i.e. the
- The smbpasswd binary and its accompanying manpage (smbpasswd.8)
are currently in the samba-client package, which is under discussion
here. But at least it is consistent!
We are currently discussing whether to move smbpasswd (tool+man)
to the client package. Both make some amount of sense to us.
"This is used by both server and client commands" - well, that's why it belongs to the "common" package you have installed on servers as well as clients while you typically don't need the client package on a server
(In reply to Harald Reindl from comment #9)
> "This is used by both server and client commands" - well, that's why it
> belongs to the "common" package you have installed on servers as well as
> clients while you typically don't need the client package on a server
Yes, the "it" I was referring to is in this case the
smbpasswd.so and smbpasswd.5, which *are* in the common package. :-)
so why can than be the small "/usr/bin/smbpasswd" also be there instead enforce installation of "smaba-client" just to add a new user or change a password on the server?
-rwxr-xr-x 1 root root 32K 2014-10-07 20:00 /usr/bin/smbpasswd
Yes, it could be there. I understand your reasoning.
As I wrote above: we are currently discussing the pro-s and con-s
and will update the bug report shortly.
Stay tuned - Michael
I've move the smbpasswd utility to samba-common package in rawhide.