Article View: sci.crypt
Article #3156Re: [QUESTION]: PUBLIC-KEYS (ETC) FOR PUBLIC BBS NETWORK
From: BEEZER
Date: Tue, 12 Jan 1993 19:47
Date: Tue, 12 Jan 1993 19:47
12 lines
1116 bytes
1116 bytes
I understand clearly the advantage/need to encrypt before uploading, but 1) most users to this network won't d/l the s/w and spend so much time encrypting (currently incompatible with all off-line mail readers)... 2) The BBS/network will likely be more vulnerable to shut-down by feds than the post office is... ie. sending local/abroad drug trafficing via public access bbs/network would be an easy and expected abuse. In this case, the sysop sets himself up for owning and transmitting illegal material - although he doesn't know that, he should... shouldn't he?
Technical Details
Message-ID:
<12JAN199312470550@cc.utah.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cc.utah.edu!beezerReferences:
<12JAN199300513143@cc.utah.edu> <1iun0sINN9f6@uwm.edu>Show Full Headers
Complete Article Headers
Newsgroups: sci.crypt Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cc.utah.edu!beezer From: beezer@cc.utah.edu (BEEZER) Subject: Re: [QUESTION]: PUBLIC-KEYS (ETC) FOR PUBLIC BBS NETWORK Message-ID: <12JAN199312470550@cc.utah.edu> Summary: You're better off to do it yourself. News-Software: VAX/VMS VNEWS 1.4-b1 Sender: news@fcom.cc.utah.edu Organization: Salt Lick, UT References: <12JAN199300513143@cc.utah.edu> <1iun0sINN9f6@uwm.edu> Date: 12 Jan 1993 12:47 MST Lines: 13