[DGD] mud as a statedump + trusted computing?

[Shentino]

On Wed, Aug 22, 2012 at 2:54 PM, Noah Gibbs <noah_gibbs at yahoo.com> wrote:
> I guess the question would be...  Are you preventing cheating even though people can see your statedump?  If so, you basically can't keep them from getting your key as well.

I realized that about 1 hour after posting...

Not much sleep last night honestly.
>
> And if they can't see your statedump and/or distrib files, you can just have a key in the source base.  So you can use that key to validate, but there's no specific reason to make it live in the statedump but not source files.
>
>
> ________________________________
>  From: Shentino <shentino at gmail.com>
> To: All about Dworkin's Game Driver <dgd at dworkin.nl>
> Sent: Wednesday, August 22, 2012 1:22 PM
> Subject: [DGD] mud as a statedump + trusted computing?
>
> Someone awhile back suggested distributing a mud as a statedump file.
>
> I also thought of how a TPM module keeps a private key hard-burned
> into itself, and figured that a live mud could hide something similiar
> inside itself that could be used for sig-checking updates to the
> mudlib.
>
> Might be a useful sort of thing on distributed muds to prevent cheating.
>
> Discuss?
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd