Security and Maintenance issues in whois++

Michael Mealling <> Thu, 29 September 1994 15:47 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa05033; 29 Sep 94 11:47 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05027; 29 Sep 94 11:47 EDT
Received: from [] by CNRI.Reston.VA.US id aa11466; 29 Sep 94 11:47 EDT
Received: by (8.6.9/UCD2.50) id IAA26795; Thu, 29 Sep 1994 08:34:21 -0700
Received: from by (8.6.9/UCD2.50) id IAA26788; Thu, 29 Sep 1994 08:34:19 -0700
Received: (from ccoprmm@localhost) by (8.6.9/8.6.9) id LAA29162 for; Thu, 29 Sep 1994 11:34:17 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Michael Mealling <>
Message-Id: <>
Subject: Security and Maintenance issues in whois++
Date: Thu, 29 Sep 1994 11:34:16 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 870

I know the working group has been disolved but one of the things I keep
worrying about is record maintenance and the security of those records.

I went and dug up an old whois++ spec and have edited out everything except
the security and record maintenance stuff. I'll be making comments about
it and everyone else is free to steal the HTML and hack on it. Check this out:

Is there any concensus in the wnils group that this is something that
is worth another paper as an adjunct to the existing spec or is
everyone dead set again having a writable database?


<HR><A HREF="">
<ADDRESS>Michael Mealling</ADDRESS>