Linode Turns 14
blog.linode.com
blog.linode.com
Since all of my dynamic based sites are dead and I'm just on static based sites now, I just threw it all into Google Cloud Storage and host it from there (which greatly reduced my money hosting cost).
Overall Linode did a great job hosting for me, especially considering the price. But moving to "cloud" providers where I don't have to worry about keeping things upgraded and secure was worth the move to me. I enjoyed it for a long while, but there are easier to maintain services out there now.
However, I find Linode's interface far less opaque and easier to use than Google and Amazon's for ongoing site management. I can also get a response from Linode in a few minutes when I submit a help request. Google's Cloud offering must have decent support, though I only know their reputation for one-on-one support across their other offerings which has traditionally been abysmal.
The other nice thing about Linode was the free upgrades. When they did fleet-wide updates to CPU/Ram/Disk, you could go into their UI, click a button and be migrated fairly quickly/easily.
I also agree that GCP and AWS are a lot more complicated, as they are vendor-specific ways of solving certain problems, which can be solved normally with Nginx and some configs (which is portable across any VPS/dedicated-host provider).
That is for static sites, for more complex sites where scalability is important, I think these offer advantages.
Tried to check out their new Linode Manager, but: "The Beta Manager and API V4 are not available for legacy pre-pay accounts. Please convert to Hourly billing." Shucks. Guess I'll have to give up on the idea of an annual discount.
I hope the new API fixes the security issues they've had in the past. We'll see.
Linode has been hacked at least 5 times¹ in the past decade, and EVERY TIME they try their hardest to downplay the incident and distract attention from it. Avoiding any public communications at all if possible.
This HN comment from a PagerDuty employee is also particularly damning https://news.ycombinator.com/item?id=10845985
I'm not saying I disagree. To prove that, for the record, I informed Linode leadership that ColdFusion admin being world-accessible was a bad idea several years before you and your 'team' were even aware of Linode, and I and another employee proposed replacing ColdFusion long before you flippantly suggested that it doesn't take years[0]. (Try running a hosting provider at medium scale.) I've been just as critical long after leaving Linode as an employee -- I saw oversights like mgreb:mgreb1221 being a full-admin user on world-accessible db1.linode.com for many years with the password in crons, for example -- so please don't interpret me as disparaging your opinion, only your trying to have it both ways with a very clear conflict of interest, and turning your takedown of Linode into a potential annoyance for me and thousands of other people. And yes, I know the key passphrase that you never recovered, despite your public assertions to the contrary.
I was successfully prosecuted for hacking coldfusion things in general, that list included Linode and over 50000 others. There was a pending investigation relating to Linode specifically, but I'm pretty sure that's hit the statute of limitations and can only assume that there's no intent to prosecute.
>Reading your comment with that context changes it slightly
You're right, it does. I considered linking directly to https://news.ycombinator.com/item?id=10845278 but figured I could deliver the information in a more concise manner, without quoting myself.
I made a mistake in not immediately clarifying my relationship here.
>given that since said prosecution you've taken every opportunity to speak negatively about Linode that you can
Since long before that actually.
>And yes, I know the key passphrase that you never recovered, despite your public assertions to the contrary.
What are you referring to? The credit card decryption key? I assure you we most definitely got that, if you want I might be able to dig up old IRC logs from police documents with plaintext credit card information of several linode customers. Jennifer Emick, Robert "xnite" Whitney and Ryan Cleary as I recall.
This is a significant exaggeration, but I'm not going to dox you. Suffice to say, I'm reading your case as we speak, so stop trying to mislead people. (Good luck with that visa.)
> What are you referring to? The credit card decryption key? I assure you we most definitely got that
Then name it. I have the one that protected the key you retrieved memorized on account of my duties (I had to enter it every time I restarted the application), and they've changed it since then, so it's a no-op. It's not brute forceable even by nation states, so you'd have had to extract it by means your entry vector did not give you. Hash it in your reply if you want.
I've always suspected you had former employee help, and I'm pretty sure I know not only exactly who, but also their motive for assisting you and "HTP". If you do have the passphrase to that key, I can almost promise it was from your assistance. I eagerly await your reply, since the passphrase is a sentence, and once you know it the gist of it is easily communicable without consulting logs.
It really isn't. The big number in that charge is referring to coldfusion shells the local CERT was supposedly able to "validate".
At best you could blame the prosecutor for exaggeration, which I entirely agree with, the court however accepted the prosecutors claims.
>Good luck with that visa.
Haven't actually had visa issues anywhere since then :) Good passport I guess.
>Then name it. I have it memorized, and they've changed it, so it's a no-op.
No clue, people within the group disagreed on carding so the person who got it didn't post it on the channel, only dropping the cards of "interesting" individuals. I guess I'll go looking for the logs though.
>It's not brute forceable even by nation states, so you'd have had to extract it by means your entry vector did not give you. Hash it in your reply if you want.
As far as I know someone wrote a quick coldfusion script to extract the decrypted key from memory.
>I've always suspected you had former employee help, and I'm pretty sure I know not only exactly who, but also their motive for assisting you and "HTP".
This was certainly not the case.
>If you do have the passphrase to that key, I can almost promise it was from your assistance. I eagerly await your reply, since the passphrase is a sentence, and once you know it the gist of it is easily communicable without consulting logs.
Don't know, and I'd assume getting coldfusion to spit out the decrypted key is much easier than the decryption passphrase that's only needed once.
And in any case your approach seems fundamentally flawed. Even in some parallel universe where we failed to extract the key, we'd still have been able to use your existing decryption code and the in-memory key to decrypt all the cards in the database.
I haven't typed it since 2011 and still remember it; it's a stupidly simple English sentence that is almost impossible to not memorize. I also note that you and your group were challenged for it in 2013 and declined to provide it. But sure, go consult logs. I'll hold.
> This was certainly not the case.
I know the network and channel where you two hang out, so OK. Keep lying to HN, I guess. (Why would you?)
>I know the network and channel where you two hang out, so OK.
Then spit it out, name the network and channel, don't make vague accusations. I'm open about my beef with Linode, but what's your beef with me?
If this is supposed to be more than a pathetic attempt at discrediting me with false accusations, please follow through.
Move on with your life. You hacked them, you got busted, and sitting around like this four years later is just indefensible.
Edit: I'm remaining vague so as not to dox you, given HN guidelines and my own personal ethics. I don't have any stake in discrediting you (you do a fine job of that yourself), but you're welcome to spin it that way. Also, your clock ran out on being uniquely positioned to comment in 2014. (As did mine, though sooner.)
Fair.
>(b) dumped everything you found online
Not even true. Neither Linode customer db or source code were publicly released.
>(c) spend your days in every Linode thread trying to shit on them while pulling wool over HN's eyes as some kind of moral high ground just "obligatory warning" a bunch of people about your own fucking actions.
Mostly not my actions, but I seem to be uniquely well positioned to give such advice given my that I've seen the insides of Linode.
>You are not the moral high ground. Please stop pretending to be as some kind of authoritative voice.
I'm certainly not the moral high ground, but I've certainly seen for my own eyes just how much of a mess Linode is.
>Move on with your life. You hacked them, you got busted, and sitting around like this four years later is just indefensible.
I don't really care about any of that. To be fair I'm more annoyed with a bunch of my time being wasted because some guy with a thick Australian accent (i.e. obviously not me) swatted them.
But this isn't my personal blog, hit me up on IRC and we can chat.
Good to know you folks are going strong - all the best.
They do offer private lan networking, but that is shared with all the other customers, if I don't trust the internet, I won't trust other Linode customers.
Does anyone have experience with a hosting provider that offer something similar?
This is interesting... Leasing point to point connectivity like this is surely very expensive for a VPS provider, I understand non-connectivity players like OVH and Google Cloud doing this but Linode?
I get 15 ms better ping to Frankfurt Linode compared to Vultr, for example.
Just compare: http://bgp.he.net/AS63949#_peers to http://bgp.he.net/AS200130#_peers
And you will see that DO alone in Europe (compared to Linodes global ASN) has many more transit providers and peerings.
Linode may be 14 years old, but they've only been running their own network for a year.
This is significantly more expensive than AWS S3 or Google Cloud Storage.
The last time S3 charged similar prices was in January 2014: https://aws.amazon.com/blogs/aws/aws-update-new-m3-features-...
edit: I'm keeping this comment up in case other people have the same confusion I did.
Linode has an INCREDIBLE support staff. Like, superhero action squad to the rescue as soon as something goes wrong incredible, they're just that good.
Please get some real boxes though! I really want to come back!
Linode Turns 87178291200
var now = new Date();
var then = new Date();
then.setYear(then.getYear() - 14);
console.log(Math.floor((now - then) / 1000))
// 60400079994 (seconds)Here's a few HN threads on the previous disasters:
https://news.ycombinator.com/item?id=3654110 Compromised Linode, thousands of BitCoins stolen (2012)
https://news.ycombinator.com/item?id=3655137 Linode Manager Security Incident (2012)
https://news.ycombinator.com/item?id=5552756 Linode hacked, CCs and passwords leaked (2013)
https://news.ycombinator.com/item?id=7086921 An old system and a SWAT team (2014)
https://news.ycombinator.com/item?id=10825425 Linode DDoS continues – Atlanta down for 16+ hours (2016)
https://news.ycombinator.com/item?id=10998661 The Twelve Days of Crisis – A Retrospective on Linode’s Holiday DDoS Attacks (2016)
https://news.ycombinator.com/item?id=10845170 Security Notification and Linode Manager Password Reset (2016)
https://news.ycombinator.com/item?id=10806686 Linode is suffering on-going DDoS attacks (2016)
Edit: Guess someone linked this on the Linode staff channel :) Hi guys!
> "While you and the sources you link to are generally correct, you should probably disclose your relationship with Linode when you make these comments -- namely that you were involved with, and successfully prosecuted for, one of the more serious of the five."
They are just another hosting company, I'm sure your can find holes and dirt on all of them?
Why not attack an organisation that is "more evil" ?
I'm certainly not alone in recommending against Linode, any sane security person will share the sentiment.
>Why do you hate then so much?
I don't really "hate" Linode, but I certainly don't wish them luck.
Why?
They wasted a bunch of my time because some guy with a very thick Aussie accent prank called them and the police while introducing himself as me.
>Why not attack an organisation that is "more evil" ?
I can do both, although I'm hardly "attacking" Linode. I'm simply pointing out their very poor track record, which is an indisputable fact.
Why advice folks away from a hosting provider that covers up known breaches for months? https://news.ycombinator.com/item?id=10845985
Or one that tells their employees to lie about breaches? https://imgur.com/sJd56AT
Or one that refused for years to spend a couple of minutes thinking about security, until it started to actually hurt their bottom line? As jsmthrowaway points out, Linode was aware of serious security issues for years and did exactly nothing to protect their customers. https://news.ycombinator.com/item?id=14572970
Honestly, I was wondering if Linode staff or people on "their side" downvoted the post since it didn't seem downvote worthy. It's only fair that their track record follow them, especially their free press. It wasn't a rant or an accusation or anything personal. It was just a list of their past actions and what others had to say about it.
Otherwise look at dedicated hosting, preferably colocation but just renting servers can be cheaper and isn't so bad. Encrypt your drives, either disable your IPMI thing completely or ensure that it's only accessible over a VPN by you only and not your host. OVH (and their other brands) might be a decent cheap choice for dedicated hosting that should be very competitive in Linodes price bracket.