similar to: Dfs and Mangle=hash

Displaying 20 results from an estimated 400 matches similar to: "Dfs and Mangle=hash"

2003 Jan 08
2
OPENSSH REMOTE ROOT COMPROMISE ALL VERSIONS (fwd)
There has not been any mention of this, so.. I'm having hard time trying to figure out whether this is for real or just a joke. (Anyway, I don't use those possibly vulnerable features myself.) Any analysis yet? -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R.
1998 Aug 21
1
Named Overlow Concern
I am running Linux 2.0.30 (Redhat 4.2) and have recently been hacked. I have tightened up security but still feel vulnerable. In running the program mscan which was kindly left on my system I get this. bullnet.co.uk: VULN: linux box vulnerable to named overflow. 194.242.135.145: VULN: redhat linux box running imapd. This is after upgrading to the versions as below. bind-4_9_7-0
2008 Dec 18
2
Contextstack overlow
All - I have a number of rows that I am assigning length classes to via l.class<-with(wae, ifelse((Length>=120)&(Length<130),"125", ifelse((Length>=130)&(Length<140),"135", ifelse((Length>=140)&(Length<150),"145", ifelse((Length>=150)&(Length<160),"155",
2006 Mar 30
1
Rails mangle my ''class''?
Did rails due this to the final output of my document. I had a div that had a style: <div style="color: #FFF; background-color: #537677l; "> fsfs </div> This was the final output? <div style="color: rgb(255, 255, 255);"> fsfs </div> -- Berlin Brown (ramaza3 on freenode) http://www.newspiritcompany.com also checkout alpha version of botverse:
2006 May 05
0
iptables time match mangle stage
Hi I am having problems trying to get a time match with iptables 1.3.5 and the latest pom it says time match only works in the prerouting stage but I really need to use the classify command which only works in the postrouting. Does any one have a patch for 2.6 kernel, latest pom and iptables 1.3.5 so time matching can occur in the post routing? machinenemae login: ipt_time loading ipt_time:
2006 May 07
1
time matching in the mangle stage?? is it possible??
Hi I am having problems trying to get a time match with iptables 1.3.5 and the latest pom it says time match only works in the prerouting stage but I really need to use the classify command which only works in the postrouting. Does any one have a patch for 2.6 kernel, latest pom and iptables 1.3.5 so time matching can occur in the post routing? machinenemae login: ipt_time loading ipt_time:
2006 Feb 06
0
ip rule, fwmark, mangle and src IP
I made a script to test if in a moultiple gateway setup all default connection are up, regardless of the fact that that gateway is the default gw. Suppose adsl1 and adsl2 are present, and all traffic goes by default to adsl1, and you want to test if adsl2 is ok. 1. I use mangles from iptables to mark icmp packets to some test machines 2. I set up a routing table for each adsl 3. I use
2005 Jul 06
0
More on conntrack + NAT + mangle/nat tables
I already understood that a packet enters chains in the ''nat'' table only if it is the _first_ packet of a connection. In that case, we may do SNAT in the POSTROUTING chain of the ''nat'' table. So, the packets arrive to the POSTROUTING chain of the ''mangle'' table with the source IP address changed (if it''s said by the rules of the
2012 May 08
1
kernel: ip_tables: MARK target: only valid in mangle table, not filter
When Shorewall refreshes the config I get following in the log.. kernel: ip_tables: MARK target: only valid in mangle table, not filter logger: Shorewall refreshed Is that something I should worry about? Thanks P.S.  shorewall version 4.5.0.2 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the
2004 May 17
0
strange dos directory names - mangle?
hi list! first, excuse my bad english! ;-) second, i've installed samba 3.0.4 on redhat 9.0 and have a problem with dos directory names. under samba 2.2.X i've created an directory like e.g: yyyyxxxxz under windows/linux. to my dos clients this directory was showed as e.g: YYYYXX~1 under dos. this was ok and very good. since i've updated the samba version to 3.0.4 i've the
2003 Jan 27
0
[Bug 15] ip6tables mangle needs 'route_me_harder' equivalent
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=15 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching
2003 Mar 04
0
[Bug 15] ip6tables mangle needs 'route_me_harder' equivalent
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=15 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Additional Comments From
2011 Feb 09
0
[LLVMdev] Why do we mangle names in llvm?
When we produce IL for int f(void) {...} it looks like define i32 @f() {.... and llvm is then responsible for adding the '_' prefix: _f: .... Why do we have this division? Wouldn't it be better for the IL to have the '_': define i32 @_f() {.... This causes problems with LTO because the symbols seem by the first pass are not the same as the ones seen once the final .o
2003 Sep 11
1
mangle characters (e.g. blank to underline)
Hi File names with blanks are not very useful in Unix scripts. Our Windows users use very often (not allowed) blanks in file names. So I am looking for a possibility to change blanks to underlines. But mangled map = (*\ * *_*) does not work ?!? Best regards Horst Liesinger CAD Coordination (IT) Doppelmayr Seilbahnen GmbH
2007 Sep 04
1
Removing mangle map parameter.
Hi all, I'm planning to remove the "mangled map" parameter as part of the removal of pstrings/fstrings from the 3.2 codebase. For those of you without long memories :-) the "mangled map" code was designed for the days when most clients were DOS 8.3 aware, and we wanted to map names like *.html -> *.htm before mangling them into 8.3 format. The code is still there,
2006 Feb 06
1
[Bug 442] New: skb->data_len corrupted in NF_IP_LOCAL_OUT in mangle table
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=442 Summary: skb->data_len corrupted in NF_IP_LOCAL_OUT in mangle table Product: netfilter/iptables Version: linux-2.6.x Platform: i386 OS/Version: Debian GNU/Linux Status: NEW Severity: major Priority: P2 Component: ip_tables
2005 Jan 06
0
iproute with iptables/mangle
Hi List, i have a realy strange problem with no solution yet, i''m using iproute together with the iptables mangle option, in a dmz network is a cisco pix present with another inet link behind, therefore i''m using the mangle option to split traffic on a protocol base like: iptables -A PREROUTING -t mangle -i eth1 -s 192.168.1.5 -p tcp --dport 80 -j MARK --set-mark 3 and add the
2006 Apr 11
1
strange iptables mangle problem
Hi all, I manage network with two connections with l00Mbit In the past when network wasn''t so load everything was OK, now in pick hours load over border server from 1.0 to 1.5 / it isn''t so big / and for me is very strange why I have increasing of ping timeout from 0.5- 5ms in normal hour to 50-100 ms in pick hours.. server is with good hardware AMD 64 Dualcore
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
Looks to me like it converted the ? into the ascii hexadecimal representation _3F_. I don't think another underscore was pre-pended. This is probably thanks to lib/Target/Mangler.cpp. You'll want to let ? be treated as an acceptable character. static bool isAcceptableChar(char C, bool AllowPeriod) { if ((C < 'a' || C > 'z') && (C < 'A'
2006 Feb 07
4
[Bug 442] skb->data_len corrupted in NF_IP_LOCAL_OUT in mangle table
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=442 ------- Additional Comments From tpaskett@cymphonix.com 2006-02-07 23:19 MET ------- (In reply to comment #0) > I have confirmed this does not happen in 2.6.13.5 and below and starts to happen > in 2.6.14 all the way to 2.6.15.2 If you have a REDIRECT rule for squid like this: > > iptables -t nat -A PREROUTING -p tcp