>>>>> "Brock" == Brock Rozen <brozen@netvoyage.net> writes:
Brock> Ideally, it would be nice. But I'm a list-manager for a few
Brock> lists on ANOTHER system. I don't believe I would have
Brock> access to the global password and then I'm still in a bind.
Brock> A compromise to this is having it unsubscribe that user to
Brock> any list that has that password. Thus, if you have 5 lists
Brock> that have the same password (generally, a bad idea) you
Brock> could unsub any user with the above.
We have PGPdomo now. I think majordomo can make a lot more use of
signed administrator messages. There is no general certification
format for PGP, so we invent just what we need and sign it! Okay, the
interface to PGP is a pain in the butt. I wish i had time to fix that.
A series of files signed by the majordomo administrator saying:
$listmaster{'mylist'}="0x1E7E6B59";
or
$listmaster{'cherag-l'}="0x1E7E6B59";
The list administrator includes as many of these signed documents as
needed before the "approve pgp command" which is signed by key
0x1E7E6B59. Since they are signed by the majordomo administrator
majordomo is willing to modify its behaviour and allow the signed
commands to apply to "all" lists in this key's pervue.
These are horribly application specific certificates, but I think
anything else is a more horrible kludge, and this isn't X.509 :-)
Follow-Ups:
References:
|
|
