In #350926, Ken Neighbors reported that, whatever the user chooses to answer to the samba/generate_smbpasswd question, that file is created anyway.
Finally, Peter Eisentraut found that smbd created it anyway and the *real* question is knowing whether one wants to *copy* the content of /etc/passwd for passdb.tdb So, the bug could be turned into a better wording of that template: Template: samba/generate_smbpasswd Type: boolean Default: false _Description: Create samba password database, /var/lib/samba/passdb.tdb? To be compatible with the defaults in most versions of Windows, Samba must be configured to use encrypted passwords. This requires user passwords to be stored in a file separate from /etc/passwd. This file can be created automatically, but the passwords must be added manually by running smbpasswd and be kept up-to-date in the future. . If you do not create it, you will have to reconfigure Samba (and probably your client machines) to use plaintext passwords. . See /usr/share/doc/samba-doc/htmldocs/ENCRYPTION.html from the samba-doc package for more details. To: Template: samba/generate_smbpasswd Type: boolean Default: false _Description: Create the samba password database from /etc/passwd? To be compatible with the defaults in most versions of Windows, Samba must be configured to use encrypted passwords. This requires user passwords to be stored in a file separate from /etc/passwd. This file can be created automatically, but the passwords must be added manually by running smbpasswd and be kept up-to-date in the future. . If you do not create it, you will have to reconfigure Samba (and probably your client machines) to use plaintext passwords. . See /usr/share/doc/samba-doc/htmldocs/ENCRYPTION.html from the samba-doc package for more details.
signature.asc
Description: Digital signature