After fixing missing API Keys, can't cd to chronos home dir
Reported by
russ.s...@intel.com,
Jul 20 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 Platform: 8610.0.2017_20_07 Steps to reproduce the problem: 1. login to the desktop UI 2. ^-alt-t to open a crosh window 3. shell to go to bash 4. cd to go to /home/chronos/user 5. ls 6. observe error message "wrong media type" 7. cd .. to go to /home/chronos 8. ls user 9. observe same error What is the expected behavior? ls to display the files in /home/chronos/user What went wrong? get an error message: ls: cannot open directory .: wrong media type Did this work before? Yes 2 days ago before they fixed the missing api keys Chrome version: 54.2800 Channel: dev OS Version: 54.8610 Flash Version: Shockwave Flash 22.0 r0
,
Jul 25 2016
This problem has been addressed upstream by reverting the patch that caused the problem. commit 78c4e172412de5d0456dc00d2b34050aa0b683b5 Author: Jeff Mahoney <jeffm@suse.com> Date: Tue Jul 5 17:32:29 2016 -0400 Revert "ecryptfs: forbid opening files without mmap handler" This reverts commit 2f36db71009304b3f0b95afacd8eba1f9f046b87. It fixed a local root exploit but also introduced a dependency on the lower file system implementing an mmap operation just to open a file, which is a bit of a heavy hammer. The right fix is to have mmap depend on the existence of the mmap handler instead. Signed-off-by: Jeff Mahoney <jeffm@suse.com> Cc: stable@vger.kernel.org Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
,
Jul 25 2016
Patch uploaded here - https://chromium-review.googlesource.com/#/c/362993/
,
Jul 26 2016
,
Jul 28 2016
This had already been submitted in https://chromium-review.googlesource.com/#/q/I2975a687ab49a386517ba0841d633c8d5b4db74d and is now merged.
,
Feb 20 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by russ.s...@intel.com
, Jul 25 2016