Article View: comp.security.misc
Article #425Re: Covert channel
From: Bill Meyers
Date: Wed, 19 Aug 1992 22:34
Date: Wed, 19 Aug 1992 22:34
15 lines
1465 bytes
1465 bytes
In article <21382@rpp386.lonestar.org> jfh@rpp386.cactus.org (John F. Haugh II) writes: [ ... ] >The definition which I have always used for "covert channel" is the one >straight out of the Orange Book - "covert channel - A communications >channel that allows a process to transfer information in a manner that >violates the system's security policy." If you are permitted to change >the mail headers, doing so cannot violate the system's security policy. I believe this definition intends -- although I see it doesn't state -- that all system access controls and other security checks are functioning correctly. In other words, process A and process B _are_ obeying all of the individual security rules imposed by the system, but somehow process A manages to send, and process B to receive, information that the overall system security policy would not permit to be sent directly. (That's why its "surprising to the authorities" <1992Aug15.162611.24659@sctc.com> :-)
Technical Details
Message-ID:
<1992Aug19.223415.26941@dg-rtp.dg.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!psinntp!psinntp!dg-rtp!leonardo!meyersReferences:
<21378@rpp386.lonestar.org> <1992Aug17.175123.3793@hpcvusn.cv.hp.com> <21382@rpp386.lonestar.org>Show Full Headers
Complete Article Headers
Newsgroups: comp.security.misc Path: arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!psinntp!psinntp!dg-rtp!leonardo!meyers From: meyers@leonardo.rtp.dg.com (Bill Meyers) Subject: Re: Covert channel Message-ID: <1992Aug19.223415.26941@dg-rtp.dg.com> Sender: meyers@rtp.dg.com (Bill Meyers) Date: Wed, 19 Aug 92 22:34:15 GMT References: <21378@rpp386.lonestar.org> <1992Aug17.175123.3793@hpcvusn.cv.hp.com> <21382@rpp386.lonestar.org> Organization: Data General Corporation, RTP, NC. Lines: 16