From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2155) id 2C09A3858CDB; Mon, 26 Feb 2024 09:20:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2C09A3858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1708939251; bh=QijU8sEsw/swHZVA612Totjta0LhqvRBeUBY6EBS8oE=; h=Date:From:To:Subject:Reply-To:References:In-Reply-To:From; b=YrcXBJZC0g8XrSfOtkDAu5o2QMJfTgLrZJFl0a1O0zamPSobqE/Q1U5UIvv1dh1L0 6zAO0ziZOKIAHwO4vS7e3jisG717CNY/zvUOFK4muvuoRVSDUS1sq9Wz8ogQgbu/pB b2gqmpk12DoXQA5ItcRsDPdPwpqrrzSO4HcTCPlA= Received: by calimero.vinschen.de (Postfix, from userid 500) id BA40BA80851; Mon, 26 Feb 2024 10:20:48 +0100 (CET) Date: Mon, 26 Feb 2024 10:20:48 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Will all SIDs fit into |SECURITY_MAX_SID_SIZE| bytes ? / was: Re: Switching groups with newgrp - how to get the new group with |GetTokenInformation()| ? Message-ID: Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: On Feb 25 22:04, Roland Mainz via Cygwin wrote: > On Sat, Feb 24, 2024 at 7:57 PM Corinna Vinschen via Cygwin > wrote: > > > > On Feb 24 15:38, Roland Mainz via Cygwin wrote: > > > On Thu, Feb 22, 2024 at 8:11 PM Corinna Vinschen via Cygwin > > > wrote: > > > > On Feb 22 18:38, Roland Mainz via Cygwin wrote: > > > > > If I switch the current user's group with /usr/bin/newgrp, how can a > > > > > (native) Win32 process use > > > > > |GetTokenInformation(GetCurrentThreadToken(), ...)| to find out which > > > > > group is the new "current group" (e.g. which |TokenInformationClass| > > > > > should I use) ? > > > > > > > > PSID sidbuf = (PSID) alloca (SECURITY_MAX_SID_SIZE); > > > [snip] > > > > > > Win32/NT API question: All known SIDs will fit into > > > |SECURITY_MAX_SID_SIZE| bytes, right ? I'm asking because right now > > > the ms-nfs41-client code assumes that all SIDs use a variable amount > > > of memory, and we always have to ask the Win32/NT API about the number > > > of bytes to allocate. If |SECURITY_MAX_SID_SIZE| is the global maximum > > > limit for all Windows versions, then we could simplify the code a > > > lot... > > > > Yes. ACLs are size restricted to 64K, though, but that shouldn't be > > much of a problem usally. > > Erm... why ACLs? I was asking about the memory allocation size for an SID. I know, and I wrote "Yes". I mentioned ACLs because ACLs consist of SIDs and if all SIDs take SECURITY_MAX_SID_SIZE bytes... well, no worries. Corinna