From: Joakim Bech <joakim.bech@linaro.org>
To: op-tee@lists.trustedfirmware.org
Subject: Re: OP-TEE development
Date: Wed, 23 Sep 2020 13:30:33 +0200 [thread overview]
Message-ID: <20200923113033.GA32573@goby> (raw)
In-Reply-To: <<01000174bab514a8-db23310d-8130-4711-aac8-b5e312f3e1a9-000000@email.amazonses.com>>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Hi Nikita,
On Wed, Sep 23, 2020 at 11:24:23AM +0000, Nikita Snetkov via OP-TEE wrote:
> Hello!
>
> Currently, I became interested in TEE research and development. After small
> investigation, I found out your product: OP-TEE. After reading about it,
> there is a thing that still bothers me: is it possible to create an
> application which uses OP-TEE and distribute in via Google Play?
>
For OP-TEE you typically create a pair of binaries, one binary running
on non-secure side (plain Linux environment) and one binary (Trusted
Application) running on the secure side.
Google Play hosts applications running in non-secure world, so I'd
believe that distributing the non-secure side of your feature using
Google Play is something you can do. But for the secure side, it's not
that easy, since it's usually the OEM that decide what to install and is
allowed to run on the secure side on their devices.
> --
> Yours faithfully,
> Nikita Snetkov
--
Regards,
Joakim
next parent reply other threads:[~2020-09-23 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <=?utf-8?q?=3C01000174bab514a8-db23310d-8130-4711-aac8-b5e312f3e?= =?utf-8?q?1a9-000000=40email=2Eamazonses=2Ecom=3E?=>
2020-09-23 11:30 ` Joakim Bech [this message]
2020-09-23 11:00 OP-TEE development Nikita Snetkov
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=20200923113033.GA32573@goby \
--to=joakim.bech@linaro.org \
--cc=op-tee@lists.trustedfirmware.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