HN user

raides

17 karma
Posts0
Comments14
View on HN
No posts found.

There is less of a chance that the Colo or shell account you are using to run psybouncer will hand over anything to anyone before you wipe the machine than there would be directly connecting to a VPN service. I think this is addressed to average Joe Americana who clicks the protect button in Facebook.

I've made this argument several times. I'm a psybouncer sort of guy. #shellz

It is super easy to get a 2 dollar a month shell account and run psybouncer with a list of hosts you can hide behind. At least then I can double proxy cheaper.

To the Aussie's credit the infrastructure and the regulations instilled on businesses there have always been Federally imposed.

Since the mid-90s the government has imposed many regulations for control that has impeded much of the free market progress for network infrastructure. Those regulations coupled with needed external transit installations have not helped. For a long period of time the government would pick and choose companies based on their ideals rather than their talent. This has hindered progress from both sides of the fence by liberal and conservative administrations.

I ran a semi successful ISP and consulting company for a decade in the US and I have always enjoyed the tiering system we setup vs other country Infrastructures. It wasn't until recently when the FCC gained control that states started to use the new regulation power to hinder progress. I am still on the fence about the whole thing because the exploitation has not been bad in my area but the horror stores I have heard in other states make me sad. Hopefully it will get back to normal.

I am curious on the hardware build out used for the storage nodes. Some of the major issues I have seen with all the appliances out there for storage are the following:

1. Network throughput on the appliance is fast but for an Enterprise level the 10gigE cards used become a bottleneck for transactions because of how the software hypervisor scales the data. 2. Power consumption of the appliances in a rack mount environment are too high and leave needed space that has to stay empty because of the facility power per rack limitations. 3. The software hypervisor scales the stack vertically and relies on the software to load balance horizontally. The performance in a high transactional environment becomes dependent on the software to scale instead of the natural horizontal distribution that can be setup on the hardware out of the box. Standard multi-purpose storage arrays scale horizontal with very little over head from traditional software storage management. I only found one company whose software does not force the stack to be vertical but they fail to meet a reasonable performance in network/power.

Streaming petabytes of data to keep a dynamic constant (static overall storage requirement that changes it's data life cycle via retention rules) becomes very hard with premade hardware.

Does anyone have any recommendations or has attempted a similar exodus from S3 that they can share?

The Surface Book has had facial recognition for almost two years now and it is actually impressive. Short of a full latex mask that has padding to shape the wearer's face it is pretty impossible to break into it. We did tests with iPad pictures and depth options, straight camera prints and a 3d printed model. None of it worked. It is also not easy to access latex custom latex masks.

I feel my only issue with FaceID is that when you are in handcuffs all it takes is for the phone to be held in front of you. It will be interesting what safety regulations are used to prevent illegal entry by police or captors.

No it actually is not the whole point. Security is never convenient. If you do not have an active password rotation automated for all accounts, even shared, then you should be more worried about an employee reporting you to compliance officers. #justsaying

The excuse that the application grew faster than scalable is amateur hour. This entire article makes any true sys engineer cringe in their stomach.

You are ~100 million dollar company and it seems like you drew your systems architecture with crayons. The article is upsetting. The lack of segmentation is embarrassing.

"oh it's the switch's fault, it doesn't learn MACs fast enough" - actually you could subnet your racks and use f*n vlans. You might use public Ips on everything but this could still be educational for the company.

Your solution to all of this was to spend twice as much on a "staging" network. Something doesn't seem right here.

It makes me cringe when I see any one sentence that has the following three words in it: escalate, network, vendor.

This isn't a boeing airplane, you cannot just rely on the vendor. This article just gives me a good sense of job security in the field of sys engineering. I really think that they should sit down and really go over their network. A bridge loop like this for a company this large is pretty amateur. Github you can do so much better.