public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "[ext] Adler, Michael" <michael.adler@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"claudius.heine.ext@siemens.com" <claudius.heine.ext@siemens.com>,
	"Claudius Heine" <ch@denx.de>
Subject: Re: [PATCH] added 'isar-cfg-userpw' package
Date: Wed, 27 Feb 2019 11:20:32 +0100	[thread overview]
Message-ID: <20190227112032.16869f81@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190227094605.10a419b2@md1za8fc.ad001.siemens.net>

On Wed, 27 Feb 2019 09:46:05 +0100
"[ext] Henning Schild" <henning.schild@siemens.com> wrote:

> On Tue, 26 Feb 2019 20:47:25 +0100
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
> > On 26.02.19 20:36, [ext] Jan Kiszka wrote:  
> > > On 25.02.19 11:34, [ext] Henning Schild wrote:    
> > >> Hi,
> > >>
> > >> this is not related to the package. But to any package that goes
> > >> through common.sh and checks the ids.
> > >>
> > >> https://groups.google.com/forum/#!searchin/isar-users/Align$20UID$20and$20GID$20%7Csort:date/isar-users/S5W8D3X4Lkg/n7HbASWnAwAJ 
> > >>
> > >>
> > >> The result of this discussion was that we probably need to align
> > >> the ids and hope we never get in trouble with the host. In this
> > >> case we do!
> > >>
> > >> The alignment should be changed. If the group does exist (100)
> > >> join the user and do not try and create a group. The check should
> > >> be changed to make sure the gid is the main group gid, instead of
> > >> 1000.    
> > > 
> > > FWIW, just ran into the same issue after purging my build folder
> > > and retrying a clean "kas-docker --isar build". I'm not seeing it
> > > with jailhouse-images where we do not use kas-docker yet and also
> > > do not create the build folder outside of the container, thus with
> > > host IDs.
> > > 
> > > So, this needs to be fixed in our kas-isar container, I
> > > suppose...    
> > 
> > No, the bug is really in common.sh, the container is fine:
> > 
> > That script checks for group names, which is probably pointless. In
> > this case, we are in the right group, that group just has an alias
> > called "builder", but was originally called "users".
> > 
> > Why the heck should we check the group?  
> 
> Because that is the most conservative we can get to check the complete
> file ownership. I guess we should keep checking the group but just
> make sure the the current gid is the gid of the user.
> 
> - [ "$(id -gn)" != "builder" ]
> + [ "$(id -g)" != "$(id -g builder)"
> 
> ... same for root.

Patch is on the way ...

Henning

> Henning
> 
> > Jan
> >   
> 


      reply	other threads:[~2019-02-27 10:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 16:21 claudius.heine.ext
2019-02-18 16:58 ` Henning Schild
2019-02-19  9:19   ` Henning Schild
2019-02-23 10:42 ` Jan Kiszka
2019-02-25  8:07   ` Jan Kiszka
2019-02-25  8:44     ` Claudius Heine
2019-02-25  8:48       ` Jan Kiszka
2019-02-25  9:32         ` Henning Schild
2019-02-25 11:15           ` Jan Kiszka
2019-02-25 11:44             ` Claudius Heine
2019-03-04 10:15               ` Claudius Heine
2019-02-25 11:18         ` Claudius Heine
2019-02-25 10:18 ` Adler, Michael
2019-02-25 10:34   ` Henning Schild
2019-02-25 11:38     ` Henning Schild
2019-02-26 19:36     ` Jan Kiszka
2019-02-26 19:47       ` Jan Kiszka
2019-02-27  8:46         ` Henning Schild
2019-02-27 10:20           ` Henning Schild [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190227112032.16869f81@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=michael.adler@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox