Re: Workaround for serious TCP exploit [correction]