Forgot your password?
typodupeerror

Comment: Counterpoint (Score 1) 204

by laughingskeptic (#48397887) Attached to: Your Incompetent Boss Is Making You Unhappy
One of the best bosses I ever had was technically clueless. He had been the company's best salesman. When he wanted to travel less, the president made him our fledgling team's director. He viewed his new job's duty as 'selling the team to management'. He figured out what management wanted for him to look good and shared that with us. His attitude was 'make me look good and I'll make you look good'. He also understood his cluelessness and asked about what to read. He would take books like Steve McConnell's Rapid Development, photocopy chapters and read them one by one while he ran on his treadmill in the evenings. It was always fun noting his progress based on his behavior and questions. Seriously one of the best bosses ever and taken way too young by Lou Gehrig's.

Comment: Re:Misleading- Good will is common accounting (Score 3, Interesting) 255

Accountants from the 1970s will tell you that having good will on your books means you made a dumb decision at some point. Modern accounting practice is to assign as much value of a major purchase as possible to 'Good Will' because of the associated write off. If you review the fortune 100's annual filings you will find them full of purchases of lesser companies where the majority of the value of the purchase was assigned to 'Good Will'. Since the IRS takes 'Good Will' assignment at face value, why wouldn't you take as big of a write off as possible if you are a business spending money?

Comment: Things everyone can do (Score 1) 106

by laughingskeptic (#48164107) Attached to: FBI Warns Industry of Chinese Cyber Campaign

In your firewall:

1. Whitelist destination IPs for destination port 53, workflow denials adding IPs that have reverse DNS entries. (e.g. don't allow access to fly-by night DNS servers)

2. Whitelist source IPs for destination port 53. (E.g. do not allow alternate DNS servers to be used inside your org)

Have your org's DNS servers point to OpenDNS or GoogleDNS -- they do a good job of filtering out the rifraf

Comment: Connect then duplicate (Score 1) 174

You should probably have your proxy choose just one path for the initial connection setup and then after some configurable number of packets start the flow cloning process to the secondary route. You want to make sure that the server has a chance to get whatever house keeping it does at connection setup time completed before you start relying on the magic of TCP to keep the server from going insane. If you mess with the connection too early you are likely going to mess something up in game's connection setup process. If you send the very first SYN packet twice there is a good chance the server will reset the connection. Then you are going to have to start adding TCP protocol logic to your proxy which is going to make it way more complex. You will need to peak at the TCP sequence numbers when deciding what to pass back to your client from the server.

UDP is a simpler protocol and therefore more complicated for you to handle. You won't have a sequence number and you will need to hash the contents of every packet coming from the server and only pass packets back to your client that you haven't seen before. And of course you will need some sort of expiration on the hashes.

Without fully implementing the TCP protocol in your proxy you can expect issues from time to time, particularly when you pause play and a reset might slip in at the TCP protocol level. But you should be able to create something that works most of the time pretty easily.

As in certain cults it is possible to kill a process if you know its true name. -- Ken Thompson and Dennis M. Ritchie

Working...