1994-12-01 - Re: Warm, fuzzy, misleading feelings

Header Data

From: werewolf@io.org (Mark Terka)
To: cypherpunks@toad.com
Message Hash: 751ab524495bec9ea15acb0ed696db200d7c6bb2b55f0bcd7e6ae9f9fb607ade
Message ID: <wLJtkOwscEs5075yn@io.org>
Reply To: <199412010119.RAA06900@python>
UTC Datetime: 1994-12-01 02:59:41 UTC
Raw Date: Wed, 30 Nov 94 18:59:41 PST

Raw message

From: werewolf@io.org (Mark Terka)
Date: Wed, 30 Nov 94 18:59:41 PST
To: cypherpunks@toad.com
Subject: Re: Warm, fuzzy, misleading feelings
In-Reply-To: <199412010119.RAA06900@python>
Message-ID: <wLJtkOwscEs5075yn@io.org>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

In article <199412010119.RAA06900@python>,
"Dr. D.C. Williams" <dcwill@python.ee.unr.edu> wrote:
>
>I've been following the dig sig fracas with great interest. While
>I can see merit in both sides, the pro-sig argument is weakened
>by their endorsement of sig spoofing. If the object is to heighten
>
>The way I see it, either sign or don't sign, but attaching a
>bogus signature block to a message for the sole purpose of pacifying
>a mailing list requirement diminishes the significance of crypto
>and sullies the image of all who participate.

I'm not entirely sure, but I thought that 90% of the "anti-sig" argument was
that it was a pain in the ass because the tools did not exist on some machines
to allow relatively seamless signing for some users (in a secure fashion).

If thats the case.....isn't it an equal pain in the ass to go to the trouble of
forging a sig? :> You would likely have to go through more key strokes and
other routines to forge one. Why not just play by the rules and sign a
message?

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBLt02ia+YbMzawbu5AQFzCQP7BTP5dyuQf8nmFIeEGeTzxjaTrWYbB9no
ZHQIC2u86TbQX1EAiA8LMCWlk+CHhvMJSMXt7QpK6h+ylpYQxJuEwebQcPPdqYAb
szD+AfeFMGEovGpt2LxQXnAT098uyIgSkf0ALGd7iTWDBsVJz74M59m8thqpHs92
W27FsPThttY=
=Orub
-----END PGP SIGNATURE-----





Thread