Displaying 5 results from an estimated 5 matches for "ts_recent".
Did you mean:
is_recent
2005 May 20
1
Possible PAWS security vulnerability
..._flags & TOF_TS) != 0 &&
SEQ_LEQ(th->th_seq, tp->last_ack_sent)) {
+ if (SEQ_LEQ(tp->last_ack_sent, th->th_seq + tlen
+
+ ((thflags & (TH_SYN|TH_FIN)) != 0)))
+ tp->ts_recent = to.to_tsval;
+ else
+ tp->ts_recent = 0;
tp->ts_recent_age = ticks;
tp->ts_recent = to.to_tsval;
}
After I basically let Ted know that I wouldn't know how to test the...
2015 Apr 08
1
syslinux.efi with QEMU/OVMF
...zeof ( *tsopt ) );
> memset ( tsopt->nop, TCP_OPTION_NOP, sizeof ( tsopt->nop ) );
> tsopt->tsopt.kind = TCP_OPTION_TS;
> tsopt->tsopt.length = sizeof ( tsopt->tsopt );
> tsopt->tsopt.tsval = ntohl ( currticks() );
> tsopt->tsopt.tsecr = ntohl ( tcp->ts_recent );
> }
>
> (When opening the connection, the TCP_SYN flag is set (from tcp_open() I
> guess?).)
>
> So, the two builds use different TCP stacks on the client side.
OK, so I've changed the test with BIOS to use gpxelinux.0 instead (hoping
that will match the syslinux.efi cas...
2015 Apr 07
3
syslinux.efi with QEMU/OVMF
Hello,
I'm trying to find out how to pxe boot with syslinux.efi on QEMU with
OVMF. After getting through the initial hurdle caused by the iPXE based
option ROM included with QEMU having a problem as described in these
threads:
http://www.syslinux.org/archives/2014-November/022804.html
http://sourceforge.net/p/edk2/mailman/message/33236100/
I'm now getting further to almost being able
2015 Apr 07
0
syslinux.efi with QEMU/OVMF
...pt = iob_push ( iobuf, sizeof ( *tsopt ) );
memset ( tsopt->nop, TCP_OPTION_NOP, sizeof ( tsopt->nop ) );
tsopt->tsopt.kind = TCP_OPTION_TS;
tsopt->tsopt.length = sizeof ( tsopt->tsopt );
tsopt->tsopt.tsval = ntohl ( currticks() );
tsopt->tsopt.tsecr = ntohl ( tcp->ts_recent );
}
(When opening the connection, the TCP_SYN flag is set (from tcp_open() I
guess?).)
So, the two builds use different TCP stacks on the client side.
(Obviously I have no clue, but this is what I could gather in five minutes.)
Laszlo
2005 Jun 24
1
Any status on timestamp vulnerability fix for 4.X?
Any information on when (or if) the following timestamp vulnerability
will be fixed for 4.X? Any information would be appreciated.
http://www.kb.cert.org/vuls/id/637934
Thanks.
Richard Coleman
rcoleman@criticalmagic.com