Google Chrome now requires at least kernel v. 3.17

Discussion in 'all things UNIX' started by tlu, Mar 8, 2015.

  1. tlu

    tlu Guest

    ... according to this thread as they added a new sandboxing flag called TSYNC used by seccomp. And indeed, I'm seeing this flag in chrome://sandbox/ in v. 41.

    Needless to say, that I'm not having any problems on Arch Linux. But what about other distros with older kernels? Is Chrome really no longer supported?

    Please share your experiences.

    EDIT: There is a patch for Ubuntu.
    EDIT2: More info on Phoronix.
     
    Last edited by a moderator: Mar 8, 2015
  2. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    1,984
    Location:
    Canada
    Is this TSYNC some sort of additional sandboxing to enforce Chrome security even more? I'm using 3.14 kernel in Arch so no support in my case.
     
  3. oliverjia

    oliverjia Registered Member

    Joined:
    Jul 21, 2005
    Posts:
    1,517
    Ubuntu 14.04 and up appear to be fine.
     
  4. tlu

    tlu Guest

    There is this explanation by Kees Cook. As far as I understand it improves seccomp by facilitating the synchronization of different seccomp threads.
     
  5. tlu

    tlu Guest

    Yes, that's because of the patch mentioned above in which tsync was backported from kernel 3.17.
     
  6. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    1,984
    Location:
    Canada
    Thanks, tlu!
     
  7. tlu

    tlu Guest

    The whole story was a nuisance alarm (to a large extent, at least).
     
Loading...