similar to: chmod sftp command and setgid/setuid bit

https://bugzilla.mindrot.org/show_bug.cgi?id=1310 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djm at mindrot.org Blocks| |1452 --- Comment #3 from Damien Miller

version: rsync v2.6.1 (+ a minor, unrelated patch). I'm rsyncing files (not as root) and am happy (indeed, for what I want, delighted) that the files at the target side end up owned by the account doing the rsync. However, I've found that if I have a setuid/setgid file on the source side, the target file ends up setuid/setgid too (but under a different id!). This happens whether

I think this is more a philosophical issue. Some people want all applications to be like windows. "Are you sure you want to delete this file" <YES> "really"<yes>"it might make something stop working<yes>"permission denied". Unix assumes you know what you're doing. If you don't, tough. There's no reason you can't make a

On Fri, 19 Jul 2002, Dan Stromberg wrote: > Many apologies. If we update on the nfs server, as we've intended all > along, we should have no .nfs* files. Well, here's one thing that could make them, even if they're being created only directly, not over NFS. I'm watching the directory you're syncing into. I open the file while it's still there. You delete it, and

https://bugzilla.samba.org/show_bug.cgi?id=4138 Summary: Incoming chmod can't override inherited directory setgid Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

> > > never seen a file created with a newline in the filename > > (except, perhaps as a test). The newline in filename issue > > And in security exploits :-) Given a newline-based format, one *must* > quote or deny newlines in filenames, not assume they're rare. (No > obvious reason not to use URL-style %-quoting, or mime-style > =-quoting, if you want to

> > This brings up an issue that I believe can be solved in a simpler way than > > with brute force C code. I suspect some of you will cringe when you hear > > this, but a taintperl log parsing program would be best for this. rsync > > could generate a verbose log file that is not human readable, designed to > > be read by a perl postprocessing script. I think this

https://bugzilla.mindrot.org/show_bug.cgi?id=1893 Summary: change ssh-keisign to setgid from setuid Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: unassigned-bugs at mindrot.org

Hello! Please, help! I have trouble with Dovecot's Deliver utility. I don't know how to avoid errors. Let me know what additional related information do you need? 1) Its call in Exim's configure: ========================================== local_delivery_spam_transport: driver = pipe command = /usr/local/libexec/dovecot/deliver -c

I vote for the consistent, complete log format as a solution to this sort of thing, and those who need to take non-rsync related actions based on what rsync did can write their own applications to do so. People keep coming up with some particular thing they need done for their own application, and want rsync to do that too. rsync is a tool to make one thing exactly like another. It is not

Package: logcheck-database Version: 1.2.33 Severity: normal I just installed 1.2.33, and it made my rules dirs setuid, not setgid... - Marc -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of

I'm seeing behavior that I was hoping somebody could explain. I have a share set up that will be a repository for company-wide data. There are three classes of people who can access it, readers, read/writers, and admins. Readers and read/writers are self explanatory, admins have read/write access, and can change the permissions/ownership of files. Read and write access is controlled by

I use rsync -ii so that it logs *all* actions. Further, I don't use any delete option but use --force. This means that if there's a name collision rsync deletes files or directories. Here's an example: 0 0 *deleting rwxrwsr-x 1969/12/31-21:00:00 scm/linux/kernel/git/amit/vs-kernel.git/objects/38 0 0 *deleting rwxrwsr-x 1969/12/31-21:00:00

It like we may have a bug in tar that ships with Centos. It looks like -o is mapped to --same-owner. Some basic info.... uname -a Linux jazzy 2.6.9-34.0.1.ELsmp #1 SMP Wed May 24 08:14:29 CDT 2006 i686 i686 i386 GNU/Linux cat /etc/redhat-release CentOS release 4.3 (Final) % /bin/tar --version tar (GNU tar) 1.14 --same-owner try extracting files with the same ownership --no-same-owner

https://bugzilla.samba.org/show_bug.cgi?id=11521 Bug ID: 11521 Summary: rsync does not use high-resolution timestamps to determine file differences Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Damien, Thanks for the response. Are you aware of any sftp server products that currently implement the uid / gid resolution or is this new draft just too unrefined / recent. Also, is there a definitive source for these drafts and where might they be published? Up till now I have just been reading the documentation available from www.openssh.org. I hope these questions aren't too

Setup: samba 2.2.2 Solaris 8 Trying to print to a printer attached to an NT4/sp6a machine. Printer passes 'test print page' test on NT and is shared. Problem: An error occurs when the smbclient command is used: cat afile | smbclient \\\\tech223\\testprn -U username%password -P -c "translate;print -" The error reported is "ERRDOS - ERRbadaccess (Invalid open mode.)

https://bugzilla.samba.org/show_bug.cgi?id=9377 Summary: acls ignored when using neither --perms nor --chmod Product: rsync Version: 3.0.9 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chrysn at fsfe.org

Hi, I searched whole 2007-2008 mailing lists for answer but couldn\'t find. I think it\'s easier and quicker to ask here. Suppose I have a message saved in file /tmp/afile. How can I tell deliver to deliver it to user\'s abc at domain.com mail box SPAM? I tried two following ways but no success: 1. more /tmp/afile | deliver -d abc at domain.com -m SPAM 2. deliver -d abc at

Esteemed R users and developers, How does one 'programatically' list or call objects for use in a function? For example, i thought i could do something better than this: save(A.cwb, B.cwb, C.cwb, D.cwb, E.cwb, F.cwb, file="afile.RData") with something like these- prfxs <- c("A", "B", "C", "D", "E", "F") #**