Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!rutgers!att!cbnewsl!mjs
From: mjs@cbnewsl.ATT.COM (michael.j.scheutzow)
Newsgroups: comp.os.minix
Subject: Don't post binaries
Message-ID: <168@cbnewsl.ATT.COM>
Date: 27 Feb 89 23:54:10 GMT
Organization: AT&T Bell Laboratories
Lines: 28

> sed "s/^X//" >program.uue <<'END_OF_program.uue'
> Xbegin 644 program.out
> XM 0,@!"  __\ =   N <  + B           !      "X0 >+W(L/@\,"B\% 
> XMT> #PZ," %!34>AF!H/$!E#H)7#,P\<&SAT (*'.';L" )GW^P,&SAVCQ =0
> XMZ(9L1$2C9!T+P'4CBQY:*M'C_[>@!/\VUAVX'@!0_S9P!^CI9X/$"&H"Z-]O
> XM1$3#5E?( @  H<0'*T8(.P;.'7]6H<0'*T8(.P;.'7\2H<0'T>"CQ >ASAW1

*** OPINION *** OPINION *** OPINION *** OPINION *** OPINION ***

I don't think it is very appropriate to post binaries in this newsgroup.
The type of people reading this are generally knowledgeable enough to
deal with source code, and I think we should be given the opportunity
to do so.  I find it very valuable to see how different features are 
implemented.  If an author isn't willing to part with his/her source code,
I think they should find another way to distribute their work.

As a side issue, users better start considering the possible effects of
malicious software.  It is much easier to distribute a Trojan horse
(virus, worm, etc) in binary than in source code.  Even if you still
get caught, you have the opportunity to see if the damage was caused by an
intentional bug or not (backups, remember?).  

AT&T takes this threat very seriously, and has regulations against using
sourceless software obtained from public sources.  I think this is smart.

Flames to /dev/null please.

Mike S.