emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Andrea Crotti <andrea.crotti.0@gmail.com>
Cc: Org mode <emacs-orgmode@gnu.org>
Subject: Re: org-passwords
Date: Tue, 15 Mar 2011 09:38:57 -0500	[thread overview]
Message-ID: <AANLkTimBjNEFX7jm=py+i6KWg-iX8HGru4CGnSvL=6G+@mail.gmail.com> (raw)
In-Reply-To: <sa07hc05vfl.fsf@gmail.com>

On Tue, Mar 15, 2011 at 9:07 AM, Andrea Crotti
<andrea.crotti.0@gmail.com> wrote:
> Last week I finally wrote all my passwords in a crypted org file, using
> properties and column mode.
> This is very nice, and taking inspiration from the wonderful
> org-contacts, I decided to open on github org-passwords.
> https://github.com/AndreaCrotti/org-passwords
> This VERY simple initial version already basically works, asking name of
> the service, username and password and storing it in a (hopefully)
> cypted file.
> Now it would be nice to make it easy to fetch and modify passwords.
> Another thing which I'm a bit "annoyed" is that keeping crypted files
> under git, I never see the real diff since the files are binary.
> Do maybe some of you found a way to see a text diff even on crypted
> files?

No idea... but my searching yielded:
- http://stackoverflow.com/questions/2456954/git-encrypt-decrypt-remote-repository-files-while-push-pull
- http://git.661346.n2.nabble.com/Transparently-encrypt-repository-contents-with-GPG-td2470145.html

They both seem to be speaking about the same thing. Not really
understanding it all, but it sounds like a locally kept "filter" of
some sort that runs gpg -d on whatever files you pull and gpg -ea on
whatever you push.


> PS. anyone is welcome to send suggestions/patches also to me directly if
>    interested...

      reply	other threads:[~2011-03-15 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 14:07 org-passwords Andrea Crotti
2011-03-15 14:38 ` John Hendy [this message]

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:

  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='AANLkTimBjNEFX7jm=py+i6KWg-iX8HGru4CGnSvL=6G+@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=andrea.crotti.0@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).