Re: Borderware predictable initial TCP sequence numbers

From: Kevin Steves (steveskat_private)
Date: Wed Sep 02 1998 - 11:17:17 PDT

Next message: Patrick: "Re: Security Hole in Axent ESM"

Previous message: psirtat_private: "Cisco Security Notice: PIX Firewall Manager File Exposure"
Maybe in reply to: Roy Hills: "Borderware predictable initial TCP sequence numbers"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 2 Sep 1998, Gigi Sullivan wrote:
: This can be applied also to Firewall-1 (CheckPoint) running on an
: HP-UX 10.X series.

In HP-UX 10 there's a tunable object to control TCP sequence number
generation:

$ nettune -h tcp_random_seq
tcp_random_seq:
When set to one (1), TCP randomizes initial connection sequence
numbers.  When set to two (2), a more sophisticated randomizer
is used. When set to zero (0), normal time-based, linearly
increasing sequence numbers are used as described in RFC 793.
The default is disabled (0).

Next message: Patrick: "Re: Security Hole in Axent ESM"
Previous message: psirtat_private: "Cisco Security Notice: PIX Firewall Manager File Exposure"
Maybe in reply to: Roy Hills: "Borderware predictable initial TCP sequence numbers"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b30 : Fri Apr 13 2001 - 14:14:50 PDT