RE: [Samba] permission bits clobbered
Update: This effect only seem to happen if the file's name begins with a dot, e.g. .secretfile It does not happen for secretfile as I have previously claimed. -Original Message- From: Panko, Kevin [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 10:55 AM To: [EMAIL PROTECTED] Subject: RE: [Samba] permission bits clobbered The '' creates a new file, but ONLY if the file did NOT exist before. If it does exist, the file's contents are replaced, but it still the same file. This is the way it works on both Windows and Unix. This command: echo foobar secretfile Does not clobber the permissions (or NTFS ACLs) on Unix (or Windows). But it does clobber them when Samba is involved. It makes no sense to say that the act of editting a text file has any effect on its security permissions. (Whether it be in notepad.exe or on the command line as I have shown.) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 3:40 AM Of course '' is very different of ''. '' creates a new file so THE NEW secretfile is created with the 644 mask. '' appends in the file. A file is chmod 600. It gets opened on Windows, and it gets changed to 644. This happens if the user does: N:\ echo foobar secretfile But it does stay at chmod 600 if he does (append instead of truncate): N:\ echo foobar secretfile The create mask parameter is set to 644. I do not think this -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Re: Logging Detail
I don't believe there is any way to do this short of going into the source code and changing something there. Sorry. I also think this would be a nice feature. -Original Message- From: Mike McMullen [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 6:37 PM Is there a way to get customized logs so that I get an entry of the form: timestamp IP or machine name Samba User filename -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] logging messenger service in windows
Look at the message command parameter in smb.conf. You can write your own program to handle the message, or just send it to the logger command to send it to the system log. -Original Message- From: kent E. [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 6:35 AM is there a way to log any communications using the windows 'net send' -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] permission bits clobbered
The '' creates a new file, but ONLY if the file did NOT exist before. If it does exist, the file's contents are replaced, but it still the same file. This is the way it works on both Windows and Unix. This command: echo foobar secretfile Does not clobber the permissions (or NTFS ACLs) on Unix (or Windows). But it does clobber them when Samba is involved. It makes no sense to say that the act of editting a text file has any effect on its security permissions. (Whether it be in notepad.exe or on the command line as I have shown.) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 3:40 AM Of course '' is very different of ''. '' creates a new file so THE NEW secretfile is created with the 644 mask. '' appends in the file. A file is chmod 600. It gets opened on Windows, and it gets changed to 644. This happens if the user does: N:\ echo foobar secretfile But it does stay at chmod 600 if he does (append instead of truncate): N:\ echo foobar secretfile The create mask parameter is set to 644. I do not think this -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Mapping a drive letter to a Samba share
The backslash is not a valid character for a share name. You might be able to have a share named C$ and set the path = /foo, then create a symlink named /foo/inetpub/mailroot/Pickup which points to /pickup. Doing it that way would mean that \\server\C$\inetpub\mailroot\Pickup is actually the same as \\server\pickup. HTH. -Original Message- From: Brian Spiegel [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 6:12 PM [C$\inetpub\mailroot\Pickup] comment = Other Pickup, Same Target Directory path = /pickup read only = No guest ok = Yes guest only = Yes Now, C$ is standard UNC for the root directory on Windows ( C: ). The Pickup share works great. However, the share with C$ in the title gives me a Network name could not be found error dialog. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] permission bits clobbered
A file is chmod 600. It gets opened on Windows, and it gets changed to 644. Now the secrets are exposed to all users. This is bad! This happens if the user does: N:\ echo foobar secretfile But it does stay at chmod 600 if he does (append instead of truncate): N:\ echo foobar secretfile Why does this happen? The create mask parameter is set to 644. I do not think this should apply to files that already exist, but only to files that are created. Samba version is 2.2.8a. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: mount points / free disk space / dfree command
I went and read some of the CIFS spec[1], and it seems to me that the QUERY_FS_INFO trans2 request only includes an identifier for the current connection. Given this information, samba can only attempt to determine the amount of space on the root of the share. This explains why using the dfree command did not give me any different numbers than not using it. If I really understand what is going on here, then what we would have to do is create a new share for each mounted device. That would be hard because the root that is exported happens to be an automounter directory, which changes. [1] http://ubiqx.org/cifs/rfc-draft/draft-leach-cifs-v1-spec-02.html#s4.1.6 -Original Message- From: Panko, Kevin [mailto:[EMAIL PROTECTED] Sent: Thursday, February 20, 2003 3:27 PM To: '' Subject: mount points / free disk space / dfree command We have a share with mount points beneath it. Free disk space is incorrect because samba always returns the free space in the top level directory of the share. It is the same problem discussed before in this thread: http://groups.google.com/groups?hl=enlr=ie=UTF-8oe=UTF-8th=4c04c4aeb2405 d4dseekm=9q2iee%242s7r%241%40FreeBSD.csie.NCTU.edu.twframe=off I was hoping to use the dfree command smb.conf option, as the df command reports the correct amount of free space for each subdirectory. I found that my dfree command was always given the directory name of the top level of the share, regardless of the current directory on the Win2k client, so the answer I get with dfree is the same as the internal samba routines. Why does that happen? Does the call have knowledge of the current directory of the client, or is that not included in the client's request? If not, then I must admit that this may be impossible. If it does, and if that directory were passed to the df command, then what I need can be done via samba. I do not want to use recursion and add up the amount of free space as the sum of each mount point. I only care about the current directory. We do have a need to determine the amount of free space from Win2k, and creating a samba share for each subdirectory would be impractical. TIA, Kevin Panko
mount points / free disk space / dfree command
We have a share with mount points beneath it. Free disk space is incorrect because samba always returns the free space in the top level directory of the share. It is the same problem discussed before in this thread: http://groups.google.com/groups?hl=enlr=ie=UTF-8oe=UTF-8th=4c04c4aeb2405 d4dseekm=9q2iee%242s7r%241%40FreeBSD.csie.NCTU.edu.twframe=off I was hoping to use the dfree command smb.conf option, as the df command reports the correct amount of free space for each subdirectory. I found that my dfree command was always given the directory name of the top level of the share, regardless of the current directory on the Win2k client, so the answer I get with dfree is the same as the internal samba routines. Why does that happen? Does the QUERY_FS_INFO trans2 call have knowledge of the current directory of the client, or is that not included in the client's request? If not, then I must admit that this may be impossible. If it does, and if that directory were passed to the df command, then what I need can be done via samba. I do not want to use recursion and add up the amount of free space as the sum of each mount point. I only care about the current directory. We do have a need to determine the amount of free space from Win2k, and creating a samba share for each subdirectory would be impractical. TIA, Kevin Panko
