Sponsored Content
Full Discussion: Our system was hacked
Special Forums Cybersecurity Our system was hacked Post 303037153 by Neo on Wednesday 24th of July 2019 10:51:59 PM
Old 07-24-2019
Turn on logging including router logging and closely monitor the logs.

Create a honeypot to lure the hackers into your logging traps, if you are interested to discover who is responsible.

Good job on keeping your backups up to date!
This User Gave Thanks to Neo For This Post:
 

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

How to know when you've been hacked

One of the most important ways to keep tou machine secure is to know when it has been broken into. The less time hackers have on your system, the less they can do to it, and the greater you chancens of kicking them off and repairing the damage. The more sophisticated the hacker, the less likely... (8 Replies)
Discussion started by: binhnx2000
8 Replies

3. 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
eli(8)							      System Manager's Manual							    eli(8)

Name
       eli - error log initialization program

Syntax
       eli [ options ]

Description
       The command initializes error logging.  This command enables error logging of hardware and system-related error packets, or error messages,
       from the kernel errorlog buffer.  It can also disable error logging, reconfigure error logging parameters, or initialize the kernel  error-
       log buffer.

Options
       -d     Disables error logging.

       -e     Enables error logging in multiuser mode.

       -f     Forces the subsequent option; the system will not prompt.  This is the only command option you can use with another option.

       -h     Prints information about the command.

       -i     Initializes the kernel errorlog buffer.  The previous contents of the errorlog buffer are lost.

       -l     Logs a one-line status message to the kernel errorlog buffer.

       -n     Only supported for local error logging.  Disables logging error packets to disk by the daemon. High priority error messages continue
	      to be printed at the console.  Note that error log packets can be viewed by using the option in real time, but are never written	to
	      the disk.  For this reason, this option is rarely used.

       -q     Suppresses the periodic display, on the console, of the missed error message that results from a full kernel errorlog buffer.

       -r     Reconfigures error logging.  Use this option after changing the file.

       -s     Enables error logging in single-user mode.

       -w     Enables the missed error message to appear on the console every 15 minutes.  This option is the opposite of

Examples
       This example logs a one-line message into the errorlog file.
       eli -f -l "This is a test message"
       This example logs a message, up to and including the first new line, from the file
       eli -f -l < myfile > /dev/null

Restrictions
       You must have superuser privileges to use the command.

       Only the -f option can be used with other options.  You must use the syntax shown in the examples above.

Diagnostics
       eli: Request Aborted.
       The requested action was aborted.  The reason for the aborted command is included with the output.

Files
See Also
       elcsd.conf(5), elcsd(8), uerf(8)
       Guide to the Error Logger

																	    eli(8)
All times are GMT -4. The time now is 01:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy