search for: watchlist

...at -F /sbin/iptables -t nat -X /sbin/iptables -t nat -Z /sbin/iptables -t nat -P PREROUTING ACCEPT /sbin/iptables -t nat -P OUTPUT ACCEPT /sbin/iptables -t nat -P POSTROUTING ACCEPT if cat /proc/net/ip_tables_matches | grep "recent" &>/dev/null ; then # if anybody from the list WATCHLIST, and in the last 20 sec, tries to do new connect attempts then DROP them! /sbin/iptables -A INPUT --match recent --name WATCHLIST --rcheck --seconds 20 -j DROP # accept client at port tcp:22 and register in WATCHLIST /sbin/iptables -A INPUT -p tcp --dport 22 --match recent --name WATCHLIST -...

...|INVALID ------- Comment #1 from kernel at linuxace.com 2008-11-25 16:26 ------- > # BUG: if "-p tcp" is left out or if instead "-p all" is used then the rule gets eliminated! > /sbin/iptables -A INPUT -p tcp --dport 139 --match recent --name WATCHLIST --set -j DROP Yes, because that is an invalid rule without "-p tcp", since you are including "--dport 139". Please ask your question about this on the netfilter user mailing list, as there is nothing wrong with iptables here, only your rules. -- Configure bugmail: http://...

Am 26.08.2016 um 18:43 schrieb Rowland Penny via samba: > What shouldn't have happened was somebody massively changing a > wiki page without changing the header, this way lies confusion. I haven't seen this. I don't have this page on my watchlist. Usually I have a short look what people changed on the pages I have on my watchlist. Regards, Marc

I noticed that the changelog for the new kernel 2.6.9-34 on the redhat enterprise watchlist states on of the fixes as; 145061 - SMART support in SATA driver (P1) Does this mean that with that kernel we should be able to interrogate SATA drives now ? Cheers, Bards.

On 2016-08-26 10:59, Rowland Penny via samba wrote: > On Thu, 25 Aug 2016 06:08:16 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> On the "Bidirectional Rsync/Unison based SysVol replication >> workaround" page. The title (as you can see) includes the word UNISON >> when in fact the "Unison" program is NOT being

...6: option barrier-timeout 120 > 107: subvolumes digitalcorpora-marker > 108: end-volume > 109: > 110: volume digitalcorpora-index > 111: type features/index > 112: option index-base /export/brick7/digitalcorpora/.glusterfs/indices > 113: option xattrop-dirty-watchlist trusted.afr.dirty > 114: option xattrop-pending-watchlist trusted.afr.digitalcorpora- > 115: subvolumes digitalcorpora-barrier > 116: end-volume > 117: > 118: volume digitalcorpora-quota > 119: type features/quota > 120: option volume-uuid digitalcorpora > 12...

I''m trying to make sure a specific user has a special ssh key used as his identity file. so I''m trying something like: augeas{"user_second_key": context => "/files/home/user/.ssh/config", changes => [ "ins IdentityFile after /files/home/user/.ssh/config/IdentityFile[last()]", " set

...> 107: subvolumes digitalcorpora-marker >> 108: end-volume >> 109: >> 110: volume digitalcorpora-index >> 111: type features/index >> 112: option index-base /export/brick7/digitalcorpora/ >> .glusterfs/indices >> 113: option xattrop-dirty-watchlist trusted.afr.dirty >> 114: option xattrop-pending-watchlist trusted.afr.digitalcorpora- >> 115: subvolumes digitalcorpora-barrier >> 116: end-volume >> 117: >> 118: volume digitalcorpora-quota >> 119: type features/quota >> 120: option volume...

CVSup is slow, insecure, and a memory hog. However, until now it's been the only option for keeping an up-to-date ports tree, and (thanks to all of the recent work on vuxml and portaudit) it has become quite obvious that keeping an up-to-date ports tree is very important. To provide a secure, lightweight, and fast alternative to CVSup, I've written portsnap. As the name suggests, this

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what

hello, I want to protect the history file from deleted for all users except user 'root' can do it, is that possible? For my server, many users can log in with root from remote through ssh, so I can not trace which guy do wrong things. So I decide to create new account for every users and let them use 'sudo' then I can trace which guy typed which command and what he

I currently have a dedicated server at ev1servers, but it''s getting rather antiquated (Redhat 9) and am looking to upgrade. I''m thinking about serverbeach.com - one of their CentOS servers. Anybody have any recommendations for dedicated servers on which to run Rails? Hopefully less than $200/month. Thanks! CSN __________________________________________________ Do You Yahoo!?