search for: unban

...er, because I'm still banned. I seemed to be Emmett's favorite person to pick on. He told me to "eat a bag of dick" in his Ogg internet radio station thing, and generally ruined my reputation as a self-respecting programmer in #vorbis. Blah...anyway. Is there any way I can get unbanned? --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages...

man_in_shack banned me during a casual conversation where i was explaining my dual x server wine setup, saying I was contradicting myself. I obviously wasn't trying to contradict myself, if I did, and I don't see how this is ban-worthy under any circumstance.

...[dovecot] Ban 45.227.253.99 2019-04-19 13:06:32,954 fail2ban.filter [21954]: INFO [dovecot] Found 45.227.253.99 2019-04-19 13:06:36,664 fail2ban.filter [21954]: INFO [dovecot] Found 185.222.209.71 2019-04-19 13:07:16,973 fail2ban.actions [21954]: NOTICE [dovecot] Unban 185.211.245.198 2019-04-19 13:07:42,108 fail2ban.actions [21954]: NOTICE [dovecot] Unban 185.234.217.221 2019-04-19 13:08:06,475 fail2ban.filter [21954]: INFO [dovecot] Found 141.98.80.32 2019-04-19 13:08:11,299 fail2ban.filter [21954]: INFO [dovecot] Found 185.234....

...> 2019-04-19 13:06:32,954 fail2ban.filter [21954]: INFO [dovecot] > Found 45.227.253.99 > 2019-04-19 13:06:36,664 fail2ban.filter [21954]: INFO [dovecot] > Found 185.222.209.71 > 2019-04-19 13:07:16,973 fail2ban.actions [21954]: NOTICE [dovecot] > Unban 185.211.245.198 > 2019-04-19 13:07:42,108 fail2ban.actions [21954]: NOTICE [dovecot] > Unban 185.234.217.221 > 2019-04-19 13:08:06,475 fail2ban.filter [21954]: INFO [dovecot] > Found 141.98.80.32 > 2019-04-19 13:08:11,299 fail2ban.filter [21954]: INFO...

...er riding its fail2ban.log. took a while, but I use /var/log/fail2ban now, that finally worked through logrotates and logwatch. Problem with centos variant of fail2ban: logrotate causes all 'ban' actions to stop happening. I am pretty sure it stops reading the logs but still functions. Unban actions still keep showing up in the log, but the 'ban' actions just stop. Program is running, but no longer working. Long searches online show a million others with the same issue. Only way to prevent it seems to be to add a reload or restart in the syslog file. This is undesired due t...

...:32,954 fail2ban.filter [21954]: INFO > > [dovecot] Found 45.227.253.99 > > 2019-04-19 13:06:36,664 fail2ban.filter [21954]: INFO > > [dovecot] Found 185.222.209.71 > > 2019-04-19 13:07:16,973 fail2ban.actions [21954]: NOTICE > > [dovecot] Unban 185.211.245.198 > > 2019-04-19 13:07:42,108 fail2ban.actions [21954]: NOTICE > > [dovecot] Unban 185.234.217.221 > > 2019-04-19 13:08:06,475 fail2ban.filter [21954]: INFO > > [dovecot] Found 141.98.80.32 > > 2019-04-19 13:08:11,299 fail2ban.filter...

...the iptables rules to see > what is actually being applied. Hi Pete, I did wonder that myself. I have now amended to Dovecot definition in jail.conf to: [dovecot] port = pop3,pop3s,imap,imaps,submission,sieve,25,1025,465,587 logpath = %(dovecot_log)s backend = %(dovecot_backend)s I then unbanned and banned each IP address manually with for F in 46.232.112.21 106.226.231.159 [snip] 52.38.234.254 ; do fail2ban-client set dovecot unbanip $F fail2ban-client set dovecot banip $F done which worked. However, having done this, the connections are still getting through to EXIM. [root at olli...

...253.99 >2019-04-19 13:06:32,954 fail2ban.filter [21954]: INFO [dovecot] >Found 45.227.253.99 >2019-04-19 13:06:36,664 fail2ban.filter [21954]: INFO [dovecot] >Found 185.222.209.71 >2019-04-19 13:07:16,973 fail2ban.actions [21954]: NOTICE [dovecot] >Unban 185.211.245.198 >2019-04-19 13:07:42,108 fail2ban.actions [21954]: NOTICE [dovecot] >Unban 185.234.217.221 >2019-04-19 13:08:06,475 fail2ban.filter [21954]: INFO [dovecot] >Found 141.98.80.32 >2019-04-19 13:08:11,299 fail2ban.filter [21954]: INFO [dove...

On Sat, Aug 03, 2019 at 04:50:05PM +0100, Giles Coochey wrote: > > On 02/08/2019 19:38, Jon LaBadie wrote: > > On Fri, Aug 02, 2019 at 10:19:49AM -0400, mark wrote: > > > Fred Smith wrote: > > > > On Fri, Aug 02, 2019 at 09:28:23AM -0400, mark wrote: > > > <MVNCH> > > I've been using fail2ban for some time, I have a number of ports open

> > I did wonder that myself. I have now amended to Dovecot definition in jail.conf to: > > [dovecot] > > port = pop3,pop3s,imap,imaps,submission,sieve,25,1025,465,587 > logpath = %(dovecot_log)s > backend = %(dovecot_backend)s > > I then unbanned and banned each IP address manually with Did you reload the configuration? ("fail2ban-client reload") What action are you using - you mention ipset, are you using iptables- ipset-proto4? I don't know anything about ipset, but can you see what ports are being blocked in the fail2...

...of fail2ban. After the > second 10min ban, the attacker is blocked for 1 week. > Interesting, didn't know about that feature, but, oh, I just generally ban for a whole week regardless, yes, I realise that a typo might? set it off for a actual user, but I have other methods of entry to unban if that happens, and we have a number of whitelisted IPs that cover most things like that for most use cases, and a VPN within the whitelist that can be used if the public services get locked out.

...aemons (nmbd, smbd and winbind) and kills itself, node 1 claims : ctdb_recovery_lock: Failed to get recovery lock on '/ctdb/.ctdb.lock' (This directory is clvm + gfs2 shared, writable and correctly accessible from both nodes) This leads node 1 to get banned. Then, (I guess), when being unbanned, reelection occurs, but I get : Recmaster node 1 no longer available. Force reelection I suppose that node 1 can't become recmaster as it can not get the recovery lock. But there's no way I see why this node claims it can take this lock. I don't know if this may help, but : - I...

Hello folks, Recently more and more messages are being killed by xiph.org's postfix anti-spam filter, followed by pleading messages from the author to 'unban' them :-) There's no banning on the group, but the anti-spam filter doesn't take prisoners. Remember these tips: Mail in HTML format is unceremoniously dropped on the floor. You will not be informed it has been dropped, and I will not be informed it was dropped. This alone eliminate...

Hello folks, Recently more and more messages are being killed by xiph.org's postfix anti-spam filter, followed by pleading messages from the author to 'unban' them :-) There's no banning on the group, but the anti-spam filter doesn't take prisoners. Remember these tips: Mail in HTML format is unceremoniously dropped on the floor. You will not be informed it has been dropped, and I will not be informed it was dropped. This alone eliminate...

...uns as root via sudo. * "ctdb delip" no longer fails if it is unable to move the IP. * A race in the ctdb tool's ipreallocate code was fixed. This fixes potential bugs in the "disable", "enable", "stop", "continue", "ban", "unban", "ipreallocate" and "sync" commands. * The monitor cancellation code could sometimes hang indefinitely. This could cause "ctdb stop" and "ctdb shutdown" to fail. Important internal changes -------------------------- * The socket I/O handling has be...

...(1) for details. * "ctdb rebalancenode" is now a debugging command and should not be used in normal operation. See ctdb(1) for details. * "ctdb ban 0" is now invalid. This was documented as causing a permanent ban. However, this was not implemented and caused an "unban" instead. To avoid confusion, 0 is now an invalid ban duration. To administratively "ban" a node use "ctdb stop" instead. * The systemd configuration now puts the PID file in /run/ctdb (rather than /run/ctdbd) for consistency with the initscript and other uses of...

...of the illegitimate sites that were coming from the UCE's I had blocked. It is quite interesting to watch this process. More interesting that no matter how strict or lax I make the system there will be the same number of attempted mails sent to my server. (give or take a few hundred). If I unban all the ips, which I did once, there was a one day bump up, then it leveled off to the same amount of individual attemtps (not counting the same attempt being tried again). I have 35,000 ips blocked right now and nothing changed...except yahoo spam. Spamassassin I use, but only for level 10 or m...

...Option: actionban # Notes.: command executed when banning an IP. Take care that the # command is executed with Fail2Ban user rights. # Tags: See jail.conf(5) man page # Values: CMD # actionban = iptables -I fail2ban-<name> 1 -s <ip> -j <blocktype> # Option: actionunban # Notes.: command executed when unbanning an IP. Take care that the # command is executed with Fail2Ban user rights. # Tags: See jail.conf(5) man page # Values: CMD # actionunban = iptables -D fail2ban-<name> -s <ip> -j <blocktype> [Init] # Default name of the chai...

Hello, I'm looking for some advice on securing Asterisk. Recently my servers been under several brute-force SIP attacks. I have several remote sites, as well as many roaming users, who may have PC softclients and/or SIP based hardphones. My first step will be to strengthen the passwords in use, and for the hardphones to restrict by IP address, but that still leaves the softphone