Soo…I’d recommend against something like Nux’s suggestion below. I’ve only looked briefly at VirtualDNS.java, and it looks fine from a glance, but I’m willing to bet I can a) DOS it, and b) use it for a reflection attack. I could be wrong, don’t really have time to look closely, but based on it looking like the design pattern for a basic UDP server, I wouldn’t recommend the community to build a network of those.
4 months is not a huge period of time, but I think if somebody can’t apply a patch within 4 months they need to consider if they should be running that service. If this was a critical security vulnerability and folks couldn’t patch it within a few weeks of notification, I’d have a hard time feeling sorry for them. I do concur that we should back port the patch. John On Mar 7, 2014, at 11:19 AM, Nux! <n...@li.nux.ro> wrote: > On 07.03.2014 14:55, France wrote: >> Hi all. >> Are we going to have a solution for older versions like 4.1.1? >> I think we can already change that domain to something different >> currently in settings. Hopefully it's not "hardcoded" anywhere else. >> Is it? >> I think it's the right thing to move away from such solution in >> future versions, but just killing the service with 4 months notice, is >> not a way to go about in enterprise world. How expensive can it be to >> keep providing it? >> If someone needs to take over realhostip.com, we can offer our >> datacenter resources too. >> Regards, >> F. > > It would be interesting to change the NS to 3-4 different Cloudstack > users/backers. Even I could run an instance. > > France, here's how to run your own (excuse the formatting, was written in a > hurry): > http://www.nux.ro/archive/2014/03/Run_your_own_realhostip.html > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro Stratosec - Compliance as a Service o: 415.315.9385 @johnlkinsella
