From: lars@larsko.org (Lars Kotthoff)
Subject: [sup-talk] Encrypted password in configuration file
Date: Fri, 28 Aug 2009 08:23:49 +0100 [thread overview]
Message-ID: <20090828082349.61bfc91b@ronin.larsko.net> (raw)
In-Reply-To: <f4cc59760908271937t764e61aeh7f105c7195fec1ce@mail.gmail.com>
> It's possible, but slightly pointless.
Not if the user supplies the passphrase, e.g. it could be encrypted with the
user's GPG key and ask for the passphrase at startup.
Lars
next prev parent reply other threads:[~2009-08-28 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 20:54 Lars Kotthoff
2009-08-28 2:37 ` Jim Cheetham
[not found] ` <20090828012502.15484x8musndy5mo@webmail.seas.upenn.edu>
2009-08-28 7:07 ` Jim Cheetham
2009-08-28 7:23 ` Lars Kotthoff [this message]
2009-08-28 9:28 ` Jim Cheetham
2009-08-28 20:29 ` William Morgan
2009-08-28 22:48 ` Mike Kelly
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=20090828082349.61bfc91b@ronin.larsko.net \
--to=lars@larsko.org \
/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