All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blibbet <blibbet@gmail.com>
To: chipsec@lists.01.org
Subject: Re: Native Mac Support for Chipsec?
Date: Mon, 27 Jul 2015 07:41:09 -0700	[thread overview]
Message-ID: <55B64305.1050605@gmail.com> (raw)
In-Reply-To: <CAFzMC=k8fj5HJBbzNARX1mmjzEO1G9=y1M55jA8JH5SijJeA+A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

On 07/27/2015 01:56 AM, Darren Bilby wrote:
> Just wondering if there is any intention to officially support OSX with
> Chipsec.
...
> Is the key factor in support just time/contributions? or are there factors
> to consider before considering this?

Yes, OS X support for CHIPSEC would be nice.

I've asked the CHIPSEC team this question before, I think the only issue
is lack of dev resources on the port. The good news is that once someone
an OSX kernel driver stub, you can copy the same Intel assembly in the
Windows and Linux drivers.

I'd be nice if Apple stepped up and helped with their platforms'
security by contributing the port and this driver. Otherwise, they'll
have to keep relying on Linux to secure their systems. :-) Ditto
Goggle/OHA for Android, and FreeBSD Foundation/iX Systems for FreeBSD...

BTW, at a class last weekend one one student successfully ran LUV-live's
CHIPSEC on a Mac system (macboo) as well.

Thanks,
Lee
RSS: http://firmwaresecurity.com/feed


  reply	other threads:[~2015-07-27 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27  8:56 Native Mac Support for Chipsec? Darren Bilby
2015-07-27 14:41 ` Blibbet [this message]
2015-07-27 17:25   ` Loucaides, John

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=55B64305.1050605@gmail.com \
    --to=blibbet@gmail.com \
    --cc=chipsec@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.