Sponsored Content
Special Forums Cybersecurity How to know when you've been hacked Post 29209 by LivinFree on Tuesday 1st of October 2002 07:09:10 PM
Old 10-01-2002
A lot of security-folk will tell you to clone the drive, and peek at that. For official evidence sake, let the proper authorities have the original disk that you have not tampered with.

Also, this stuf must be planned out way in advace... you shouldn't be reactive in a security policy. Everyone should be involved, as frustrating as that is bound to be: Lawyers, Managers, Technicians, Operators - everyone has something to offer.

I recommend subscribing to Bugtraq if you have the time to read it all - also, the other lists hosted by Security Focus are great. You'll get a chance to see how people are cleaning these incidents up, and see where mistakes have been made.
 

3 More Discussions You Might Find Interesting

1. Linux

pc hacked

Hi, i think someone has hacked my server, the following rules used to come which i haven't put. Please help me i couldnt find out how this rules are apply, i think someone has put an script which generates enables the rules. But after restarting the iptables everything seems to be working... (0 Replies)
Discussion started by: naik_mit
0 Replies

2. Cybersecurity

Server hacked on known port

Hi, There is a recent case whereby it was reported that one of the production servers was hacked on port 1521. However, I am not sure how this was possible, as I checked that the OS firewall (iptables) is on : # /etc/init.d/iptables status Table: nat Chain PREROUTING (policy ACCEPT) num ... (7 Replies)
Discussion started by: anaigini45
7 Replies

3. Cybersecurity

Our system was hacked

Someone made a mistake, and left our router wide open, pointing all ports to a SCO 6.0.0 system. Within 24 hours, the following happened. The contents of all the files (except tar files) in three directories, one directory on each of three different file systems, were replaced with nulls. None... (3 Replies)
Discussion started by: jgt
3 Replies
diskseekd(1)						      General Commands Manual						      diskseekd(1)

Name
       diskseek, diskseekd - disk seek daemon; simulates Messy Dos' drive cleaning effect

Note
       This  manpage has been automatically generated from fdutils's texinfo documentation.  However, this process is only approximative, and some
       items, such as cross-references, footnotes and indices are lost in this translation process.  Indeed, these items have no appropriate  rep-
       resentation  in	the  manpage  format.  Moreover, only the items specific to each command have been translated, and the general information
       about fdutils has been dropped in the manpage version.  Thus I strongly advise you to use the original texinfo doc.

       *      To generate a printable copy from the texinfo doc, run the following commands:

		     ./configure; make dvi; dvips fdutils.dvi

       *      To generate a HTML copy,	run:

		     ./configure; make html

	      A pre-made HTML can be found at: `http://www.tux.org/pub/knaff/fdutils'

       *      To generate an info copy (browsable using emacs' info mode), run:

		     ./configure; make info

       The texinfo doc looks most pretty when printed or as HTML.  Indeed, in the info version certain examples are difficult to read due  to  the
       quoting conventions used in info.

Description
       Several	people	have  noticed that Linux has a bad tendency of killing floppy drives. These failures remained completely mysterious, until
       somebody noticed that they were due to huge layers of dust accumulating in the floppy drives. This cannot happen under Messy  Dos,  because
       this  excuse  for  an  operating system is so unstable that it crashes roughly every 20 minutes (actually less if you are running Windows).
       When rebooting, the BIOS seeks the drive, and by doing this, it shakes the dust out of the drive mechanism. diskseekd simulates this effect
       by seeking the drive periodically.  If it is called as diskseek, the drive is sought only once.

Options
       The syntax for diskseekd is as follows:

	  diskseekd [-d drive] [-i interval] [-p pidfile]

       -d drive
	      Selects the drive to seek.  By default, drive 0 (`/dev/fd0') is sought.

       -i interval
	      Selects the cleaning interval, in seconds.  If the interval is 0, a single seek is done. This is useful when calling diskseek from a
	      crontab.	The default is 1000 seconds (about 16 minutes) for diskseekd and 0 for diskseek.

       -p pidfile
	      Stores the process id of the diskseekd daemon into pidfile instead of the default `/var/run/diskseekd.pid'.

Bugs
       1.     Other aspects of Messy Dos' flakiness are not simulated.

       2.     This section lacks a few smileys.

See Also
       Fdutils' texinfo doc

fdutils-5.5							      03Mar05							      diskseekd(1)
All times are GMT -4. The time now is 08:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy