From Address Forged

On Thu, Nov 05, 1998 at 06:01:23PM +0100, Siegfried Langenbach wrote:
> On 5 Nov 98, at 17:45, Daniel Karrenberg wrote:
> 
> > 
> > Wilhelm and other colleagues,
> > 
> > it appears that the header forging did only occur in an effort to
> > correct mistakes made earlier.  Repeat: the updates that caused the
> > problems originally were not done using forged headers.  This does not
> > mean header forging was not very bad judgement, but at least it occurred
> > only in an effort to correct earlier mistakes.  The RIPE NCC will work
> > with Transpac on a post-mortem analysis.  More news as it develops. 
> 
> Hmm, 
> if it was needed to forge a header to correct a mistake,
> how then the mistake could be done without forging the header?
> 
> siegfried



I get tired discussing this.


Yes, the original 'mistake' didn't involve forged headers.
Yes, old records have been deleted this way.
No, these records were not protected by their maintainers (auth: NONE).
Yes, the handles were reallocated to other records.
Yes, some of these new records were protected by their maintainers.
Yes, these new records were deleted using forged mail headers.
No, the old records were not restored because the restoring update 
    was sent too early (usually in the same mail which inherently
    fails).
Yes, the yet-again free handles have been reallocated to even more new
    records again.
Yes, deleting the new records caused more inconsistencies and more data
    loss.
No, deleting the new records didn't correct the original 'mistake' at all.
Yes, deleting the new records produced more errors outside the RIPE-DB
    realm (for example, registrations of domains that reference the
    new-but-then-deleted person records in the RIPE-DB failed).
Yes, deleting the new records sabotaged other people's attempt to
    recover from original 'mistake'.


We have thus switched from MAIL-FROM to CRYPT-PW authorization.
If I see any unauthorized update in the future, the responsible
person gets shot.




-- 
i.A. Michael van Elst                /          phone: +49 721 6635 330
Xlink - Network Information Centre \/           fax:   +49 721 6635 349
Vincenz-Priessnitz-Str. 3          /\ link      http://nic.xlink.net/
D-76131 Karlsruhe, Germany        /_______      email: hostmaster at xlink.net
[ Xlink Internet Consulting GmbH, Sitz Koeln                              ]
[ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert           ]