similar to: [2.PATCH]: Eliminate typo in bsd-misc.*

Hi, the SETGROUPS_NOOP define is used only for Cygwin. But it's also combined with the HAVE_SETGROUPS test in bsd-misc.c. So, since setgroups() exists and is functional in Cygwin, this is actually a noop in the more general sense. The below patch drops that entirely. Corinna Index: acconfig.h =================================================================== RCS file:

Hi, I've sent that patch once already but it seems more or less forgotten in the tumultuous days of the latest vulnerability. It adds a new define NO_IPPORT_RESERVED_CONCEPT which can be defined on platforms not supporting the concept of "privileged" ports only accessible by privileged users but which allow everyone to use these ports. This patch removes some Cygwin dependencies

I need this for BSD/OS 4.2 + privsep perhaps we should not call do_setusercontext() after chroot(). --- sshd.c.orig Fri Jun 21 03:09:47 2002 +++ sshd.c Tue Jun 25 13:11:03 2002 @@ -548,21 +548,35 @@ /* Change our root directory*/ if (chroot(_PATH_PRIVSEP_CHROOT_DIR) == -1) fatal("chroot(\"%s\"): %s", _PATH_PRIVSEP_CHROOT_DIR, strerror(errno)); if

I am enclosing a context diff of the changes that I made to get openssh working on UWIN. UWIN is a UNIX operating system layer that runs on Win32 systems. For more information on UWIN go to http://www.research.att.com/sw/tools/uwin/. I also ran configure using -with-cppflags=-D_BSDCOMP=2. I don't know where that information would go with the source code. Let me know if you need more

Fixes a potential (but probably rather unlikely) use after free bug in function temporarily_use_uid(), file uidswap.c. --- a/uidswap.c +++ b/uidswap.c @@ -113,8 +113,9 @@ temporarily_use_uid(struct passwd *pw) } } /* Set the effective uid to the given (unprivileged) uid. */ - if (setgroups(user_groupslen, user_groups) < 0) -

Begin forwarded message: From: Bill Bumgarner <bbum@codefab.com> Date: Wed Feb 19, 2003 9:31:24 AM US/Eastern To: "George D.Plymale" <george@SouthernOhioComputerServices.com> Subject: Re: fink rsync --daemon failure On Wednesday, Feb 19, 2003, at 08:14 US/Eastern, George D.Plymale wrote: > It would seem that OS X does indeed have a problem zeroing > the supplimental

Hello, I have recently upgraded to macOS 10.14 (Mojave) and am running into an issue where one use can no longer log into dovecot via imap. Log shows Oct 11 08:10:27 imap(hwr)<12659><YpC/0+133+EAAAAAAAAAAAAAAAAAAAAB>: Fatal: setgroups(501) failed: Too many extra groups and indeed, the user is in 17 groups, which is more than NGROUPS_MAX (16). Another user with << 16 groups

I've been trying to get my two Mac OS X computers to sync using rsync 2.5.5. I have one set up as the host with --daemon and the other with a client running. I was encountering an @ERROR: chroot failed error in my messages. I found that the problem lied in a misconfiguration of the rsyncd.conf file. I had tried to specify a POSIX pathway using the quoted foward-slash method. Once I got past

I found and tried this work around on the man page: https://www.unix.com/man-page/all/5/ngroups_max/ but I still get the same "Too many extra groups" error even when I start dovecot with the above program to limit the # of groups. I suspect that dovecot is adding a number of groups when it starts up. I've hacked a work around to get it working for me on my laptop: diff --git

Hi! I'm investigating the seccomp filter in openssh and I wanted to know whether the following system calls should be added to the filter: 1. getgroups - do_authentication2->dispatch_run_fatal->sshpkt_fatal->logdie->cleanup_exit->do_cleanup->temporarily_use_uid->getgroups 2. setgroups -

I've added the: /etc/services /etc/inetd entries as well as /etc/rsync.conf with the contents: [io] path = //Volumes/Mac_OS_X/Library/WebServer/iolanguage.com/Io comment = iolanguage source code But I get this error: % rsync -rvR --progress localhost:/ . localhost.dekorte.com: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error:

Dave- I've got the rsync daemon running as root, (setgroups() man page said that if setgroups wasn't called as root it would give an error message) and I've configured the ports correctly a la man page. I still get the error with setgroups. If it's a recently implemented security feature could I yank that section out of the code and recompile it again? I haven't had a chance to

On Thu, Oct 11, 2018 at 09:51:34AM +0300, Aki Tuomi wrote: > > Looking at the source, I see this is handled in > > src/lib/restrict-access.c::fix_groups_list(), > > where above the call to setgroups() a gid_list2 is constructed. I > > wonder if one could > > have a config option to prevent adding all those extra groups, which > > then make the > > call to

I am trying to debug some core dump problems. I should be able to run imap by itself right? How to fix? # ./imap imap(root): Fatal: setgroups() failed: Too many extra groups I am using latest nightly code.

Greetings, Has anyone successfully compiled rsync 2.5.5 under Mac OS X (not Server), and actually have it work fully? I'm in a position where I'm trying to setup an automated nightly remote backup between and Cobalt Raq4 (running a variant of Redhat Linux) and a Mac running OS X 10.1.5 with the latest development tools installed. As has been pointed out previously on the list, one has

Hello. We have a few OS X machines running Jaguar 10.2 that's set to rsync over important files for backup purposes. The rsync was happening without any problems until the last Jaguar security update was installed a few weeks ago or so. Now they are giving the below errors and the rsync does not happen: @ERROR: setgroups failed rsync: connection unexpectedly closed (78 bytes read so far)

In running the various 1.0.n versions of Dovecot's LDA with the instructions in the wiki for using LDA with Postfix [on OS X 10.4] things went well using the instructions as-is (no setuid problems). This changed in moving over to the 1.1 beta. The LDA refused to work failing with the error "setgroups() failed: Operation not permitted" as I mentioned in a previous message.

I am trying to set up a MacOS X rsync server and am not having much success at the moment. I'm able to see the "share" alright, but here is what I get when I actually try to copy anything to the server: #rsync -vz /Users/myhome localhost::backup @ERROR: setgroups failed rsync: connection unexpectedly closed (37 bytes read so far) rsync error: error in rsync protocol data stream

Okay .. have dovecot set up with following settings : userdb static { args = uid=97 gid=97 home=/export/dovecot/mail/%d/%u mail=mbox:/export/dovecot/mbox/%d/%u/ } passdb passwd-file { # Path for passwd-file args = /etc/dovecot-passdb } Passdb works I think in the sense that I can log into dovecot using a regular mail client. The real issue is when I try to deliver

Hi! We had stand-alone anonymous samba server serving a read-only share as guest account. It worked well but had a few strange issues (like lots of noise in logs about bad smb2 signature). Its been suggested to switch to a domain member server. I didn't see the point since we don't need different user IDs and security model, but okay, - I joined a new server to a domain. Now I see