devnull42

Heh I gave a talk at DefCon Skytalks last week on this exact exfil method and C&C structure with a live demo using code we wrote....interesting.

CNAMEs at apexes make my heart hurt so much.

It goes against RFCs and you shouldn’t but non-compliant resolvers will do it.

rfc1034 is vague but rfc2181 clears it up. https://tools.ietf.org/html/rfc1034 https://tools.ietf.org/html/rfc2181

The Infrastructure plans seriously limits support techs from helping. They wont be able to see running configs or logfiles. They can't login to your box at all you are feel around in the dark and playing ticket ping pong until you get the info you need to even make an educated guess as to the issue even then you cant test the fix.

When I interviewed at Rackspace 3 years ago I had 8 interviews. Things have changed since then but I remember the process really being comprehensive for both culture fit, technical, and overall just who you are. I used to do interviews when I was in Support and this article is indeed accurate.

So at the moment I see no reason why Go written BGP would be better than standard Quagga/Zebra. There aren't really concurrency or resource issues with large scale Quagga in my experience.

Correct but they would not have had access to the the iCloud data without Apple doing work (Resetting password or handing over a copy of the data)

The original comment is correct.

Yup if they are able to support this it will get much more adoption in the corporate world.

And to add to that the real issue is that Slack stores data unencrypted on their servers.

This would be handing your financial data over to a third party to old in an unsecured format. Yikes.

I run some pretty large NTP deployments and our NTP drift is never really over 1 second. Now the difference between NTP serverside drift and client server-side "skew" isn’t something I have looks at but for the most part I get a nagios alert on anything over 1 second of drift with 5 seconds being the most I have ever seen.

So no onsite data storage and no at rest encryption? These are the reasons we have been having issues with Slack. I was hoping they would address these clear gaps in the enterprise market.

I have been working with this for quite some time now. I was pretty surprised to see this on HN as news.

Regardless of why this is here, negligence or cost cutting, this is pretty bad and leaves the systems pretty open.

I actually had my first interview was told I passed it and they would schedule the next one with me within a couple days then never heard back.

:(

Friends on the Backbone DNS Team.