** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/886048
Title:
“check password script” option does not reliably pass
sure, here it is! Thank you for your attention.
** Attachment added: checkpw.sh
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/886048/+attachment/2655076/+files/checkpw.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
the purpose of my “check password script” is, amongst others, to check
if a new password contains relevant portions of the username. Therefore,
it is called like this from smb.conf:
check password script = /usr/local/sbin/checkpw.sh %U
I did expect it to pass the username
Public bug reported:
from the smb.conf man page:
check password script (G)
The name of a program that can be used to check password complexity.
The password is
sent to the program's standard input.
The program must return 0 on a good password, or any other
Sorry! The option has to be set on the server where the password
actually will be changed!
I was testing this on a server with a slave LDAP directory.
** Changed in: samba (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Does setting preserve case=no solve your issues ?
No, as “touch test.test ; touch TEST.test” still creates two separate
files.
Anyhow, “touch file.test ; ls FILE.test” (correctly) returns FILE.test?
--
case sensitivity option (case sensitive=no) is not honored
–– more importantly, with “preserve case = no” it is seems to be
impossible to create mixed-case file names; but only from Windows, LINUX
does allow this…?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification
My conclusion for now:
Does setting preserve case=no solve your issues ?
YES, BUT it creates a new critical issue. With this option, it is no
longer possible to create files with the case that the file passes (see
smb.conf). They are forced to be the default case (lower).
--
case sensitivity
hm… might “short preserve case = no” be the key?
--
case sensitivity option (case sensitive=no) is not honored
https://bugs.launchpad.net/bugs/561281
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
** Changed in: samba (Ubuntu)
Status: New = Invalid
** Description changed:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test”
Public bug reported:
Binary package hint: samba
In my setup using samba's “case sensitive = no” option it is not
possible for Windows machines to create files with the same filename but
different cases. Example: “file.test” can not reside next to
“FILE.test”.
However, when a LINUX client
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43896901/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
http://launchpadlibrarian.net/43896902/SambaInstalledVersions.txt
--
case sensitivity option (case sensitive=no) is not honored
I disagree.
The problem is that when, for example, two files “test.test” and
“test.TEST” are being addressed they should be treated as the exact same
file, as case sensitivity should be off and SAMBA should not care about
letter cases. They do when being addressed by a Windows (7) machine, in
my
14 matches
Mail list logo
