[VANILLA-L:1211] Re: [VANILLA-L:1209] Maybe I'm Naive

["Nick Trown" <ntrown@inprise.com>]

Hi Carlos,

    Usually what I did was if it was someone I knew I put it in.  After all if they made a borg I had no
problem pulling the key and then letting everyone else know that he/she cheats :-)    If it is someone I don't
know I'm a little more cautious but I usually put it in.

    A couple of guidelines I followed were:

        1) check for what platform/client the key is for.  Is there one in the key list already?  If so, I'm
suspicous so I email the submitter of the key and ask them about it and why they aren't using the already made
client.

        2) If it is someone I know and it is a new client/platform combination I put it in.

        3) If it isn't someone I know I email them about it and ask a few questions.  It's up to you what you
ask, something to try and find out what they've done.


I never tested out the clients.   I didn't have access to all the platforms and it would have been too time
consuming.

>From scanning over the keys that have been added below I'd say the second one, the COW key, is bogus.  COW has
a somewhat annoying feature of automatically emailing the key maintainer (you Carlos :-) )  everytime a key is
made.  Since the key is for "unix" which isn't very discriptive I usually ignore these.

For the JTrek one I'd make it a "test" client type.  Therefore, it would be easier for say Bob to ignore it if
he chooses.

The last thing I do is check the 'ct' field.  I usually try to group them together so that in the motd there
aren't tons of client types.  Therefore, I'd make the first client, "Paradise 2.4 Patch 1", be just "Paradise
2.4".  There are other ways to get the exact patch/version information.

Sorry Carlos,  I should have told you all this stuff before.

Nick

"Carlos Y. Villalpando" wrote:

> Hey all.
>
> A request for advise.
>
> I've been blindly accepting keys on faith from client submitters since
> I started serving the keys.
>
> I'm not sure If that's a good thing.
>
> What should I do?
>
>  1) Message here and to r.g.n. saying that I've got a new key and who
>     I got it from.
>
>  2) Accept keys from established client developers. (I have no clue
>     who they are)
>
> Or.
>
>  3) Test out each client.
>
> Comments? What can I do to make it harder for people to slip in a
> blessed borg?
>
> At any rate, here are the few keys I've gotten so far:
>
> paradise.jkauffman.x86-sol7:ct=Paradise 2.4 Patch 1b:cr=John Kauffman <jkauffm@hellfire.dusers.drexel.edu>
>
> key.cow.unix:ct=Client Of Win:cr=nguyenpk@kuci.org:
>
> key.JTrek:ct=JTrek 0.94beta:cr=robertt@starwave.com:
>
> OpenBSD-sparc-paradise-2.4:ct=Paradise 2.4:cr=Ari Johnson <ari_j@hotmail.com>:
>
> Suprisingly enough, nobody's compiling any new clients, even with
> paradise clients being expired en masse.
>
> --Carlos V.
>
> +
> ++ Vanilla-l Mailing List ++
> To unsubscribe: send "unsubscribe vanilla-l" to majordomo@real-time.com
> For more information: http://archives.real-time.com

+
++ Vanilla-l Mailing List ++
To unsubscribe: send "unsubscribe vanilla-l" to majordomo@real-time.com
For more information: http://archives.real-time.com