When I try to think about explaining this period of our company, it's hard to put into words the genuine changes Pterodactyl had on the people which naturally form the company. Better yet, the issues I expected to occur? They never happened.
Today I am releasing Pterodactyl Daemon v0.4.6 to address a DoS attack vector in the Daemon as well as address a race condition in the code causing some headaches for large hosting providers. This blog post will quickly cover what was discovered, how it affects you, and what was done to address it. I was made aware of a potential issue in the Daemon earlier this week when a member of our support team and developer at a hosting company using Pterodactyl reported unexplainable
In previous versions of Pterodactyl you had very few configuration options available in the Admin CP. For the most part this was done because I was moving quickly to implement other features and abused Laravel's excellent configuration system to keep track of things. There were many instances were users had to ask around to figure out what environment variable they needed to change in order to toggle a feature on or off. No more though! Pterodactyl@0.7 introduces a much improved Admin UI that allows
Two years ago Pterodactyl went public with our first ever commit. Since then we've seen over 1500 commits, 38 releases, and a community that continues to teach me daily.