Path: utzoo!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!radius!lemke From: lemke@radius.UUCP (Steve Lemke) Newsgroups: news.software.b Subject: Re: Anyone interested in end-to-end checksums in news? Message-ID: <1191@radius.UUCP> Date: 18 Nov 89 22:52:36 GMT References: <1989Nov16.173359.22435@utzoo.uucp> <14603@well.UUCP> Reply-To: radius!lemke@apple.com (Generic Account) Organization: Radius Inc., San Jose, CA Lines: 26 In article <14603@well.UUCP> Jef Poskanzer writes: } ^^^^^^ ^^^^^ }? Unless I'm missing something, you compute it once, when an article }is submitted, and each site checks it upon reception. That's the whole }point of an end-to-end check. Sure it means that the Path: is not }protected, but I can live with that. OK, so it gets checked upon reception, but maybe I'm missing something here - what happens if the check fails? This doesn't seem like it will happen real-time (as the transfer is taking place) but rather when the rnews executes, which is usually after it's too late to ask for the article to be sent again. Well, do you somehow try to request that article again later? Of course, if it was munched then you don't really know how to ask for it again, do you? So, do you ignore it? You only want non-munched news, regardless of what it was that actually caused the checksum to fail? Just forget about anything that doesn't pass? I just recently started running bnews and everything seems to be working fine, but I'm no expert - I'm just curious as to what happens in the event that your proposed checksum fails upon receipt. -- ============================================================================= ===== Steve Lemke, Engineering Quality Assurance, Radius Inc., San Jose ===== ===== Reply to: radius!lemke@apple.com (Coming soon: radius.com ...) ===== ===== AppleLink: Radius.QA; GEnie: S.Lemke; Compu$erve: 73627,570 =====