mobileorg and encryption

[mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/]

Cross-posted to the orgmode mailing list:

-----

I have the following in emacs config:

(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")

I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
(https://github.com/matburt/mobileorg-android/wiki):
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----

But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?


Thanks,
John

[mobileorg-android on behalf of Matthew Jones]

The apg mechanism predates org-mobile-*encryption and just provides a
facility for decrypting encrypted org files.... it might not even still
work in the current iteration of the application because no one has ever
really used it and thus it hasn't really been maintained.


On Fri, Jan 11, 2013 at 3:25 PM, <

Post by mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/]

So there's no encryption support in mobileorg for Android at the moment?

Should the blurb about integration with APG on the front github page be removed?

Thanks for the response,
John

The apg mechanism predates org-mobile-*encryption and just provides a facility for decrypting encrypted org files.... it might not even still work in the current iteration of the application because no one has ever really used it and thus it hasn't really been maintained.
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To view this discussion on the web visit https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J.
For more options, visit this group at http://groups.google.com/group/mobileorg-android?hl=en.

[mobileorg-android on behalf of Matthew Jones]

Possibly? I believe we might still have some of it wired in but I haven't
gone to test it in a while... which is why I'm not sure if it still works
or not. We can/should verify it before making any changes. If we're
interested in implementing org-mobile-*encryption then we should rip out
what's there in its entirety. So encryption is a todo item and the apg
stuff kind of serves as a reminder to remove it when we do get around to
fixing it up.


On Fri, Jan 11, 2013 at 4:30 PM, <

Post by mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/
So there's no encryption support in mobileorg for Android at the moment?
Should the blurb about integration with APG on the front github page be removed?
Thanks for the response,
John

Post by mobileorg-android on behalf of Matthew Jones
The apg mechanism predates org-mobile-*encryption and just provides a

facility for decrypting encrypted org files.... it might not even still
work in the current iteration of the application because no one has ever
really used it and thus it hasn't really been maintained.

Post by mobileorg-android on behalf of Matthew Jones
On Fri, Jan 11, 2013 at 3:25 PM, <
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google

Groups "mobileorg-android" group.

Post by mobileorg-android on behalf of Matthew Jones
To view this discussion on the web visit

https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J.

Post by mobileorg-android on behalf of Matthew Jones
To unsubscribe from this group, send email to
For more options, visit this group at

http://groups.google.com/group/mobileorg-android?hl=en.
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/GFKUhCnGnVQJ.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[John Hendy via mobileorg-android]

If it's in there, I haven't seen any options or been asked for a password.
I was going to try an attempt to futz with a file and rename to .gpg per
the documentation on github, but I'm not sure it would work as I'd have to
edit index.org manually -- would that goof with the checksum file?

I'm happy to check on things and report back; just let me know what you
need to know. I investigated this since these are work notes and I don't
want them in the clear on Dropbox. I could setup webdav, but I don't have a
server, just my laptop which wouldn't always be on to sync with. Perhaps
not a big deal.

Anyway, let me know how I can help. Happy to do so.


John

Post by mobileorg-android on behalf of Matthew Jones
Possibly? I believe we might still have some of it wired in but I haven't
gone to test it in a while... which is why I'm not sure if it still works
or not. We can/should verify it before making any changes. If we're
interested in implementing org-mobile-*encryption then we should rip out
what's there in its entirety. So encryption is a todo item and the apg
stuff kind of serves as a reminder to remove it when we do get around to
fixing it up.
On Fri, Jan 11, 2013 at 4:30 PM, <

Post by mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/
So there's no encryption support in mobileorg for Android at the moment?
Should the blurb about integration with APG on the front github page be removed?
Thanks for the response,
John

Post by mobileorg-android on behalf of Matthew Jones
The apg mechanism predates org-mobile-*encryption and just provides a

facility for decrypting encrypted org files.... it might not even still
work in the current iteration of the application because no one has ever
really used it and thus it hasn't really been maintained.

Post by mobileorg-android on behalf of Matthew Jones
On Fri, Jan 11, 2013 at 3:25 PM, <
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google

Groups "mobileorg-android" group.

Post by mobileorg-android on behalf of Matthew Jones
To view this discussion on the web visit

https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J.

Post by mobileorg-android on behalf of Matthew Jones
To unsubscribe from this group, send email to
For more options, visit this group at

http://groups.google.com/group/mobileorg-android?hl=en.
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/GFKUhCnGnVQJ.
.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[Matthew Jones via mobileorg-android]

Yep, all you'll need to do is rename the file and then rename it in the
index.org and checksums.dat (you should be able to do that manually). Give
it a whirl... let me know what you find out.

Post by John Hendy via mobileorg-android
If it's in there, I haven't seen any options or been asked for a password.
I was going to try an attempt to futz with a file and rename to .gpg per
the documentation on github, but I'm not sure it would work as I'd have to
edit index.org manually -- would that goof with the checksum file?
I'm happy to check on things and report back; just let me know what you
need to know. I investigated this since these are work notes and I don't
want them in the clear on Dropbox. I could setup webdav, but I don't have a
server, just my laptop which wouldn't always be on to sync with. Perhaps
not a big deal.
Anyway, let me know how I can help. Happy to do so.
John

Post by mobileorg-android on behalf of Matthew Jones
Possibly? I believe we might still have some of it wired in but I
haven't gone to test it in a while... which is why I'm not sure if it still
works or not. We can/should verify it before making any changes. If we're
interested in implementing org-mobile-*encryption then we should rip out
what's there in its entirety. So encryption is a todo item and the apg
stuff kind of serves as a reminder to remove it when we do get around to
fixing it up.
On Fri, Jan 11, 2013 at 4:30 PM, <

Post by mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/
So there's no encryption support in mobileorg for Android at the moment?
Should the blurb about integration with APG on the front github page be removed?
Thanks for the response,
John

Post by mobileorg-android on behalf of Matthew Jones
The apg mechanism predates org-mobile-*encryption and just provides a

facility for decrypting encrypted org files.... it might not even still
work in the current iteration of the application because no one has ever
really used it and thus it hasn't really been maintained.

Post by mobileorg-android on behalf of Matthew Jones
On Fri, Jan 11, 2013 at 3:25 PM, <
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google

Groups "mobileorg-android" group.

Post by mobileorg-android on behalf of Matthew Jones
To view this discussion on the web visit

https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J.

Post by mobileorg-android on behalf of Matthew Jones
To unsubscribe from this group, send email to
For more options, visit this group at

http://groups.google.com/group/mobileorg-android?hl=en.
--
You received this message because you are subscribed to the Google
Groups "mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/GFKUhCnGnVQJ.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[John Hendy via mobileorg-android]

Alright. Steps:

1) Set the following in .emacs:

,-----
| (setq org-mobile-use-encryption t)
| (setq org-mobile-encryption-password "password")
`-----

2) run org-mobile-push

3) go to org-mobile-directory location:
-- rename file.org to file.gpg
-- change index.org entry to [[file:file.gpg][file.gpg]]
-- change checksum.dat entry to `hash file.gpg`

4) clear db in mobileorg

5) re-run sync wizard

6) sync

The above is currently not working. My first run, however, I didn't follow
the above exactly. The problem is I don't recall exactly what I did... I
think I forgot to change the index.org file and simply renamed the file to
file.gpg and then changed it in checksums.dat. With that, I got a pop up
like the attached image, but it wasn't clear how to use that screen. I
entered my password and tapped "Decrypt" and got a java io exception.

I wanted to use Dropbox, but without encryption just can't as my files
contain intellectual-property-sensitive work information. I've now got
webdav running with authentication (though I added to the github issue
concerning AuthMode Digest not working, which would be preferred). As such,
I don't really need encryption, but would still like to help troubleshoot
if it could be included. I'm sure others would benefit.


Is that any help?
John

Post by Matthew Jones via mobileorg-android
Yep, all you'll need to do is rename the file and then rename it in the
index.org and checksums.dat (you should be able to do that manually).
Give it a whirl... let me know what you find out.

Post by John Hendy via mobileorg-android
If it's in there, I haven't seen any options or been asked for a
password. I was going to try an attempt to futz with a file and rename to
.gpg per the documentation on github, but I'm not sure it would work as I'd
have to edit index.org manually -- would that goof with the checksum
file?
I'm happy to check on things and report back; just let me know what you
need to know. I investigated this since these are work notes and I don't
want them in the clear on Dropbox. I could setup webdav, but I don't have a
server, just my laptop which wouldn't always be on to sync with. Perhaps
not a big deal.
Anyway, let me know how I can help. Happy to do so.
John

Post by mobileorg-android on behalf of Matthew Jones
Possibly? I believe we might still have some of it wired in but I
haven't gone to test it in a while... which is why I'm not sure if it still
works or not. We can/should verify it before making any changes. If we're
interested in implementing org-mobile-*encryption then we should rip out
what's there in its entirety. So encryption is a todo item and the apg
stuff kind of serves as a reminder to remove it when we do get around to
fixing it up.
On Fri, Jan 11, 2013 at 4:30 PM, <

Post by mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/
So there's no encryption support in mobileorg for Android at the moment?
Should the blurb about integration with APG on the front github page be removed?
Thanks for the response,
John

Post by mobileorg-android on behalf of Matthew Jones
The apg mechanism predates org-mobile-*encryption and just provides a

facility for decrypting encrypted org files.... it might not even still
work in the current iteration of the application because no one has ever
really used it and thus it hasn't really been maintained.

Post by mobileorg-android on behalf of Matthew Jones
On Fri, Jan 11, 2013 at 3:25 PM, <
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end in
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google

Groups "mobileorg-android" group.

Post by mobileorg-android on behalf of Matthew Jones
To view this discussion on the web visit

https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J.

Post by mobileorg-android on behalf of Matthew Jones
To unsubscribe from this group, send email to
For more options, visit this group at

http://groups.google.com/group/mobileorg-android?hl=en.
--
You received this message because you are subscribed to the Google
Groups "mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/GFKUhCnGnVQJ.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[mobileorg-android on behalf of Matthew Jones]

Does org mobile encrypt use gpg? The original use case was to encrypt them
directly with gpg (using some other mechanism) and then have apg pick them
up and decrypt them during syncing.


On Sat, Jan 12, 2013 at 2:52 PM, John Hendy via mobileorg-android <

Post by John Hendy via mobileorg-android
,-----
| (setq org-mobile-use-encryption t)
| (setq org-mobile-encryption-password "password")
`-----
2) run org-mobile-push
-- rename file.org to file.gpg
-- change index.org entry to [[file:file.gpg][file.gpg]]
-- change checksum.dat entry to `hash file.gpg`
4) clear db in mobileorg
5) re-run sync wizard
6) sync
The above is currently not working. My first run, however, I didn't follow
the above exactly. The problem is I don't recall exactly what I did... I
think I forgot to change the index.org file and simply renamed the file
to file.gpg and then changed it in checksums.dat. With that, I got a pop up
like the attached image, but it wasn't clear how to use that screen. I
entered my password and tapped "Decrypt" and got a java io exception.
I wanted to use Dropbox, but without encryption just can't as my files
contain intellectual-property-sensitive work information. I've now got
webdav running with authentication (though I added to the github issue
concerning AuthMode Digest not working, which would be preferred). As such,
I don't really need encryption, but would still like to help troubleshoot
if it could be included. I'm sure others would benefit.
Is that any help?
John

Post by Matthew Jones via mobileorg-android
Yep, all you'll need to do is rename the file and then rename it in the
index.org and checksums.dat (you should be able to do that manually).
Give it a whirl... let me know what you find out.

Post by John Hendy via mobileorg-android
If it's in there, I haven't seen any options or been asked for a
password. I was going to try an attempt to futz with a file and rename to
.gpg per the documentation on github, but I'm not sure it would work as I'd
have to edit index.org manually -- would that goof with the checksum
file?
I'm happy to check on things and report back; just let me know what you
need to know. I investigated this since these are work notes and I don't
want them in the clear on Dropbox. I could setup webdav, but I don't have a
server, just my laptop which wouldn't always be on to sync with. Perhaps
not a big deal.
Anyway, let me know how I can help. Happy to do so.
John

Post by mobileorg-android on behalf of Matthew Jones
Possibly? I believe we might still have some of it wired in but I
haven't gone to test it in a while... which is why I'm not sure if it still
works or not. We can/should verify it before making any changes. If we're
interested in implementing org-mobile-*encryption then we should rip out
what's there in its entirety. So encryption is a todo item and the apg
stuff kind of serves as a reminder to remove it when we do get around to
fixing it up.
On Fri, Jan 11, 2013 at 4:30 PM, <mobileorg-android+noreply-**

Post by mobileorg-android+noreply-APn2wQfmAlB3gQ9DvSRLhuwi8SjfvwLdmSQBVu-/
So there's no encryption support in mobileorg for Android at the moment?
Should the blurb about integration with APG on the front github page be removed?
Thanks for the response,
John

Post by mobileorg-android on behalf of Matthew Jones
The apg mechanism predates org-mobile-*encryption and just provides

a facility for decrypting encrypted org files.... it might not even still
work in the current iteration of the application because no one has ever
really used it and thus it hasn't really been maintained.

Post by mobileorg-android on behalf of Matthew Jones
On Fri, Jan 11, 2013 at 3:25 PM, <mobileorg-android+noreply-**
-----
(setq org-mobile-use-encryption t)
(setq org-mobile-encryption-password "password")
I installed android privacy guard on the phone, and can verify that
staged files are encrypted... but I don't see how to decrypt in the
app. The documentation states
(https://github.com/matburt/**mobileorg-android/wiki<https://github.com/matburt/mobileorg-android/wiki>
-----
Decrypting encrypted org files via integration with Android Privacy
Guard. Encrypted files must end in one of three file extensions: gpg,
enc, or pgp.
-----
But doesn't this imply that org-mode needs to change the file
extensions from .org to .gpg when staging the files? Mine still end

in

Post by mobileorg-android on behalf of Matthew Jones
.org, but are indeed encrypted. Or do I need to change my actual org
files in my main computer repository to be .gpg's as well and this
will result in staged files having .gpg extensions?
Thanks,
John
--
You received this message because you are subscribed to the Google

Groups "mobileorg-android" group.

Post by mobileorg-android on behalf of Matthew Jones
To view this discussion on the web visit

https://groups.google.com/d/**msg/mobileorg-android/-/**nD7gCkt2NG8J<https://groups.google.com/d/msg/mobileorg-android/-/nD7gCkt2NG8J>
.
googlegroups.com.

Post by mobileorg-android on behalf of Matthew Jones
For more options, visit this group at http://groups.google.com/**

group/mobileorg-android?hl=en<http://groups.google.com/group/mobileorg-android?hl=en>
.
--
You received this message because you are subscribed to the Google
Groups "mobileorg-android" group.
To view this discussion on the web visit https://groups.google.com/d/*
*msg/mobileorg-android/-/**GFKUhCnGnVQJ<https://groups.google.com/d/msg/mobileorg-android/-/GFKUhCnGnVQJ>
.
googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/mobileorg-android?hl=en<http://groups.google.com/group/mobileorg-android?hl=en>
.

--

You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/eT49MQRZk6gJ.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[John Hendy via mobileorg-android]

So you propose the following:

1) org-mobile-push normally

2) cd org-mobile-directory

3) run gpg -c file.org

4) edit index.org and checksums.org to contain references to file.org.gpg
(the default output file when running gpg as above)

Is that accurate?


John

[mobileorg-android on behalf of Matthew Jones]

Yep


On Sat, Jan 12, 2013 at 3:38 PM, John Hendy via mobileorg-android <

Post by John Hendy via mobileorg-android
1) org-mobile-push normally
2) cd org-mobile-directory
3) run gpg -c file.org
4) edit index.org and checksums.org to contain references to file.org.gpg
(the default output file when running gpg as above)
Is that accurate?
John
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/SObGba7rTv0J.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[John Hendy via mobileorg-android]

Looks like not. Dug into org-mobile.el and found this section:

----------
(when org-mobile-use-encryption
(unless (string-match "\\S-" (org-mobile-encryption-password))
(error
"To use encryption, you must set `org-mobile-encryption-password'"))
(unless (file-writable-p org-mobile-encryption-tempfile)
(error "Cannot write to encryption tempfile %s"
org-mobile-encryption-tempfile))
(unless (executable-find "openssl")
(error "OpenSSL is needed to encrypt files"))))
----------

So, looks like it's checking for the openssl command, not gpg.

Ah, after more digging, this is verified:
----------
(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)))))
----------

So, it's using openssl.

Just rereading this
thread: https://github.com/matburt/mobileorg-android/issues/155

I'll re-try with just using file.gpg after manually encrypting with gpg,
integrating with orgmode via epa-file. That might work better, and there
shouldn't be any index/checksums file editing required since those will be
the default names. I think that's what you were suggesting, but I
mis-understood.


John

Post by John Hendy via mobileorg-android
1) org-mobile-push normally
2) cd org-mobile-directory
3) run gpg -c file.org
4) edit index.org and checksums.org to contain references to file.org.gpg
(the default output file when running gpg as above)
Is that accurate?
John

[John Hendy via mobileorg-android]

Alright, turns out this works after all. For others, the procedure found at
this github issue is correct:
- https://github.com/matburt/mobileorg-android/issues/155

I was incorrectly using `(setq org-mobile-use-encryption t)` from the
Orgmode documentation, which looks geared toward the iOS version. The
proper way, as alluded to above 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-*-

There's some other documentation about encryption, including using keys at
the Org documentation:
- http://orgmode.org/worg/org-tutorials/encrypting-files.html

So, in the end, this works just fine. Sorry for the noise, but hopefully
it's also proliferating the information for others looking for help! I'll
look into updating the org-mode documentation as well as seeing if someone
who knows elisp/has interest in this might add a new variable such as
`org-mobile-os` to take either `ios` or `android` as inputs. That could
perhaps feed the method used by `org-mobile-use-encryption`. It looks like
it's only setup for iOS, as I don't think the Android version allows for
openssl.

If org-mobile-os was Android, it could use gpg instead? Then again, not
much hassle to just manually encrypt one's self since org-mode is already
so nicely integrated. I would like to figure out how to disable the
multiple password prompts that arise when opening/saving/pushing the
encrypted file.


Hope that helps summarize things a bit and thanks for enduring!
John

[Matthew Jones via mobileorg-android]

Thanks for verifying that this still works... I'm sure it would be great to
support org-mobile-use-encryption also, but as I said earlier... when we
originally implemented encryption support this feature didn't exist in
org-mode.

Post by John Hendy via mobileorg-android
Alright, turns out this works after all. For others, the procedure found
- https://github.com/matburt/mobileorg-android/issues/155
I was incorrectly using `(setq org-mobile-use-encryption t)` from the
Orgmode documentation, which looks geared toward the iOS version. The
$ gpg -c file.org
- 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
-*-mode:org-*-
There's some other documentation about encryption, including using keys at
- http://orgmode.org/worg/org-tutorials/encrypting-files.html
So, in the end, this works just fine. Sorry for the noise, but hopefully
it's also proliferating the information for others looking for help! I'll
look into updating the org-mode documentation as well as seeing if someone
who knows elisp/has interest in this might add a new variable such as
`org-mobile-os` to take either `ios` or `android` as inputs. That could
perhaps feed the method used by `org-mobile-use-encryption`. It looks like
it's only setup for iOS, as I don't think the Android version allows for
openssl.
If org-mobile-os was Android, it could use gpg instead? Then again, not
much hassle to just manually encrypt one's self since org-mode is already
so nicely integrated. I would like to figure out how to disable the
multiple password prompts that arise when opening/saving/pushing the
encrypted file.
Hope that helps summarize things a bit and thanks for enduring!
John

[mobileorg-android+noreply-APn2wQeSh1c0gsIPLEUPpPd3-AT5ghPJ02zRu6-/]

Post by John Hendy via mobileorg-android
7) A popup via APG should ask for symmetric password

APG starts with an empty panel "Message" and a decrypt button.
And a java ioerror that passes quickly.

Pressing Decrypt casts a java error about invalid object in stream 47.

MobileOrg Version 0.9.8
APG v1.0.8

[mobileorg-android on behalf of Tracy Helms]

On Wed, 17 Jul 2013 13:12:52 -0700 (PDT)

Post by mobileorg-android+noreply-APn2wQeSh1c0gsIPLEUPpPd3-AT5ghPJ02zRu6-/

Post by John Hendy via mobileorg-android
7) A popup via APG should ask for symmetric password

APG starts with an empty panel "Message" and a decrypt button.
And a java ioerror that passes quickly.
Pressing Decrypt casts a java error about invalid object in stream 47.
MobileOrg Version 0.9.8
APG v1.0.8

same here

the push gets the encrypted file to Dropbox but APG throws errors.

I can use APG to decrypt the file from Dropbox.

[Matthew Jones via mobileorg-android]

It seems like it's possible that something has broken between us and APG...
can you file a bug report on our issue tracker?

Post by mobileorg-android on behalf of Tracy Helms
On Wed, 17 Jul 2013 13:12:52 -0700 (PDT)

Post by mobileorg-android+noreply-APn2wQeSh1c0gsIPLEUPpPd3-AT5ghPJ02zRu6-/

Post by John Hendy via mobileorg-android
7) A popup via APG should ask for symmetric password

APG starts with an empty panel "Message" and a decrypt button.
And a java ioerror that passes quickly.
Pressing Decrypt casts a java error about invalid object in stream 47.
MobileOrg Version 0.9.8
APG v1.0.8

same here
the push gets the encrypted file to Dropbox but APG throws errors.
I can use APG to decrypt the file from Dropbox.

[Per Sjoholm via mobileorg-android]

issue
https://github.com/matburt/mobileorg-android/issues/403

Post by Matthew Jones via mobileorg-android
It seems like it's possible that something has broken between us and
APG... can you file a bug report on our issue tracker?

Post by mobileorg-android on behalf of Tracy Helms
On Wed, 17 Jul 2013 13:12:52 -0700 (PDT)

Post by mobileorg-android+noreply-APn2wQeSh1c0gsIPLEUPpPd3-AT5ghPJ02zRu6-/

Post by John Hendy via mobileorg-android
7) A popup via APG should ask for symmetric password

APG starts with an empty panel "Message" and a decrypt button.
And a java ioerror that passes quickly.
Pressing Decrypt casts a java error about invalid object in stream 47.
MobileOrg Version 0.9.8
APG v1.0.8

same here
the push gets the encrypted file to Dropbox but APG throws errors.
I can use APG to decrypt the file from Dropbox.