From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Once again: PGnus & PGP
Date: 17 Apr 1999 16:50:36 +0200 [thread overview]
Message-ID: <8790br9u83.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "17 Apr 1999 15:32:26 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> wmperry@aventail.com (William M. Perry) writes:
>
> > Make it able to be done by any arbitrary elisp function. From the
> > point of view of the NSA, having an external function or a
> > DLL/script do the munging is equivalent. It is still a 'hook' for
> > some 3rd party to do the encryption.
>
> Does that mean file-name-handler-alist is illegal because you can
> use it to hook up PGP to Emacs?
No; I believe `file-name-pgp-handler' with PGP-friendly defaults would
be illegal.
A "general mechanism for handling multiparts" sounds NSA-friendly to
me. Bill?
next prev parent reply other threads:[~1999-04-17 14:50 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-07 14:10 Stefanie Teufel
1999-04-07 14:33 ` Kai.Grossjohann
1999-04-07 16:30 ` Stefanie Teufel
1999-04-07 19:32 ` Jack Twilley
1999-04-07 21:01 ` Stefanie Teufel
1999-04-08 0:54 ` Stainless Steel Rat
1999-04-08 15:55 ` Jack Twilley
1999-04-08 19:38 ` Stainless Steel Rat
1999-04-09 4:58 ` Jack Twilley
[not found] ` <m3zp4imat6.fsf@tank.worldcom.nl>
[not found] ` <tank@xs4all.nl>
1999-04-10 0:17 ` Stainless Steel Rat
1999-04-10 12:57 ` Jack Twilley
1999-04-10 22:14 ` Carey Evans
1999-04-12 2:28 ` Jack Twilley
1999-04-12 7:18 ` Carey Evans
1999-04-12 15:49 ` Jack Twilley
1999-04-12 16:57 ` David S. Goldberg
1999-04-12 19:47 ` Carey Evans
1999-04-12 20:05 ` Jack Twilley
1999-04-12 20:34 ` David S. Goldberg
1999-04-12 20:44 ` Jack Twilley
1999-04-12 21:03 ` Stefanie Teufel
1999-04-12 23:51 ` Stainless Steel Rat
1999-04-13 0:36 ` Russ Allbery
1999-04-13 0:57 ` Stainless Steel Rat
1999-04-13 7:54 ` Russ Allbery
1999-04-20 10:49 ` Jari Aalto+list.ding
1999-04-20 13:40 ` Stainless Steel Rat
1999-04-20 20:30 ` Hrvoje Niksic
1999-04-20 23:58 ` Stainless Steel Rat
1999-04-21 7:20 ` Kai.Grossjohann
1999-04-21 11:32 ` Jari Aalto+list.ding
1999-04-21 14:29 ` Stainless Steel Rat
1999-04-21 15:49 ` Jari Aalto+list.ding
1999-04-21 17:57 ` Stainless Steel Rat
1999-04-21 18:03 ` Samuel Tardieu
1999-04-12 21:47 ` Stainless Steel Rat
1999-04-20 10:28 ` Jari Aalto+list.ding
1999-04-11 13:41 ` Stainless Steel Rat
1999-04-11 14:27 ` Stefanie Teufel
1999-04-11 17:41 ` Stainless Steel Rat
1999-04-17 7:49 ` Lars Magne Ingebrigtsen
1999-04-17 10:37 ` Stefanie Teufel
1999-04-17 15:15 ` Lars Magne Ingebrigtsen
1999-04-17 15:53 ` William M. Perry
1999-04-18 10:47 ` Stefanie Teufel
1999-04-17 12:16 ` William M. Perry
1999-04-17 13:32 ` Kai.Grossjohann
1999-04-17 14:50 ` Hrvoje Niksic [this message]
1999-04-17 15:52 ` William M. Perry
1999-04-17 16:12 ` Hrvoje Niksic
1999-04-17 15:52 ` William M. Perry
1999-04-17 15:18 ` Lars Magne Ingebrigtsen
1999-04-12 2:16 ` Jack Twilley
1999-04-12 17:52 ` Stainless Steel Rat
1999-04-20 10:24 ` Jari Aalto+list.ding
1999-04-20 13:36 ` Stainless Steel Rat
1999-04-21 20:26 ` Russ Allbery
1999-04-07 21:07 ` Jes Sorensen
1999-04-07 22:01 ` François Pinard
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=8790br9u83.fsf@pc-hrvoje.srce.hr \
--to=hniksic@srce.hr \
/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).