linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [tpmdd-devel] [PATCH RESEND 3/3] tpm-chip: Export TPM device to user space even when startup failed
Date: Wed, 30 Aug 2017 13:15:10 +0300	[thread overview]
Message-ID: <20170830101510.rlkh2p3zecfsrhgl@linux.intel.com> (raw)
In-Reply-To: <20170829151739.315ae581@kitsune.suse.cz>

On Tue, Aug 29, 2017 at 03:17:39PM +0200, Michal Such?nek wrote:
> Hello,
> 
> On Tue, 29 Aug 2017 15:55:09 +0300
> Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
> 
> > On Mon, Aug 28, 2017 at 05:15:58PM +0000,
> > Alexander.Steffen at infineon.com wrote:
> > > But is that just because nobody bothered to implement the necessary
> > > logic or for some other reason?  
> > 
> > We do not want user space to access broken hardware. It's a huge risk
> > for system stability and potentially could be used for evil purposes.
> > 
> > This is not going to mainline as it is not suitable for general
> > consumption. You must use a patched kernel if you want this.
> > 
> > /Jarkko
> > 
> 
> It has been pointed out that userspace applications that use direct IO
> access exist for the purpose. So using a kernel driver is an
> improvement over that if the interface is otherwise sane.
> 
> What do you expect is the potential for instability or evil use?

By definition the use of broken hardware can have unpredictable effects.
Use a patched kernel if you want to do it.

/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-08-30 10:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170824083714.10016-1-Alexander.Steffen@infineon.com>
     [not found] ` <20170824083714.10016-4-Alexander.Steffen@infineon.com>
2017-08-25 17:20   ` [PATCH RESEND 3/3] tpm-chip: Export TPM device to user space even when startup failed Jarkko Sakkinen
2017-08-28 17:15     ` Alexander.Steffen at infineon.com
2017-08-29 12:55       ` Jarkko Sakkinen
2017-08-29 13:17         ` [tpmdd-devel] " Michal Suchánek
2017-08-29 13:53           ` Peter Huewe
2017-08-30 10:26             ` Jarkko Sakkinen
2017-08-30 10:15           ` Jarkko Sakkinen [this message]
2017-08-30 10:20             ` Jarkko Sakkinen
2017-08-30 10:34               ` Michal Suchánek
2017-08-30 11:07                 ` Jarkko Sakkinen
2017-08-31 16:18                   ` Alexander.Steffen at infineon.com
2017-09-02 10:20                     ` Jarkko Sakkinen
2017-08-30 10:41             ` Peter Huewe
2017-08-30 11:10               ` Jarkko Sakkinen
2017-08-31 16:26                 ` Alexander.Steffen at infineon.com
2017-09-02 10:24                   ` Jarkko Sakkinen
     [not found] ` <20170824083714.10016-2-Alexander.Steffen@infineon.com>
2017-08-25 17:25   ` [PATCH RESEND 1/3] tpm-chip: Move idr_replace calls to appropriate places Jarkko Sakkinen
2017-08-28 17:18     ` Alexander.Steffen at infineon.com

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=20170830101510.rlkh2p3zecfsrhgl@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).