public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 2a747e37a86f44c5da8dbf67c4135772df29f24e
Date: Fri, 10 Jan 2014 16:20:24 +0100	[thread overview]
Message-ID: <20140110152025.435D020AEC@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, fifteen has been updated
       via  2a747e37a86f44c5da8dbf67c4135772df29f24e (commit)
      from  7514fe47f6b2caf5a1dfc80de3a539975b753b21 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 2a747e37a86f44c5da8dbf67c4135772df29f24e
Author: Kim Wölfel <xaver4all(a)gmx.de>
Date:   Fri Jan 10 16:19:43 2014 +0100

    guardian: React on BF attacks for SSH at pre-auth stage.
    
    See #10457.

-----------------------------------------------------------------------

Summary of changes:
 config/guardian/guardian.pl | 6 +++++-
 lfs/guardian                | 2 +-
 2 files changed, 6 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/config/guardian/guardian.pl b/config/guardian/guardian.pl
index 86d93fe..34546b7 100644
--- a/config/guardian/guardian.pl
+++ b/config/guardian/guardian.pl
@@ -106,6 +106,10 @@ for (;;) {
 					$temp = $array[11];
 				}
 				&checkssh ($temp, "possible SSH-Bruteforce Attack");}
+
+			# This should catch Bruteforce Attacks with enabled preauth
+			if ($_ =~ /.*sshd.*Received disconnect from (\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}):.*\[preauth\]/) {
+				&checkssh ($1, "possible SSH-Bruteforce Attack, failed preauth");}
 			}
 	}
 
@@ -424,4 +428,4 @@ sub get_aliases {
 	}
 
 	print "done \n";
-}
\ No newline at end of file
+}
diff --git a/lfs/guardian b/lfs/guardian
index fea50db..a91fbd9 100644
--- a/lfs/guardian
+++ b/lfs/guardian
@@ -30,7 +30,7 @@ THISAPP    = guardian-$(VER)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = guardian
-PAK_VER    = 8
+PAK_VER    = 9
 
 DEPS       = ""
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-01-10 15:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140110152025.435D020AEC@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox