Article View: net.bugs.v7
Article #122Re: Possible at(1) security breach?
From: wapd
Date: Wed, 01 Jun 1983 14:59
Date: Wed, 01 Jun 1983 14:59
15 lines
1131 bytes
1131 bytes
This is only one of many ways in which AT(1) can cause security breaches. Set up properly, AT is fully secure (at least on BTL systems running equivalents of System III and IV). However, there are many ways for administrators to make mistakes that cause a security breach. If the AT spool directory is writable, you can create dummy files owned by various users and anything can happen. If files in the directory are writable, you can change the commands in them and break security. If the directory above the spool directory is writable, you can remove the entire spool directory and make your own. And so on ... Bill Dietrich houxj!wapd
Technical Details
Message-ID:
<259@houxj.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!decvax!decwrl!leonard!beesvax!utah-cs!harpo!eagle!mhuxt!mhuxi!mhuxa!houxm!houxk!houxj!wapdReferences:
csu-cs.2230Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!decvax!decwrl!leonard!beesvax!utah-cs!harpo!eagle!mhuxt!mhuxi!mhuxa!houxm!houxk!houxj!wapd From: wapd@houxj.UUCP Newsgroups: net.bugs.v7 Subject: Re: Possible at(1) security breach? Message-ID: <259@houxj.UUCP> Date: Wed, 1-Jun-83 10:59:43 EDT Article-I.D.: houxj.259 Posted: Wed Jun 1 10:59:43 1983 Date-Received: Sat, 4-Jun-83 06:47:09 EDT References: csu-cs.2230 Lines: 15