Support forum
wyDay blog
wyDay Home

The wyDay blog is where you find all the latest news and tips about our existing products and new products to come.

wyDay blog

We’ve just released TurboActivate 3.4.7. You can get it right now on your API page.

Here are the changes:

  • On Windows, if a customer disabled a network adapter it would force them to re-activate. Now it just acts as a “fuzzy change”. In the upcoming TurboActivate 4.0, the fingerprinting algorithm has been vastly improved to reduce all known false-positives and false-negatives. This is not that improvement.

  • On Windows (and some unconfirmed Mac OS X reports) in some regions of the world TurboActivate failed to contact the activation servers even if there was nothing locally (on the computer or LAN) blocking the connection. This has been fixed by back-porting the vast amount of networking improvements back from TurboActivate 4.0.

    This bug was a result of an ISP-level configuration error that effected a chunk of customers in Australia and New Zealand.

  • All communication with the activation servers now happens over HTTPS on port 443. This prevents system administrators or any middle-men from inserting junk into reponses to/from the servers. Previously sensitive information was encrypted, but the data was transmitted over HTTP under most circumstances.

  • Included XCode project for the C example (1 project for dynamic linkage, another for static linkage)

The past 24 hours have been pretty eventful. We’ve undergone 2 pretty nasty DDoS attacks (and another half-hearted DDoS attack) on our servers. And as a result we had about 2 hours of downtime.

And for this I’m truly sorry.

The good news is we’re back up and running now. If you’re having trouble accessing your LimeLM accounts (or even just accessing in general) then make sure you do the following:

  1. Make sure your network is not caching old DNS entries. Our IP addresses have been swapped out and we’re now behind CloudFlare. If you try to access using an old IP address nothing will happen.

  2. Make sure you’re not hard-coding IP addresses to a whitelist. Never do this. Always use the DNS servers. Our IP addresses have changed in the past, they’ll change again in the future. I guarantee it.

Quick FAQ for people who don’t know what a DDoS is

A DDoS is an acronym for “distributed denial of service”. Or, in plain English, it means someone with a grudge wanted to throw a whole bunch of traffic at our servers so that no one else could access our servers.

A DDoS is not a hack. No data was accessed; our servers remain secure.

The long and short of it is that DDoS attacks are a blunt, ultimately harmless, weapon used by small-minded people.

What we’ve done

The 2 big things we’ve done is:

  1. Swap out our old IP addresses.

  2. Put our servers behind CloudFlare.

This means that the brunt of future attacks will be handled by CloudFlare. Meaning more uptime for us (and less angry customers calling you).

What’s coming

In addition to everything we’ve done to successfully stop this DDoS attack, we’re also going to further improve our backend so that there is never any 1 “point of failure”. Before these latest attacks there was 1 “point-of-failure” in that all traffic was being routed through a single IP address.

So, even though we have several servers spread across the United States doing the hard work of processing activations, verified trials, API requests, and everything else that LimeLM does, all traffic had a common “entry point” in our systems. This was a mistake and didn’t account for the cynical nature of the Internet.

In the coming weeks we’re going to add several new entry-points world-wide so that if a subsequent DDoS attack effects us at all it will last minutes rather than an hour (because all we’ll have to do is “flip a switch” and legitimate traffic will be routed through new entry points, while the attacked entry-point will be shutdown).

What else is coming

TurboActivate and TurboFloat 4.0 are almost out. We’re just finishing 2 last-minute bug fixes, and then going through one last round of testing. These are significant releases that we’re very proud of. I’ll post a long detailed blog post when they’re released.

The announcement blog post will also talk about the infrastructure improvements we’ve already done.

– Wyatt O’Day
Founder & CEO of wyDay

Tags: LimeLM, Scum

Hey Guys (and girls),

LimeLMThis is a short, but long overdue, update to tell you we’ve extensively tested all of our products with the current pre-release build of Windows 10 (10240), and everything is working perfectly. So if you’re using the latest version of TurboActivate and TurboFloat (get the latest versions on your API page), and the latest version of wyBuild, then you’ll be able to continue to use the best licensing and updaters with all currently supported versions of Windows.

(And of course, with TurboActivate and TurboFloat, you’ll be able to continue to use the best licensing on Mac OS X, Linux, and soon Android in addition to the Windows support).

We’ll of course test everything with the final Windows 10 once it comes out.

We keep an up-to-date list of compatibility and requirements on their own pages:

Big changes coming

This past week we did major work and expansion to our server infrastructure to support the big features that are coming to LimeLM in the very near future.

The only changes that you will see currently (as of me writing this) is a healthy speed-up for all requests (managing licenses in LimeLM, online activations, deactivations, web API requests, etc.). But visible — and very cool! — features are coming soon.

So, stay tuned for big updates to LimeLM, TurboActivate, TurboFloat, and wyBuild that will be rolling out over next 3 months.

I’m excited! I can’t wait to show off our hard work to our growing, loyal, customer base.