From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] GPG Support
Date: Tue, 03 Jul 2007 19:55:56 -0700 [thread overview]
Message-ID: <1183517242-sup-3554@south> (raw)
In-Reply-To: <1182210252-sup-8502@mona>
Excerpts from jeff.covey's message of Mon Jun 18 17:00:52 -0700 2007:
> Excerpts from Chris Lee's message of Thu May 17 17:24:11 -0400 2007:
> > The sources.yaml file is pgp encrypted now.
>
> why is that? there doesn't seem to be any sensitive information in
> sources.yaml, and encrypting it makes it harder to deal with.
For IMAP and mbox+ssh sources, the username and password is stored in
sources.yaml. Sup is careful to create it with the right unix mode, so
I'm not convinced of the vital necessity of this feature, but I'm not
opposed to its very existence either.
> i wouldn't bother with storing passwords/phrases and encrypting files,
> i would just let gpg prompt people for the words/phrases as needed.
> if they don't want to type them each time, they can use something like
> gpg-agent.
I tend to agree. I'm happy to offload as much functionality to other
programs as possible.
> i only use one key myself, but it would be nice to be able to specify a key
> for each account under ":accounts:".
Agreed.
I haven't incorporated Chris's patch yet, mostly because I wanted to
flesh out Sup's multi-account support, but now that things are better on
that end, I do plan to revisit the issue. Chris, if you're still there,
please don't feel like I've ignored you.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-07-04 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 21:24 Chris Lee
2007-06-19 0:00 ` jeff covey
2007-07-04 2:55 ` William Morgan [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1183517242-sup-3554@south \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox