Article View: comp.unix.programmer
Article #261logging outgoing telnet sessions to catch 'hackers'
From: Swift
Date: Mon, 06 Apr 1992 23:38
Date: Mon, 06 Apr 1992 23:38
18 lines
1478 bytes
1478 bytes
We're running Dynix on a Sequent S81 and are considering methods of logging outgoing telnet sessions. We can log which sites connect to ours (by putting tcp_wrapper between inetd and the server daemons), but we're trying to determine the best way to log users connections to other hosts. Frequently, another site might report incidences of possible hacking from our site and we'd like to know who's doing it. Some options I've considered: 0. Modifying the kernel. Not possible without the source. 1. Modifying telnet to log sessions. This can be easily circumvented by getting the source and recompiling though. 2. Monitoring output from 'netstat' and 'who'. This seems 'kludgy.' 3. Peeking into the kernel. I have very little experience with this and am not sure what method to use. I have heard of mmap(), but the manual pages are insufficient. Does anyone have an example or a reference? Thanks in advance, Lin
Technical Details
Message-ID:
<2769@copper.Denver.Colorado.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!mnemosyne.cs.du.edu!mercury.cair.du.edu!copper!l1ngoReferences:
<1992Mar31.172400.10104@cs.rose-hulman.edu> <1992Apr1.013724.7335@kurango.cit.gu.edu.au> <1992Apr1.074513.3358@fwi.uva.nl>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!mnemosyne.cs.du.edu!mercury.cair.du.edu!copper!l1ngo From: l1ngo@copper.denver.colorado.edu (Swift) Newsgroups: comp.unix.programmer,comp.unix.admin Subject: logging outgoing telnet sessions to catch 'hackers' Message-ID: <2769@copper.Denver.Colorado.EDU> Date: 6 Apr 92 23:38:14 GMT References: <1992Mar31.172400.10104@cs.rose-hulman.edu> <1992Apr1.013724.7335@kurango.cit.gu.edu.au> <1992Apr1.074513.3358@fwi.uva.nl> Followup-To: comp.unix.programmer Organization: University of Colorado at Denver Lines: 18