You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(15) |
Jul
(1) |
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
2016 |
Jan
(10) |
Feb
|
Mar
|
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
(8) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2017 |
Jan
(6) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Kevin Z. <kev...@gm...> - 2015-10-12 23:47:06
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Greetings, It is my pleasure to announce the availability of the SSHGuard 1.6.2 release. This release backports a compatibility fix for the iptables backend and overhauls the ipfw backend. If you are not using either backend, you do not need to upgrade. If you are not currently experiencing issues with 'iptables', you do not need to upgrade. If you are running 'ipfw', you should definitely upgrad e. If you are running 'ipfw', you will need to make changes to your firewall configuration. SSHGuard will add addresses to table 22 (currently hard-coded in SSHGuard); you will need to write the firewall rule that uses the table to actually do something. This will most likely be the last release from the 1.6 branch. Developing in 'master' and backporting fixes for releases is too cumbersome at this point and prevents features from landing at a reasonable pace. Future releases will be cut from 'master', beginning with 1.7.0. I haven't figured out a version scheme, though. The source tarball, along with a GPG-signed checksum, is available from SourceForge. Only a XZ'ed tarball is available; if anyone still needs a gzip'ed tarball please let me know. As usual, please report issues on the Bitbucket tracker or mailing list. Best, Kevin Zheng - -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWHEZwAAoJEOrPD3bCLhCQLRsH/jyyRTP3aXaKjEvHbJvImS9f OEEKz4VZel4iHPxqMcpeA4/qnWs5lyQCdCWC+C0Nt+etScRDfSOQ4bf3lVE8z0rV jT0n1yGtnXDu8W2sVednMlwC+EonMHHZeH+bmVDFb9FWT165Pgy5FuxXiPfxsvVz TnogaqiH3EJgUBtRNDcTNUdl/zWo5Z9ae3ejDqSBtKLnxUbrlWiRbLTndizT7xeS pgwEG+FSFh6nss1WSdJMDzC9vQIZ0BnNPBV5GcJMfwoN0N0CeONstguWB0POVZhj 5eMuxIIFXsIUuRMjgt28nrKr3wUfOYv8pZxDWe3nB9cGZEk5LbLpgUS0ks14lKU= =ee63 -----END PGP SIGNATURE----- |
From: Willem J. W. <wj...@di...> - 2015-08-03 09:08:23
|
On 1-8-2015 03:07, Kevin Zheng wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Greetings, > > I am pleased to announce the release of SSHGuard 1.6.1 [1]. This > release is primarily a bugfix release that fixes a few late-breaking > issues from 1.6.0 while incorporating a few feature improvements. This > release was slightly delayed by a recent SourceForge outage. > > Changes in this release include: > > - - Accept "Received disconnect" with optional prefix > - - Add support for socklog entries > - - Fix 'ipfw-rules-range' option in configure script > - - Fix build for 'ipfw' and 'hosts' backends > - - Fix integer comparisons of different types > - - Match attacks when syslog debugging is enabled > > Many thanks to the contributors who reported issues or sent in patches > to fix them. Special thanks to the FreeBSD community for reporting and > fixing a number of problems amended in this release. > > As usual, please report any bugs, build failures, or other issues to > the mailing list or the Bitbucket tracker [2]. Hi, I added some code on FreeBSD to libssh to make some errors actually log the the ip-number, because this is usualy abuse as well.... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202055 And it changes the log like: fatal: Read from socket failed: Connection reset by peer [preauth] Which is rather useless for tools like sshguard and/or fail2ban But this patch changes this info to: Aug 2 19:37:32 zfs sshd[19444]: Read from socket failed: 218.2.22.36 [preauth] Aug 2 19:37:32 zfs sshd[19444]:fatal: Read from socket failed: Connection reset by peer [preauth] But then again this needs to be picked upt by sshguard with an extra parser rule... --WjW patch: Index: crypto/openssh/packet.c =================================================================== --- crypto/openssh/packet.c (revision 286222) +++ crypto/openssh/packet.c (working copy) @@ -1128,8 +1128,10 @@ logit("Connection closed by %.200s", get_remote_ipaddr()); cleanup_exit(255); } - if (len < 0) + if (len < 0) { + logit("Read from socket failed: %.200s", get_remote_ipaddr()); fatal("Read from socket failed: %.100s", strerror(errno)); + } /* Append it to the buffer. */ packet_process_incoming(buf, len); } |
From: Kevin Z. <kev...@gm...> - 2015-08-01 01:07:46
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Greetings, I am pleased to announce the release of SSHGuard 1.6.1 [1]. This release is primarily a bugfix release that fixes a few late-breaking issues from 1.6.0 while incorporating a few feature improvements. This release was slightly delayed by a recent SourceForge outage. Changes in this release include: - - Accept "Received disconnect" with optional prefix - - Add support for socklog entries - - Fix 'ipfw-rules-range' option in configure script - - Fix build for 'ipfw' and 'hosts' backends - - Fix integer comparisons of different types - - Match attacks when syslog debugging is enabled Many thanks to the contributors who reported issues or sent in patches to fix them. Special thanks to the FreeBSD community for reporting and fixing a number of problems amended in this release. As usual, please report any bugs, build failures, or other issues to the mailing list or the Bitbucket tracker [2]. Very best, Kevin Zheng [1] https://sourceforge.net/projects/sshguard/files/sshguard/1.6.1/ [2] https://bitbucket.org/sshguard/sshguard/issues/ - -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVvBvZAAoJEOrPD3bCLhCQmdMH/3g8gjEF67GUBX7VH+QpY2vQ W2UYCbIln5z4VytYHMyykNcqTMkZCpnPnuQV+14IVrIUSfQp5fY3vYKL7xcTT3PC canTMbuPsLPjdXsSFCtZjQetbuDrsGEDzXD82XV1ATHz41RknanSnq0GasRF7NZR GpLN7gukNHhtzoSSca7fC/W9AUo1Ya0s9avIbkamm5PKfZ+ZQW1C6UaXOOshpTLb 8FQ1sbG9PozyN6ohEA2VnEMvcD8EdJ4sBTNdEPpehSj/SzRSkMvaVeQdq9yhnuQV uC8q6aT76rhgu1CMMB/zxASND/mJyyDgWfkH0QxF+pRGR3SMehJENAkXesPZzgA= =HFiX -----END PGP SIGNATURE----- |
From: Kevin Z. <kev...@gm...> - 2015-05-26 21:48:22
|
This is an errata notice for SSHGuard. This issue impacts the 1.6.0 release, but has actually been around for quite some time. ## Problem ## When blocking attackers from a loaded blacklist file, SSHGuard will write past the boundaries of a fixed-length buffer. This problem only affects users running SSHGuard with blacklisting enabled, while using the `ipfw` backend. ## Impact ## SSHGuard will crash with a segmentation fault upon startup when loading a blacklist with enough (less than 100) entries. Because the blacklist file is generally owned by the superuser, it is unlikely that this vulnerability could be used to gain superuser privileges. If you are affected, please consider using one of the workarounds: ## Workaround ## Any one of these should work around the issue: 1. Don't use blacklisting. 2. Don't use the `ipfw` backend. 3. If you need blacklisting, delete the blacklist file before starting. ## Solution ## We're working on one. The "long-term" solution is to switch `ipfw` to the "command" backend and use ipfw tables instead of individual rules. For the time being: 1. Increase the length of the fixed buffer. Eventually, though, this will run into the same problem. 2. There is a patch on the mailing list that adds the blacklisted addresses one at a time. I haven't taken a look at it yet. ## Credits ## Thanks to Greg Putrich <gr...@n0...> for analyzing and proposing a fix to this issue. Thanks to the many people who have reported this issue beforehand, even though I never got around to acting on them. -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 |
From: Kevin Z. <kev...@gm...> - 2015-05-04 21:52:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 This is an errata notice for the SSHGuard 1.6.0 release: ## Problem ## SSHGuard supports one of several firewall backends; of these, the 'ipfw' and 'hosts' backends failed to build due to a missing header file after some code reorganization prior to the 1.6.0 release. There is no workaround available; however, users who are not using the 'ipfw' or 'hosts' backends are not affected. ## Solution ## Those who are affected should apply the attached patch against the 1.6.0 release tarball, or track the 1.6 branch on Bitbucket. ## Credits ## Thanks to Mark Felder <feld@FreeBSD.org> for reporting this issue. - -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVR+okAAoJEOrPD3bCLhCQlgQH+wUWoWLdBhzcppnc3CZ6eXol CA+5uHa0+cuYdouTjqW5tayGOO8JT6Ng7ydw5tML6CjtBDRJ8aWIHeJcUI9l4yA3 htAD+CxhxJ4l2rWy0Upz1kLb0ylGkNfk8tE56oSwYlLCYptVGeIMw3OQhPI8gnpb ZJt2YHpiS+Cf/qjhsmKQ6N9/8Tf7H8dZRXhUK5zhZ8LZ4ZQPJf2+1le3DMOy08P1 UjoQivl6Vh6m3ea3Cu9L3DLh2oqRfrh9ixYmkcPWIKKPO0Xnz1jPy8BF5NoTyGt2 KlsFKzbwKablGNOxUrEVaPEp48VP1heTVGsjHYfVK7CNp0yDtOvLBsvjAgWCORE= =/iDp -----END PGP SIGNATURE----- |
From: Mark F. <feld@FreeBSD.org> - 2015-05-04 17:38:10
|
On Sat, May 02, 2015 at 02:17:12PM -0500, Kevin Zheng wrote: > > Greetings, > > On behalf of the SSHGuard Team, it is my pleasure to announce the > 1.6.0 release. This release is the first in the 1.6 branch and comes > after more than four years of development. > Fails to build with Clang due to missing include statement hosts.c:47:15: error: use of undeclared identifier 'ADDRLEN' char addr[ADDRLEN]; ^ hosts.c:234:22: error: use of undeclared identifier 'ADDRKIND_IPv4' case ADDRKIND_IPv4: ^ hosts.c:238:22: error: use of undeclared identifier 'ADDRKIND_IPv6' case ADDRKIND_IPv6: ^ 3 errors generated. See attached. Thanks! |
From: Kevin Z. <kev...@gm...> - 2015-05-02 19:17:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Greetings, On behalf of the SSHGuard Team, it is my pleasure to announce the 1.6.0 release. This release is the first in the 1.6 branch and comes after more than four years of development. This release is tagged as 'v1.6.0' on Bitbucket [1] and source tarballs are available from SourceForge [2]. Tarballs are available in both `gzip` and `xz` formats. Checksums are signed with the same PGP key as this announcement (0xC22E1090). Notable changes in this release include: - - Add rules for Postfix SASL login attempts - - Add support for ISO 8601 timestamps (David Caldwell) - - Add support for external commands run on firewall events (-e) - - Blacklist file is now human-readable (Armando Miraglia) - - Check tcpwrapper file permissions regardless of local umask - - Detect additional pre-auth disconnects - - Fix ipfw crash when loading an empty blacklist (Jin Choi) - - Fix log parsing on days beginning with zero - - Fix log polling on filesystems with many files (Johann H. Hauschild) - - Fix matching for Cyrus IMAP login via SASL - - Fix syslog format detection on hosts with undefined hostname - - Match SSH login failures with "via" suffix - - Remove broken kqueue(2) support - - Tweak option names and help strings - - Update SSH "Bad protocol" signature - - Use case-insensitive "invalid user" signature - - Wait for xtables lock when using iptables command (James Harris) Please report any bugs, build failures, or OS-specific issues to the mailing list or to the Bitbucket tracker [3]. Cheers, Kevin Zheng [1] https://bitbucket.org/sshguard/sshguard/commits/tag/v1.6.0 [2] https://sourceforge.net/projects/sshguard/files/sshguard/1.6.0/ [3] https://bitbucket.org/sshguard/sshguard/issues/ - -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVRSK1AAoJEOrPD3bCLhCQvjAIANAD/Pfs3Etf2dwiztfsDUOo VLdReSUj8B1wdxo58joIDde7muhdnfmRnrx9dwFZ9FScrQCVoYJUuBKkwy9tRBAy hYjO/Zu6jmFaUvYmnAa2Z7accHTJZpnztd9vEsHK/xV9/4wLbnJi+biUoz0PY2AH 4YNNWh4EHbkOd4o/ZkDbmxf9MjXkmraPKSIFcklkyUydqbDI4QGodLZ0ZkvwoJPc fY0lJGd/FonlfJOFdHahTR6xKwrNZ5XeRq8RgpX5AKt71VfRd6XMmMma/8HS9wCq 8IJFZogpWPO27X7seCb3WEsBRoUWP+hY+NVIxCmkBPQezphG0wfz6j9S9b9hB24= =eBK+ -----END PGP SIGNATURE----- |
From: Kevin Z. <kev...@gm...> - 2015-04-25 17:45:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, It is my pleasure to announce the first release candidate for 1.6. This release candidate is expected to become the 1.6.0 release. This release candidate is tagged as 'v1.6-rc1' on Bitbucket [1] and source tarballs are available from SourceForge [2]. Tarballs are available in both `gzip` and `xz` formats. Checksums are signed with the same key as this announcement (0xC22E1090). For a list of user-visible changes, please see 'ChangeLog'. Please report any bugs, build failures, or OS-specific issues to the mailing list or to the Bitbucket tracker [3]. Unless critical issues are uncovered, expect the 1.6.0 release within a week. Thanks, Kevin Zheng [1] https://bitbucket.org/sshguard/sshguard/commits/tag/v1.6-rc1 [2] https://sourceforge.net/projects/sshguard/files/sshguard/1.6-rc1/ [3] https://bitbucket.org/sshguard/sshguard/issues/ - -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVO9KhAAoJEOrPD3bCLhCQu4gH/382KUIhPV6uooBlNNas/DgO mW4HPgQrodsP8+rCivtrz8AgOoPVhGgftMN9Lyp1pMsFhZMAm9z828LYG7hpd9uS vjr7Q74+y68veb/AhqKi2MLWmNcmQW2Spe0Q7HoLdlbx5ygeObrm1dr/ABLwCWnF 2znys8jX+i7iK5vmtLGzwhHhQQctoaPoHP5g7sDoggdZMv8FegkOKZFZCvJllNrE YsF3w6y2TYu17+dLXbs+jwJmUIA7UNqNNnr8vEAjJkPOQTjHnp88TNeYSZYObfNj DM+E2HGoAO+8NedOptwWOeot126jEf854gHYhiTVfhrHR04xyZEmKvbU+bOWto0= =o574 -----END PGP SIGNATURE----- |
From: Kevin Z. <kev...@gm...> - 2015-04-12 16:25:50
|
Hi all, It's been four years since the 1.5 release. Since then, there have been a series of bug fixes, improvements, and attack signature updates. In the coming few days I would like to tag the 1.6 branch in preparation for the 1.6.0 release. Until then, the 'master' branch on Bitbucket [1] reflects what will be in the next release. I encourage everyone, especially package maintainers, to clone or download a snapshot of the repository and give it a whirl. We've received a lot of patches and issue reports. These *are* being taken care of, albeit a little slowly. If there are patches or bugs that should really be fixed in 1.6.0, please feel free to submit them to the mailing list or the Bitbucket issue tracker [2]. As always, feedback is immensely appreciated. Please send mail to the users mailing list if you encounter crashes, bugs, or other issues. Thanks, Kevin Zheng [1] https://bitbucket.org/sshguard/sshguard/ [2] https://bitbucket.org/sshguard/sshguard/issues/ -- Kevin Zheng kev...@gm... | ke...@kd... | PGP: 0xC22E1090 |
From: Pinocchio <pin...@gm...> - 2013-04-07 17:39:32
|
Hello! I am use sshguard 1.5 about a year and it works with no hitch. Recently, however, I found sshguard crashing every time it started by syslog. Little investigation found that the reason is in it's database content. After I've removed it the problem was gone. Configuration details: [root@XXX /var/db/sshguard]# sshguard -v sshguard 1.5.0 Copyright (c) 2007,2008 Mij <mi...@ss...> This is free software; see the source for conditions on copying. [root@XXX /var/db/sshguard]# uname -a FreeBSD XXX 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 ro...@al...:/usr/obj/usr/src/sys/GENERIC i386 [root@cytadel /var/db/sshguard]# grep sshguard /etc/syslog.conf auth.info;authpriv.info |exec /usr/local/sbin/sshguard -b /var/db/sshguard/blacklist.db The flawed blacklist.db is attached. -- Best Regards |
From: Tobias M. <Tob...@tw...> - 2013-03-01 11:11:03
|
Hi! sshguard fails to parse log lines from metalog such as Mar 01 11:21:33 [sshd] Invalid user test from XXX.XXX.XXX.XXX when there is a leading 0 in the day of the month. The attached patch fixes this. Tobias |
From: Mij <mi...@ss...> - 2012-03-25 21:12:27
|
Hey Henry, I replied to your private e-mail yesterday. For patches, write to ssh...@li... . This list is for maintainers of packaged versions of sshguard. On Mar 25, 2012, at 1:30 , Henry Yen wrote: > Is this project still active? The maintainer-style posts date back over > five months. I have an enhancement suggestion or two, having written > some local patches recently. I also see that user questions/bugs haven't > been answered since then. > > -- > Henry Yen Aegis Information Systems, Inc. > Senior Systems Programmer Hicksville, New York > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Sshguard-maintainers mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-maintainers |
From: Henry Y. <henry@Aegis00.com> - 2012-03-25 00:52:34
|
Is this project still active? The maintainer-style posts date back over five months. I have an enhancement suggestion or two, having written some local patches recently. I also see that user questions/bugs haven't been answered since then. -- Henry Yen Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York |
From: hays <bil...@un...> - 2012-03-01 16:30:39
|
I'm trying to get sshguard working with valid users under OSX. At first I thought it was a signature issue, and perhaps it is, but I'm not conversant enough to figure it out. Here's a debug listing: tomthumb:sshguard hays$ env SSHGUARD_DEBUG=foo /usr/local/sbin/sshguard whitelist: add '127.0.0.1' as plain IPv4. whitelist: add plain IPv4 127.0.0.1. Started successfully [(a,p,s)=(40, 420, 1200)], now ready to scan. error: PAM: authentication error for hays from flutterby.cs.unc.edu via 2.3.4.5 Starting parse Entering state 0 Reading a token: --accepting rule at line 148 ("error: PAM: authentication error for hays from ") Next token is token SSH_LOGINERR_PAM () Shifting token SSH_LOGINERR_PAM () Entering state 9 Reading a token: --accepting rule at line 211 ("flutterby.cs.unc.edu") Next token is token HOSTADDR () Shifting token HOSTADDR () Entering state 52 Reducing stack by rule 25 (line 211): $1 = token HOSTADDR () Successfully resolved 'flutterby.cs.unc.edu' --> 4:'1.2.3.4'. -> $$ = nterm addr () Stack now 0 9 Entering state 56 Reducing stack by rule 34 (line 279): $1 = token SSH_LOGINERR_PAM () $2 = nterm addr () -> $$ = nterm ssh_authfail () Stack now 0 Entering state 32 Reducing stack by rule 27 (line 264): $1 = nterm ssh_authfail () -> $$ = nterm sshmsg () Stack now 0 Entering state 30 Reducing stack by rule 11 (line 169): $1 = nterm sshmsg () -> $$ = nterm msg_single () Stack now 0 Entering state 28 Reducing stack by rule 9 (line 163): $1 = nterm msg_single () -> $$ = nterm logmsg () Stack now 0 Entering state 27 Reducing stack by rule 4 (line 125): $1 = nterm logmsg () -> $$ = nterm text () Stack now 0 Entering state 23 Reading a token: --accepting rule at line 223 (" ") --accepting rule at line 222 ("via") Next token is token WORD () Error: popping nterm text () Stack now 0 Cleanup: discarding lookahead token WORD () Stack now 0 Not sure what Next token is token WORD () Error: popping nterm text () means, any ideas? tia, bil -- ________________________ bil hays Infrastructure Manager Computer Science, UNC CH http://www.cs.unc.edu/~hays/ |
From: Jing Lu <luj...@gm...> - 2011-07-25 10:38:50
|
Are you sure your IP number has not been added into the blacklist. Or you can check your iptable rules, and make sure your ip number has not been transformed. I suggest that you can check all your computer configure, which article have connection with sshguard. On Tue, Jul 19, 2011 at 5:28 AM, Shaun Courtney <sh...@co...>wrote: > Hello, > > I've noticed that I'm unable to ssh to some of my machines and on closer > inspection I find my IP number has been added from the project. I'm not sure > how this happened? Do you have any logs that can help me track down what > happened to get this listed? > > Regards, > > > Shaun > > > > ------------------------------------------------------------------------------ > Storage Efficiency Calculator > This modeling tool is based on patent-pending intellectual property that > has been used successfully in hundreds of IBM storage optimization engage- > ments, worldwide. Store less, Store more with what you own, Move data to > the right place. Try It Now! > http://www.accelacomm.com/jaw/sfnl/114/51427378/ > _______________________________________________ > Sshguard-maintainers mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-maintainers > |
From: Shaun C. <sh...@co...> - 2011-07-18 21:58:49
|
Hello, I've noticed that I'm unable to ssh to some of my machines and on closer inspection I find my IP number has been added from the project. I'm not sure how this happened? Do you have any logs that can help me track down what happened to get this listed? Regards, Shaun |
From: Mij <mi...@bi...> - 2009-07-13 14:45:03
|
Dear maintainers, You have noticed that sshguard has been augmented with major new features in the recent RC releases. To the best of our knowledge, sshguard is now the only log-based IPS not vulnerable to log spoofing from local users, nor most notably the infamous Denial Of Services from remote attackers ( http://www.ossec.net/en/attacking-loganalysis.html ). This is result of the fundamental design, and as for any tool based on a good infrastructure, features are blooming with faster pace once the framework is completed. SSHGuard 1.4 is coming in the next weeks and will be a significant leap from older versions. Among the news, blacklists are finally there after many requests, and "touchiness" gives sshguard much higher effectiveness in preventing brute forces by introducing more smartness with respect to the other tools. As we do not foresee code updates for the 1.4 stable release, we invite you to start preparing packages for sshguard-1.4rc5 as sshguard-1.4 . 1.4 should appear in few weeks from now, after the usual testing, as a rename of the 1.4rc5 package. As usual, the team is available for assistance. |
From: Mij <mi...@bi...> - 2009-02-18 23:28:29
|
Thanks for reporting. I removed the repos because the author didn't maintain it any longer. I will update the links. Btw, if there is anybody interested in taking over, of course the RPM package is a significant plus. On Feb 18, 2009, at 18:15 , Phusion wrote: > I checked http://sshguard.sourceforge.net/packages/, but the RPM's > weren't in there. Is there another place to find the RPMS for > sshguard? Let me know. > > Phusion > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San > Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise > -Strategies to boost innovation and cut costs with open source > participation > -Receive a $600 discount off the registration fee with the source > code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Sshguard-users mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-users |
From: Mij <mi...@bi...> - 2008-11-23 22:25:39
|
Hello Fernando, thanks for reporting this, I will try to reproduce this problem in the next days. Please file a bug here http://sourceforge.net/tracker/?group_id=188282&atid=924685 the maintainers mailing list is meant for packages, not development. michele On Nov 20, 2008, at 9:22 PM, Fernando Macedo wrote: > Hello, I have installed sshguard on FreeBSD. When it blocked a ipv6 > address on hosts.allow, it put a ipv6 with no []. After this, the > hosts.allow had no more worked. How to config it to works with ipv6? > > -- > Fernando Macedo > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > Sshguard-maintainers mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-maintainers |
From: Fernando M. <fdf...@in...> - 2008-11-20 20:22:54
|
Hello, I have installed sshguard on FreeBSD. When it blocked a ipv6 address on hosts.allow, it put a ipv6 with no []. After this, the hosts.allow had no more worked. How to config it to works with ipv6? -- Fernando Macedo |
From: Mij <mi...@bi...> - 2008-10-15 20:01:59
|
Hello maintainers, please update to 1.3. This version will be around for some time before an update. For which packages are currently outdated see http://sshguard.sourceforge.net/packages/ thanks for your persistent support. michele |
From: Ali P. <ha...@ge...> - 2008-08-31 10:15:20
|
Mij yazmış: > Dear folks, > > sshguard 1.1 is finally out. Please update your packages respectively. > <snip> > Please notify the mailing list when the package is ready, so that I > can update > http://sshguard.sourceforge.net/packages/ . > sshguard-1.1 is in portage. > thanks for your collaboration > michele > -- Regards, Ali Polatel |
From: Mij <mi...@bi...> - 2008-07-27 13:18:17
|
Dear folks, sshguard 1.1 is finally out. Please update your packages respectively. There are no news wrt 1.0 for what concerns the building system. Beware that with the new autotools versions man pages are now installed in DATAROOTDIR/man by default ($PREFIX/share/man instead of $PREFIX/man). You can use the --mandir argument to ./configure conveniently if you want to change this. Again, please take your decisions such that the user is required the least for setting up the tool, yet your package does not make too strict assumptions or too intrusive operations. Please notify the mailing list when the package is ready, so that I can update http://sshguard.sourceforge.net/packages/ . thanks for your collaboration michele |
From: Mij <mi...@bi...> - 2008-05-20 14:36:11
|
On May 2, 2008, at 04:52 , mantra UNIX wrote: > Hello Mij, > I have found some discrepancy in version v0.91, v1.0, v1.1-beta, the > way "sshguard" is blocking the offending ip's. I found the > consistent behaviour between the v0.91 and and v1.1-beat. But v1.0 > stable release seems to be not blocking address in a timely fashion. are you talking about the report about not considering attacks those with user names with 1 letter? > What is the time frame you are planning on release the stable > version of 1.1 ? Although the development has been idle for the former months, I do plan to commit the marginal modifications I had in mind for -stable. I think it should be ready in one or two months. mm > > > Thanks, > Tantra. > > > > > On 6/5/07, Mij <mi...@bi...> wrote: hello folks, > > sshguard 1.0 stable has been finally released, see > > http://sourceforge.net/forum/forum.php?forum_id=701923 > > There is a couple of relevant news for maintainers wrt 0.91: > 1) paths can now be set during ./configure > For example, iptables path, or the path of /etc/hosts.allow file. > These are autodetected via $PATH if they're not specified manually. > If the package compiles on the user host, mind that some systems > exclude sbin from users PATH, so specifing the path manually is safer. > > 2) there is now a man page to install (man/sshguard.8) > It is installed automatically during make install > > 3) there is an example file for whitelisting in exmples/ > whitelistfile.example. > Depending on the policy of the system, decide whether (and where) > to copy this example file into the system. > > 4) a thorough setup guide covering all the setup combos is available > at > http://sshguard.sourceforge.net/doc/setup/setup.html > Unless your package makes the software "up and running" (which is > preferred, when possible), I recommend to show it off as feedback > after > a successful installation. > > I remind to use the syslog+sshguard or syslog-ng+sshguard whenever > possible; avoid the tail+sshguard combo which is just a working hack. > > > > Last but not least, there is a new "policy" for maintainerships: > - I have freed slots on http://sshguard.sourceforge.net/doc/ > sshguardpackages.html > for sshguard 1.0 > - if you intend to build a package for an OS, please send a message > to the > sshguard-maintainers ml containing: > - the target OS or OSes > - the URL of the package, or the package content itself if > you want > mirroring > - possibly a brief TXT or HTML file with notes for users to > install > the package if it's not > trivial on default setups (for example on unofficial APT > sources, or > gentoo sunrise etc). > If what you need to say is already explained somewhere else, > feel > free to redirect there. > I will publish your file on the website for better user > feedback. > > > Your help is appreciated, thanks > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Sshguard-maintainers mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-maintainers > > > > -- > Regards, > mantra - Instrument of Thought > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________ > Sshguard-maintainers mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-maintainers |
From: Mij <mi...@bi...> - 2008-05-06 10:03:20
|
hello, It's months that I say I should made the two or three mods and finally release it but I have hard time finding time to do it. Still, feedback is always welcome. what do you mean with "not blocking in a timely fashion"? There is one version that doesn't consider trials with usernames with one letter only (which may mean that more than 4 attacks are issued before blocking). Besides this, I'm not aware of other problems. michele On May 5, 2008, at 17:09 , mantra UNIX wrote: > Hello Mij, > I have found some discrepancy in version v0.91, v1.0, v1.1-beta, the > way "sshguard" is blocking the offending ip's. I found the > consistent behavior between the v0.91 and and v1.1-beat. But v1.0 > stable release seems to be not blocking address in a timely fashion. > > What is the time frame you are planning on release the stable > version of 1.1 ? > > > Thanks, > Tantra. > > > -- > Regards, > mantra - Instrument of Thought > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________ > Sshguard-maintainers mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-maintainers |