Re:OpenBSD disables Heartbeat in libssl, questions IETF
by 0x0 on Thursday April 10, 2014 @04:59PM
(#7569661)
I think it can be useful when the TCP connection is going through NAT which may drop the rule and stop passing packets after idling, no?
[ Parent
| on HN ]
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by mschuster91 on Thursday April 10, 2014 @05:01PM
(#7569673)
Yep, crappy routers tend to do this :/
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by fulafel on Thursday April 10, 2014 @05:02PM
(#7569681)
It's not a real router if it does NAT. NAT is just a half assed proxying hack for hosts not on the internet.
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by feld on Thursday April 10, 2014 @05:41PM
(#7569913)
A Juniper MX960 can do NAT. Is that not a router?
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by fulafel on Friday April 11, 2014 @09:20AM
(#7572652)
If it's configured to do NAT instead of routing, then it's not being a router. Routing is a job and "router" describes a role, not a static property of a box. Like firewall, bridge, etc.
Routing is defined as shuffling packets where they need to go unmolested - without messing with the address or port fields. It's specced in the IP RFC's. If you're mangling the traffic, you're violating router requirements.
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by feld on Sunday April 13, 2014 @02:13PM
(#7582211)
You're never seen a router have to do NAT for two subnets that it's routing between?
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by jlgaddis on Thursday April 10, 2014 @09:45PM
(#7570808)
While I certainly share your dislike of NAT, this is just absurd.
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by carey on Thursday April 10, 2014 @05:14PM
(#7569770)
In retrospect, I think using TCP_KEEPALIVE would be a better solution to this specific use case. Are TLS heartbeats truly indistinguishable from normal traffic?
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by pstrateman on Thursday April 10, 2014 @06:25PM
(#7570090)
TCP Keepalive is a much better solution for this problem.
Nearly all bitcoin pools utilize TCP keepalive to maintain connections with miners.
These are systems in which performance and DoS resistance are paramount.
Re:OpenBSD disables Heartbeat in libssl, questions IETF
by lsaferite on Thursday April 10, 2014 @06:33PM
(#7570126)
My understanding, from the heartbleed page, is that the packets for the heartbeat have a specific packet type identifier and that you can use this to train an IDS to watch for the heartbleed attack.
I would guess that makes them identifiable?