From: "Steven E. Harris" <seh@panix.com>
Cc: "Ding Mailing List" <ding@gnus.org>
Subject: Re: netrc.el now supports encoded files
Date: Tue, 06 Jan 2004 12:59:02 -0800 [thread overview]
Message-ID: <q67wu84kd49.fsf@L75001820.us.ray.com> (raw)
In-Reply-To: <ilu1xqcesg3.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 06 Jan 2004 21:24:28 +0100")
Simon Josefsson <jas@extundo.com> writes:
> I'm not sure the current netrc.el approach should be advertised as
> secure, there is more to file encryption than using some block
> cipher in CBC mode, and deriving the key and iv from a password. It
> is more like obfuscation. OTOH, obfuscation is what people seem to
> want.
Now I'm confused. If encrypting the file with a symmetric cipher
doesn't count as "secure," what more would it take to make this system
secure? What's the difference between obfuscation and security in this
case?
--
Steven E. Harris
next prev parent reply other threads:[~2004-01-06 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 23:22 Ted Zlatanov
2004-01-05 23:34 ` Jesper Harder
2004-01-06 1:02 ` Ted Zlatanov
2004-01-06 0:13 ` Steven E. Harris
2004-01-06 1:01 ` Ted Zlatanov
2004-01-06 21:57 ` Chris Green
2004-01-06 23:00 ` Ted Zlatanov
2004-01-06 23:25 ` Simon Josefsson
2004-01-06 23:58 ` Ted Zlatanov
2004-01-07 0:09 ` Simon Josefsson
2004-01-07 2:53 ` Lars Magne Ingebrigtsen
2004-01-08 22:03 ` Ted Zlatanov
2004-01-27 19:44 ` Ted Zlatanov
2004-01-07 14:47 ` Chris Green
2004-01-08 20:48 ` Ted Zlatanov
2004-01-06 13:28 ` Simon Josefsson
2004-01-06 19:58 ` Ted Zlatanov
2004-01-06 20:24 ` Simon Josefsson
2004-01-06 20:59 ` Steven E. Harris [this message]
2004-01-06 22:00 ` Simon Josefsson
2004-01-06 22:24 ` Simon Josefsson
2004-01-06 22:56 ` Ted Zlatanov
2004-01-06 23:13 ` Ted Zlatanov
2004-01-06 23:35 ` Simon Josefsson
2004-01-06 20:33 ` Simon Josefsson
2004-01-06 23:14 ` Ted Zlatanov
2004-01-06 23:19 ` Richard Hoskins
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=q67wu84kd49.fsf@L75001820.us.ray.com \
--to=seh@panix.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).