From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: mobileorg encryption in iOS vs. Android Date: Mon, 14 Jan 2013 10:34:08 -0600 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TumzG-00057v-4V for emacs-orgmode@gnu.org; Mon, 14 Jan 2013 11:34:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TumzB-0004Ue-Fl for emacs-orgmode@gnu.org; Mon, 14 Jan 2013 11:34:14 -0500 Received: from mail-ob0-f169.google.com ([209.85.214.169]:60237) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TumzB-0004Ty-Ak for emacs-orgmode@gnu.org; Mon, 14 Jan 2013 11:34:09 -0500 Received: by mail-ob0-f169.google.com with SMTP id v19so4105612obq.14 for ; Mon, 14 Jan 2013 08:34:08 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode See this thread on the Android mobileorg mailing list for reference: - https://groups.google.com/forum/#!topic/mobileorg-android/IELoLsOCvos I was having issues with org-mobile-use-encryption, and think it ended up being that this variable is only for the iOS version. It encrypts with openssl (at least from what I could tell) evidenced by this in org-mobile.el: ---------- (defun org-mobile-encrypt-file (infile outfile) "Encrypt INFILE to OUTFILE, using `org-mobile-encryption-password'." (shell-command (format "openssl enc -aes-256-cbc -salt -pass %s -in %s -out %s" (shell-quote-argument (concat "pass:" (org-mobile-encryption-password))) (shell-quote-argument (expand-file-name infile)) (shell-quote-argument (expand-file-name outfile))))) ---------- The Android version integrates encryption via Android Privacy Guard (http://thialfihar.org/projects/apg/), which decrypts gpg files. Thus, the Android procedure is: 1) Encrypt the desired org files: $ gpg -c file.org 2) Get org-mobile-files to update by either: - Adding file.org.gpg (or whatever you renamed the encrypted file to) to org-agenda-files - Adding the encrypted gpg file to org-mobile-files 3) M-x org-mobile-push 4) I was asked for the password three times; looks like once to decrypt and then twice for a new password to re-encrypt when pushing 5) Make sure Android Privacy Guard is installed on phone 6) Setup sync settings and syncronize 7) A popup via APG should ask for symmetric password Also, add this text at the top of the file so that emacs knows this is an orgmode file even thought it ends in .gpg: -*-mode:org-*- I'm wondering if there's a way to add some sort of variable, say `org-mobile-os` that could take "ios" or "android" as the inputs so that org-mobile-use-encryption worked more as expected for Android users? Just a thought and wanted to inquire about this. At the very least, it looks like the manual should be updated to reflect that the process is not the same for both mobileorg's when it comes to encryption. Thanks for any feedback, John