Gnus development mailing list
 help / color / mirror / Atom feed
From: Adrian Aichner <adrian@xemacs.org>
To: ding@gnus.org
Subject: Re: EasyPG 0.0.12
Date: Wed, 30 May 2007 07:24:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070530T090846-624@post.gmane.org> (raw)
In-Reply-To: <716b7bce-fb42-4e76-89f3-9d798a2d1e14@well-done.deisui.org>

Daiki Ueno <ueno <at> unixuser.org> writes:

> 
> >>>>> In <loom.20070529T124032-777 <at> post.gmane.org> 
> >>>>>	Adrian Aichner <adrian <at> xemacs.org> wrote:
> > > > The biggest issue I found is that ediff-revision will not work with it
> > > > out of the box.

> > The issue, as I understand it, is that data written to disk into files
> > matching epa-file-name-regexp with write-region cannot just always be
> > encrypted.
> 
> > It that data is coming from processes, like "cvs update ..." via
> > vc-find-version then it is already/still encrypted.
> 
> > Perhaps I am missing some obvious point how to solve this problem.
> 
> I see there are two different issues.  The first is, vc-find-version
> doesn't inhibit file-name-handlers when creating backup files, as you
> mentioned above.  The second is, if you want to make diffs for decrypted

Hi Daiki!

ah, inhibiting file-name-handlers might be an option, even though I
don't know whether it will break existing cusomizations out there.

> text, it has to be written into files since ediff calls the external
> program to compute diffs.  Which may cause a security problem unless
> Emacs warns about it.

But epg does this already for
epg-decrypt-file
epg-decrypt-string
and the the encrypt and verify functions as well.

In this ediff-revision case data would still go to disk encrypted (but
encrypted only once).

> 
> Something different.  jka-compr seems to have the same issue on "*.gz"
> files.  So... can this kind of problem be better solved by advices (or
> hooks, if any) to ediff-revision?

No, by the time ediff-revision kicks in, the damage is already done.

The file written to disk by vc-find-version has been encrypted one more time.

Perhaps I try the inhibit file handlers ideea of your.

BTW, I'm running with CVS EasyPG now, and I'm happy to confirm the XEmacs
compatibility and buffer-modified issues fixed.

Best regards!

Adrian

> 
> Regards,





  reply	other threads:[~2007-05-30  7:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29  4:42 Daiki Ueno
2007-05-28 15:34 ` Adrian Aichner
2007-05-29  7:15   ` Daiki Ueno
2007-05-29 10:50     ` Adrian Aichner
2007-05-30  3:50       ` Daiki Ueno
2007-05-30  7:24         ` Adrian Aichner [this message]
2007-05-30  8:30           ` Daiki Ueno

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=loom.20070530T090846-624@post.gmane.org \
    --to=adrian@xemacs.org \
    --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).