From: lull@acm.org (John Lull)
To: cypherpunks@toad.com
Message Hash: 79e8c8828403f80c83de426bb4642194f022840f4d662670af14197de86a4016
Message ID: <30e2ce46.37070124@smtp.ix.netcom.com>
Reply To: <199512281517.JAA13397@cdale1.midwest.net>
UTC Datetime: 1995-12-29 02:41:50 UTC
Raw Date: Fri, 29 Dec 1995 10:41:50 +0800
From: lull@acm.org (John Lull)
Date: Fri, 29 Dec 1995 10:41:50 +0800
To: cypherpunks@toad.com
Subject: Re: Proxy/Representation?
In-Reply-To: <199512281517.JAA13397@cdale1.midwest.net>
Message-ID: <30e2ce46.37070124@smtp.ix.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain
David E. Smith wrote:
> The question is: how do the current software packages handle representatives
> and proxies for a given is-a-person? Using PGP as an example, I can't sign
> a message with Helen's key. And a message signed with my key won't hold
> as much weight because "Dave" is not "Helen." And if every message I send
> on behalf of Helen has to be followed up by a message from Helen stating
> "yes, Dave may act on my behalf for this instance" then much of the point
> of the proxy process is lost. (i.e. the reduction of Helen's workload etc.)
I would think a power-of-attorney, signed by Helen, would do the
trick. This would normally be valid for some pre-defined period, for
a pre-defined set of transactions, and would not have to be generated
anew each time.
Return to December 1995
Return to ““Perry E. Metzger” <perry@piermont.com>”