-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Tue, 14 Dec 2004, Dave Page wrote:
>> Further, the subscription address list would be automatically
>> echoed to a non-postgresql.org mailserver somewhere, so that
>> it can be used to coordinate in the event of a general
>> network failure like last week's.
>
> You know how to do this? I've been looking at it for the main lists and
> haven't found any way to have a second server.
* We could rsync the subscriber list. (for any @PostgreSQL.org lists)
* ... since I think the subscriber list of admins@PostgreSQL.org list
will not change day by day, we can mirror the users by hand.
>> I know this sounds similar to what Devrim proposed a few
>> months ago, but this
>> would be a bit different. For one, it would not concern web site
>> development *at all*, which would still happen on this list.
>> It would instead be devoted exclusively to "Server A is down,
>> who can take the list archives?" and "Hub.org is going down
>> at 5pm to relocate, switching over to alternate DNS" type
>> messages. Also exchanging passwords and setup info,
>> necessitating a closed, non-archived list.
>>
>> Does this seem like a good idea?
>
> Exchanging passwords should be done in private email, with the username
> & hostname *never* appearing in the same message as the password imho. A
> list is definitely not the place for that sort of thing.
IMHO using PGP should be a must for all subscribers. If someones sends a
password to another, he/she will sign+encrpyt the e-mail with the
receiver's key so that only the receiver can read the e-mail.
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org devrim.gunduz~linux.org.tr
http://www.tdmsoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBv4Kotl86P3SPfQ4RAtcWAJ9Qn4JRpET5zWCbdYXgZjCWLYNFSgCgsVh5
pVfVViw2wj8UhRioztKrhmM=
=d1B8
-----END PGP SIGNATURE-----