SSHD config in Suse Post: 302618517

Sponsored Content

Top Forums UNIX for Advanced & Expert Users SSHD config in Suse Post 302618517 by hedkandi on Wednesday 4th of April 2012 05:41:21 AM

04-04-2012

Registered User

I agree with you, because already IP addresses are captured and I hate to mess up something I don't know how to fix later. But if I were to do it, how do i go by it? My sshd setting in syslog-ng.conf.in is as such:

Code:

# SSH Filters
filter f_sshderr    { match('^sshd\[[0-9]+\]: error:'); };
filter f_sshd       { match('^sshd\[[0-9]+\]:'); };

# SSH Logging
destination sshderr { file("/var/log/sshd/sshderr.log"); };
log { source(src); filter(f_sshderr); destination(sshderr); flags(final); };

destination sshd { file("/var/log/sshd/sshd.log"); };
log { source(src); filter(f_sshd); destination(sshd); flags(final); };

hedkandi

View Public Profile for hedkandi

Find all posts by hedkandi

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

1st install Suse, network config set up

Hello, I'm a newbie to unix. I just about have the Suse 10.1 installed. During set up it automatically detected components to access the internet. But failed. I lost now. Any ideas? Thank You

2. AIX

It helps in the sshd on sshd.log

Friends, I made the installation of the ssh in the it conspires, I configured in the ssh_config the following parameters.. SyslogFacility AUTH LogLevel INFO that should generate sshd.log in the /var/log.... more no this generating. Somebody could help myself in...

LEARN ABOUT OSF1

log

log(8)							      System Manager's Manual							    log(8)

NAME

       log - Records input and output from a program

SYNOPSIS

       /usr/sbin/log <logfile> <command>

OPERANDS

       The file in which to record the interaction being logged.  The command to execute.

DESCRIPTION

       The  log  program  runs <command> and logs the input to and output from <command> to the <logfile> file.  Input and output are logged until
       <command> exits, the log program exits, and the exit status of <command> is returned.

       The log program is used by the system  installation  procedure  and  the  it(8)	command  to  create  the  /var/adm/smlogs/install.log  and
       /var/adm/smlogs/it.log installation log files.

RESTRICTIONS

       Because	the  log  program is used in the installation standalone environment, program size was the greatest concern in its implementation.
       The log program does not search for the PATH variable to locate <command> and error messages are terse.

       The log program causes <command> to take standard input from and write standard output and standard error to  UNIX  pipes.   Some  commands
       will  not  be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead.  UNIX shells will
       not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells).  For example, log
       foo.tmp /sbin/sh -i

       In the previous example, foo.tmp is the name of <logfile>.

       The  log  program  intercepts  end-of-file (usually Ctrl/d).  Therefore programs which normally receive end-of-file as an exit command must
       exit by some other means.

ERRORS

       Log open error

   Explanation:
       The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.

       Exec Error

   Explanation:
       The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and  that  <command>  is  an  exe-
       cutable file.

       Fork Error

   Explanation:
       The log program was unable to create one of the processes it requires to log data.

SEE ALSO

       Commands: it(8), script(1)

																	    log(8)