full-disclosure - impersonation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20020816073739.GE1131@home.parts-unknown.org>
From: benfell at greybeard95a.com (David Benfell)
Subject: impersonation

On Thu, 15 Aug 2002 12:24:41 -0600, Charles Stevenson wrote:
> Jonathan,
> 
> On Thu, Aug 15, 2002 at 12:03:27PM -0400, Jonathan Rickman wrote:
> > Yep. Everyone should start signing messages. I think I'll start now...
> 
> Count me in.
> 
> peace,
> core
> 
Having been doing this all along, far be it from me to argue.

However:

[-- PGP output follows (current time: Fri 16 Aug 2002 12:23:20 AM PDT) --]
gpg: Signature made Thu 15 Aug 2002 11:24:40 AM PDT using DSA key ID 13B27893
gpg: Can't check signature: public key not found
[-- End of PGP output --]

This makes it difficult to confirm your signature.  I would suggest
publishing your public keys on public key servers.

Also, everyone should be cautioned that Windows virus-checking
programs have been known to mistake GnuPG (and I would presume PGP)
signatures for virii.  As you can imagine, this can lead to grave
misunderstandings.

So while I'm all in favor of using verifiable cryptographic
signatures, doing so may make this list less friendly to those who
(sometimes under duress) are using Windows.

Finally, given the sort of spam we've been seeing, there's little to
stop these children from also signing their messages; so I would
suggest the following procedures (without regard to how difficult they
might be to actually implement):

1) Moderate subscription requests.  Subscription requests must be
accompanied by a verifiable cryptographic signature.

2) Only subscribers may post, and all postings must have verifiable
cryptographic signatures matching the key used to sign the original
subscription request.

-- 
David Benfell, LCP
benfell@...ts-unknown.org
---
Resume available at http://www.parts-unknown.org/resume.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20020816/acedc5f9/attachment.bin