mosys => libminijail not locking any securebits |
|||
Issue descriptionChrome OS Version: R71-11151.13.0 Chrome OS Platform: grunt Steps To Reproduce: (1) tail -F /var/log/messages & (2) mosys platform sku Expected Result: 1 Actual Result: 2018-10-26T18:33:21.894515-06:00 WARNING mosys[13058]: libminijail[13058]: not locking any securebits 2018-10-26T18:33:21.894555-06:00 WARNING mosys[13058]: libminijail[13058]: SECURE_NOROOT not set, not dropping bounding set 1 How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always
,
Oct 30
,
Nov 6
verified this is occurring on R72 and on both a caroline and nautilus, so it is larger issue than Grunt and R71.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by vapier@chromium.org
, Oct 30Components: -OS>Systems>Security OS>Systems>Minijail
Summary: mosys => libminijail not locking any securebits (was: grunt: mosys => libminijail not locking any securebits)
Mattias: is this warning useful ? seems like we could delete these warnings. unsigned long securebits = (SECURE_BITS_NO_AMBIENT | SECURE_LOCKS_NO_AMBIENT) & ~skip_mask; if (!securebits) { warn("not locking any securebits"); return 0; }