From: Cecilio Pardo <cpardo@imayhem.com>
To: Richard Stallman <rms@gnu.org>
Cc: oub@mat.ucm.es, Cecilio Pardo <cpardo@imayhem.com>, emacs-devel@gnu.org
Subject: Re: Will Emacs be ever available for iOS?
Date: Mon, 07 Jan 2019 01:55:21 +0100 [thread overview]
Message-ID: <8636q52sna.fsf@inmotica-integral.es> (raw)
In-Reply-To: <E1ggEHA-00049B-FE@fencepost.gnu.org> (Richard Stallman's message of "Sun, 06 Jan 2019 14:40:00 -0500")
> Someone wrote
>
>> > I think there is a app called popcorn which is for streaming videos and
>> > which is not available in the app shop, but can installed via the webpage
>> > of the developer. So may this is the way Emacs could go.
>
> 1. Is this correct?
Yes, that can be done, but it is in violation of the license with
Apple. They use a "Enterprise developer certificate". This allows an
enterprise to distribute software internally to its employees, not to
the public.
Apple would normally revoke certificates that are used this way, so this
applications also tamper with the certificate validation system to stay
alive, and could stop working at any time. This is very shady, I don't
know much more about it, sorry.
> 2. Can anyone who has an iMonsteer install popcorn in this way?
Yes.
> 3. What else does a person have to do install popcorn in this way?
Not much. Install the app as it would be done for a 'legitimate'
enterprise distribution. And trust the binary.
> 4. Does the user installing it need a developer certificate?
No.
> 5. Is the binary in that web site signed with someone's developer certificate?
Yes. The "enterprise" certificate.
> 6. Does Apple forbid others to redistribute that binary?
Yes. Those certificates are to be used only inside the organization.
--
Cecilio Pardo
next prev parent reply other threads:[~2019-01-07 0:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 21:48 Will Emacs be ever available for iOS? Ahmed Alharbi
2018-12-31 9:22 ` Tim Cross
2018-12-31 13:26 ` Nahuel Jesús Sacchetti
2018-12-31 13:55 ` Kalman Reti
2019-01-01 21:44 ` Richard Stallman
2019-01-02 20:52 ` Nahuel Jesús Sacchetti
2019-01-03 23:21 ` Richard Stallman
2019-01-04 4:05 ` Elias Mårtenson
2019-01-04 21:27 ` Richard Stallman
2019-01-05 4:03 ` Elias Mårtenson
2019-01-05 7:59 ` Toon Claes
2019-01-05 19:32 ` Richard Stallman
2019-01-05 8:56 ` Uwe Brauer
2019-01-05 19:33 ` Richard Stallman
2019-01-05 22:28 ` Cecilio Pardo
2019-01-06 19:40 ` Richard Stallman
2019-01-06 19:46 ` Uwe Brauer
2019-01-06 20:26 ` Uwe Brauer
2019-01-07 0:55 ` Cecilio Pardo [this message]
2019-01-07 3:44 ` Elias Mårtenson
2019-01-07 16:21 ` Cecilio Pardo
2019-01-07 20:14 ` Richard Stallman
2019-01-07 22:44 ` Cecilio Pardo
2019-01-07 20:12 ` Richard Stallman
2019-01-05 19:32 ` Richard Stallman
2018-12-31 22:57 ` Richard Stallman
2019-01-04 17:22 ` Uwe Brauer
2019-01-04 17:17 ` Uwe Brauer
2019-01-04 17:19 ` Uwe Brauer
-- strict thread matches above, loose matches on Subject: below --
2019-01-15 9:05 Van L
2019-01-15 9:24 Van L
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8636q52sna.fsf@inmotica-integral.es \
--to=cpardo@imayhem.com \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).