Bogus .UUCP addresses under SCO

[David Lesher]

I recently exchanged mail with a user down under about his bogus
.UUCP suffix, instead of the correct .oz.au that he showed in
his .sig files.

He told me that SCO had shipped them only binaries for bnews, with the
.UUCP hardcoded into it.

1) Why would SCO ship brain_damaged binaries such as this?

2) I thought it was 'rn' that had the .UUCP hardcode bug. Does bnews 
also suffer?

3) Is it any wonder so many sites have this flaw (I see them daily) if
this is the case? [danger: rhetorical question]

4) How would this user, *with the least effort* get his own version of
bnews compiled? (i.e. did SCO do weird things to news to make it work
on their box?)

comments/flames/free_beer?
-- 
A host is a host from coast to coast.....wb8foz at mthvax.cs.miami.edu 
& no one will talk to a host that's close............(305) 255-RTFM
Unless the host (that isn't close)......................pob 570-335
is busy, hung or dead....................................33257-0335