From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ken manheimer Newsgroups: gmane.emacs.devel Subject: interjecting a custom epa passphrase prompt Date: Wed, 1 Dec 2010 21:04:24 -0500 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001485f1db982a08c4049663d860 X-Trace: dough.gmane.org 1291255497 32677 80.91.229.12 (2 Dec 2010 02:04:57 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Dec 2010 02:04:57 +0000 (UTC) To: emacs-devel@gnu.org, Daiki Ueno Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 02 03:04:50 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PNyXR-00064U-8U for ged-emacs-devel@m.gmane.org; Thu, 02 Dec 2010 03:04:49 +0100 Original-Received: from localhost ([127.0.0.1]:43364 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PNyXQ-0004ZQ-M4 for ged-emacs-devel@m.gmane.org; Wed, 01 Dec 2010 21:04:48 -0500 Original-Received: from [140.186.70.92] (port=33611 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PNyXK-0004Uo-U6 for emacs-devel@gnu.org; Wed, 01 Dec 2010 21:04:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PNyXJ-00051R-Jj for emacs-devel@gnu.org; Wed, 01 Dec 2010 21:04:42 -0500 Original-Received: from mail-wy0-f169.google.com ([74.125.82.169]:35171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PNyXJ-00051F-FN for emacs-devel@gnu.org; Wed, 01 Dec 2010 21:04:41 -0500 Original-Received: by wyj26 with SMTP id 26so281362wyj.0 for ; Wed, 01 Dec 2010 18:04:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=/YNGQ8Gd2EEZCUMMXAywmDK0En6otmE1Eitn+k2zAdY=; b=x1xeNM/AnbI83QY0PMPfCyt165pL5luNG6XaeNud1Qu9zk7AWCx+x+kg03248mD6rB XmyHENUMPazao/s+o0GRdUSjCvvN6i4RYH4izBBz5xUvahgDCRdGft8GpMG/Aa3hla6X EvsNutUrSNhYwJbbyY+KwOwAq7h3lD2mvI8As= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=qAj+ifyaCPMVd7cDgMYMcj2iomvI+4vE5R0MY35wGprk6fHGDHs76J0QrcqQQLawbw VRWBr/BpLSmhZp7C7TwlWGIarLy686nA3xDtuiBQ9VkeGN/PpErboM7Cax12lWbkWkMm SYoV9P1HsOngHU9q2D9on4wunftRy1G4RmUuY= Original-Received: by 10.216.163.80 with SMTP id z58mr491890wek.33.1291255479404; Wed, 01 Dec 2010 18:04:39 -0800 (PST) Original-Received: by 10.216.18.8 with HTTP; Wed, 1 Dec 2010 18:04:24 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:133296 Archived-At: --001485f1db982a08c4049663d860 Content-Type: text/plain; charset=ISO-8859-1 hi! i'm working on migrating allout.el topic encryption to the epg.el interface to gpg, but am encountering a problem. i would like to continue to maintain some unique passphrase features unique to working with multiple entries in a single file, but i'm failing to substitute my custom passphrase prompting for the epg passphrase callback mechanisms, and i wonder what i'm doing wrong. specifically, i am trying to use 'epg-context-set-passphrase-callback' to adjust the context for encryption to try to interject my own prompting, but it's having no effect. i see that 'epg-passphrase-callback-function' has been marked obsolete, but that looks like a separate provision from the context-specific callback. in fact, i'm hoping so, because without a way to explicitly reuse a passphrase i have no way to do verification of a symmetric passphrase against one associated with all topics in the file, or to present a similarly associated passphrase hint. (i also figure that 'epg-context-set-passphrase-callback' would have been removed, or at least conspicuously marked as ineffective, if it no longer works!) has all provision for custom passphrase prompting in epg been eliminated? -- ken http://myriadicity.net --001485f1db982a08c4049663d860 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hi! =A0i'm=A0working on migrating allout.el topic encryption to th= e epg.el interface to gpg, but am encountering a problem. =A0i would like t= o continue to maintain some unique passphrase features unique to working wi= th multiple entries in a single file, but i'm failing to substitute my = custom passphrase prompting for the epg passphrase callback mechanisms, and= i wonder what i'm doing wrong.

specifically,=A0i am trying to use 'epg-context-set= -passphrase-callback' to adjust the context for encryption to try to in= terject my own prompting, but it's having no effect. =A0i see that '= ;epg-passphrase-callback-function' has been marked obsolete, but that l= ooks like a separate provision from the context-specific callback. =A0in fa= ct, i'm hoping so, because without a way to explicitly reuse a passphra= se i have no way to do verification of a symmetric passphrase against one a= ssociated with all topics in the file, or to present a similarly associated= passphrase hint. =A0(i also figure that=A0'epg-context-set-passphrase-= callback' would have been removed, or at least conspicuously marked as = ineffective, if it no longer works!)

has all provision for custom passphrase prompting in ep= g been eliminated?
--=A0
--001485f1db982a08c4049663d860--