emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: mobileorg encryption in iOS vs. Android
Date: Mon, 14 Jan 2013 11:42:37 -0600	[thread overview]
Message-ID: <CA+M2ft8+Mjx2m6eVsGC9YpfEcoYCaC4oJKpEuAw8EB-ax2w5pg@mail.gmail.com> (raw)
In-Reply-To: <rmi4nij7m0u.fsf@fnord.ir.bbn.com>

On Mon, Jan 14, 2013 at 10:43 AM, Greg Troxel <gdt@ir.bbn.com> wrote:
>
> It seems that the android version should act like the ios version and
> just use the symmetric cipher.  Is that hard, or is there some advantage
> to the gpg scheme?   Or perhaps the android-style encryption should be
> supported directly in org?
>

I think it has to do with the method used. org-mobile-use-encryption
uses openssl based encryption. From the APG entry on wikipedia [1]:
----------
The application provides strong, user-based encryption which is
compatible with the Pretty Good Privacy (PGP) and GNU Privacy Guard
(GPG) programs.
----------

When I encrypt with org-mobile-use-encryption, I get an APG popup with
a blank entry field expecting a PGP message, and it features a
"Decrypt" button at the bottom. When using gpg manually, I get a popup
for a symmetric key password.

Does this make sense? If so, this is my reasoning for thinking the
change has to be on the org side. Alternatively, an openssl decryption
method could be integrated into mobileorg Android.

[1] http://en.wikipedia.org/wiki/Android_Privacy_Guard


John

  reply	other threads:[~2013-01-14 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 16:34 mobileorg encryption in iOS vs. Android John Hendy
2013-01-14 16:43 ` Greg Troxel
2013-01-14 17:42   ` John Hendy [this message]
2013-01-14 21:10     ` Greg Troxel

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+M2ft8+Mjx2m6eVsGC9YpfEcoYCaC4oJKpEuAw8EB-ax2w5pg@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gdt@ir.bbn.com \
    /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/org-mode.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).