Servers

Elliquiy Security, part I

Elliquiy's time at Accelerated Web was not a bad one. The new server is faster, more reliable, and more customizable. However, there is something you do not see in that $50/month ($60/month when I purchased it) price tag and feature list for that host. Of every shared host I have seen, they were the most security-conscious by far. It is hard to fully express just how much I learned from them.

Not just because it would take awhile, but discussing the finer details of how Elliquiy is set up always bothers me - knowledge can be used against its giver. I also have a moral objection to throwing out technical details that I am not willing to make at least a courteous attempt at explaining. I hope that, if you are curious, you do not feel that I throw out random terms that hold no meaning without explanation. I am going to do my best to explain a lot of terms here, but if I fail and you are still curious, please feel free to ask.

This does not keep me from discussing concepts, things that a technically adept attacker would know, or someone who takes the time to read the public statements I have made so far, however. That still leaves quite a lot to talk about, so I am going to begin somewhat randomly. : )

Moving Pains

From apache's log:

[Wed Nov 19 07:11:16 2008] [warn] long lost child came home! (pid 5523)
[Wed Nov 19 07:11:16 2008] [warn] long lost child came home! (pid 5524)

Why we Moved

I get various hints at this question and I figured I would try to explain the technical details with more rigor. This has been a goal of mine for some time now, and honestly the main benefit can be expressed as 'liberation'. That is, having Elliquiy on a dedicated platform means that I have options that simply weren't available to me before.

Syndicate content