Forgot your password?

Comment: Re:Just use headlights (Score 1) 187

by CBravo (#46750117) Attached to: First Glow-In-the-Dark Road Debuts In Netherlands
Not at all. We probably have the best roads in the world. Silky smooth, hardly makes noise, very well maintained. I drove through Europe a while ago from the Netherlands to Italy and the NL was the quietest. We invest a lot in infrastructure and roads are part of that. The onlly thing that is not nice is the speedbumps.

I was in North Caroline a while ago and it reminded me of a bad stretch of Polish road. Canada is ok, given its two seasons (winter and road repair season?).

Comment: Re:It's not just the implementation (Score 1) 446

by CBravo (#46722939) Attached to: Heartbleed Coder: Bug In OpenSSL Was an Honest Mistake
Some have overseen the fact that a heartbeat in one layer isn't always enough. The OS tcp/ip heartbeat might have different timeout than preferrable for TLS and you may not have the option to change the one from the OS for different reasons. The second issue is that you want to have the proper exception handling (to correct the issue you had with the bad connection). Just getting a new connection may not cut it.

I had the issue recently when a redundant system had a failover due to maintenance. The firewall of the second system, which took control of the IP address, just ignored the packets (TCP session failover was of no use here) and the messaging system thought that the message was sent (tcp was not complaining for a while). I fixed this by letting the messaging system send an ACK after every message and activating the heartbeat of the messaging system. Any failover is now detected quickly and resolves in making a new connection (and when this happens while sending a message: retry). The original situation always wasted a dozen messages and then corrected by making a new connection.

Comment: Re:US blame culture. (Score 1) 479

by CBravo (#46450369) Attached to: Author Says It's Time To Stop Glorifying Hackers
Although this is a simplistic example of what is obviously stupid... There is an argument to make for her.

First, she does not know beforehand this is stupid. Second: Are not all hacks stupid afterwards? It is only a question of how professional you can and will/must do stuff. There are hardly any laws on how much one has to lock down and tripwire operational systems to detect penetration (attempts). There is always the commercial pressure of feature (over security costing money). I have seen many security departments being overruled because function is more important (that includes banks). Just check online how many banks actually implemented a feature like DMARC on their domain (with policy:deny). It tells you exactly how lax securiy rules actually are.

Nobody takes responsibility because noone has it. The only stupid thing she can be blamed of is not having a company policy to CHA.

"If that makes any sense to you, you have a big problem." -- C. Durance, Computer Science 234